Hello, I’ve created a dynamo to automate interior elevation setup, and in the project I built the dynamo in, everything worked as expected. I switched to a new project, and I keep getting the same error “Warning: View.SetCropRegion operation failed. Starting a new transaction is not permitted…” fro…

Just an update- I never found a way to use rhythm’s View.SetCropRegion node. I ultimately just found ways around using it, specifically View.SetCropBoxCurves from MEPover. I am still interested in understanding why this particular node kept having the error, but don’t know enough to really troubles…

I have seen this before when the node is trying to use standard transactions and/or sub transaction when Dynamo is trying to also use / run it’s transaction that has to be force closed. You could try using a Transaction.End node from the BoundingBox.ByCorners and the SetCropRegion node. @john_piers…

[image] Setting Crop region Revit @Snehal25 Try this: Set_Crop_Region_bb_For Snehal.dyn (69.5 KB)

Thanks Sean for the suggestion, although adding the Transaction.End didn’t fix the issue. I will keep trying different variations.

Thanks Vijay for this thread. @Kulkul used the same node that is causing me problems in the supplied .dyn, and I verified I get the same warning/error when modified to run in my project. It’s frustrating that I’m so close but can’t seem to get past this. Thanks again.

[image] jweber: I am still interested in understanding why this particular node kept having the error @SeanP nailed it on the head here :point_down: [image] SeanP: I have seen this before when the node is trying to use standard transactions and/or sub transaction when Dynamo is trying to…

John, Thank you for the reply. I was mostly curious as to whether it was something I was doing, or could avoid doing, that was triggering the error, but thanks for the explanation. Also, a whole-hearted thank you for all that you do, both here in the forums and through rhythm package. Very very mu…

I am getting stuck on the same issue. Has there been any update on this issue? Also if there’s a work-around, I would love to see the dynamo graph for its solution.

Did you try the mepover option?

Hi! Yes, I am so so so close to the solution. Here is my dynamo graph. The only problem is that the Dynamo generated crop region shows up as a blue line when I try to export the view as an image, which is annoying. [Export_Image_2]

Turn off the revit preview in the Dynamo display settings, or disable the preview of any nodes generating geometry in Dynamo. Sounds like otherwise everything is working which is great.

Setting a View's Crop Region

Packages

_Vijay April 5, 2021, 4:25pm 3

Topic		Replies	Views
Rhythm node causing transaction error Revit rhythm , transaction	10	899	July 14, 2021
Issue with View.SetCropRegion Node (Rhythm Package)	6	871	July 29, 2019
New transaction is not permitted	4	468	March 29, 2022
Views.SetCropBox throws - "Value cannot be null. Parameter name: obj." Error Revit revit , dynamo , views	4	1013	May 2, 2022
Edit crop region Revit	25	17145	September 30, 2018

Setting a View's Crop Region

Related topics