Save geometry after transaction or run multiple transactions


Coming from Revit- Dynamo( Building Design) background, i am new to Bentley generative Components & exploring it currently. In revit dynamo, once we run a script & close dynamo , the geometry/process still is saved or present in model. we can run another script post that without worrying about the geometry or any element in revit being affected with respect to the task being automated .
when i try the same in generative components say create points from excel or place cell based on coordinates, only one transaction is available at a time , how can i save the placed geometry/cell or points? So that i can run another transaction or scripts do further automation later on as & when the team needs to modify anything.  i tried switching to modeling or aecosim from dropdown after i ran transaction , it did save geometry the next time i opened generative components, but it seems to crash most of the time. any help would be appreciated.

Parents Reply
  • We GC users are very comfortable

    Yah... maybe too comfortable for too long Stuck out tongue winking eye

    The 2D survey example illustrates the problem. Once the info is processed and part of the general OBD model it is difficult to manage / retrieve for further processing by GC. Advantage: Dynamo.

    It would be good to discuss further and clarify the options available now and maybe what is in the pipeline. Future SIG-o-rama?

    A 'Range Processor' Node might be something that should be on the near term roadmap.

    1. User writes script in model A.

    2. User Ref attaches elements to be processed in Model B or uses a Ref attach Node.

    3. User uses Range Node to suck in elements to process.

    4. New option in Range Node to lock the elements in the Ref attachment using the same mechanism that spits this cheerful message out 'The originating application (22877) has intentionally restricted changes to this element.'?

    5. User wires results to a Range Processor Node that exports the results back into the Ref attachment. Inputs include the Range Node (to get the keys to find, unlock and delete the input elements; as well as the dgn file and model path etc).