Bit of a weird bug that I’m experiencing while trying to utilise the view.SetCropRegion node within a script which is also creating the views I’m trying to set the crop region of.
After getting the script to a certain point I starting having issues with the following error message displaying on any revit interfacing nodes:
Starting a new transaction is not permitted. It could be because another transaction started and has not yet been completed yet. or the document is in a state in which it cannot start a new transaction.
After an iterative process of of freezing portions of the script I tracked down the error maker to be the view.SetCropRegion node. As, if I freeze this node, I have no issues with the rest of the script and the elevations are created (albeit with an undefined crop region).
I’ve tried a number of passthrough configs as well as forcing a transaction.end but to no avail. Every time I get pushed this error.
Could it be something to do with the ElevationMarker.Create node and view.SetCropRegion node not enjoying being together?
I’d ideally like to keep this within 1 script so any suggestions would be appreciated!