topic Re: Updater Exception due to Recursion in Revit API Forum

Updater Exception due to Recursion

mm1452 — Tue, 06 Jun 2017 14:00:39 GMT

Hi All,

the below exception has been thrown when trying to modify the modified elements.

"Third party updater 'MyUpdater' has experienced a problem and its action had to be canceled."

I think that happened because my business logic recursion behaviour

Any help about how to modify the modified elements?

Thanks in advance.

Re: Updater Exception due to Recursion

jeremytammik — Wed, 07 Jun 2017 18:07:33 GMT

Afaik, the different updater types have different priorities and are executed in a specific order.

Choose the correct updater priority.

If that does not help, check out the hints on Dynamic Update of Elements that Mutually Influence each Other in

http://thebuildingcoder.typepad.com/blog/2013/12/devlab-munich.html

Here is The Building Coder topic on DMU:

http://thebuildingcoder.typepad.com/blog/about-the-author.html#5.31

Good luck!

Please let us know how you end up solving this.

Thank you!

Cheers,

Jeremy

Re: Updater Exception due to Recursion

mm1452 — Mon, 12 Jun 2017 15:25:28 GMT

Dear Jeremy,

Thanks for caring.

Regarding the problem, I have tried several approaches like make a condition inside the execute method to end the recursion by checking the equality of the modified elements ids, but the exception still thrown. Also trying to save the elements ids and modify them at the updater destuctor but I have found the updater object still a live! finally I gave up :D.

So I have redefined the problem by customizing the event using GetChangeTypeParameter method instead of GetChangeTypeAny which doesn't throw an exception but doesn't satisfy all my need.

Thanks,

Re: Updater Exception due to Recursion

FAIR59 — Mon, 12 Jun 2017 20:37:07 GMT

Inside an Updater you aren't allowed to use a transaction. When you do, you'll get the message you described.

Re: Updater Exception due to Recursion

jeremytammik — Tue, 13 Jun 2017 07:35:41 GMT

Yes, absolutely!

The updater already has a transaction open.

The whole point of the updater framework is to enable an add-in to include its modifications in the same transaction as the trigger.

Cheers,

Jeremy