Goemetry change updater not firing for Elements of Type Topography

Goemetry change updater not firing for Elements of Type Topography

grahamcook
Advocate Advocate
659 Views
3 Replies
Message 1 of 4

Goemetry change updater not firing for Elements of Type Topography

grahamcook
Advocate
Advocate

Hi

 

I have found that adding an Update Trigger with change type Element.GetChangeTypeGeometry() to a Topography element does not fire when it's geometry is changed.  A workaround is to use Element.GetChangeTypeAny() buts that's not really an option in this case as it causes the updater to fire to many times.  Surely adding points to a Topography or changing the boundary of a Site Region constitutes a Geometry Change?

0 Likes
660 Views
3 Replies
Replies (3)
Message 2 of 4

jeremytammik
Autodesk
Autodesk

Dear Graham,

 

Yes, indeed.

 

I have heard of similar issues before.

 

Please submit a complete minimal reproducible case that I can pass on to the development team for you:

 

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

 

Thank you!

 

Cheers,

 

Jeremy



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes
Message 3 of 4

grahamcook
Advocate
Advocate

Jeremy

 

Here's a Revit file with an embedded macro that illustrates the problem:

 

1. Open file.

2. Macro Manger.

3. Select and Run Macro SetUpdaterAny

4. Modify the topo points or the boundary of the Site Region Object (Element 300817)

5. Updater is firing on all cylinders

6. Macro Manager

7. Select and Run Macro SetUpdaterGeometry

8. Modify the topo points or the boundary of the Site Region Object

9. Updater not firing 😞

 

Attached mp4 shows those steps.

0 Likes
Message 4 of 4

jeremytammik
Autodesk
Autodesk

Dear Graham,

 

Thank you for your nice and complete sample material.

 

That sounds perfect!

 

I logged the issue REVIT-128421 [IUpdater with GetChangeTypeGeometry trigger does not fire on Topography element] with our development team for this on your behalf as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.

 

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

 

This issue is important to me. What can I do to help?

 

This issue needs to be assessed by our engineering team and prioritised against all other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

 

  • Impact on your application and/or your development.
  • The number of users affected.
  • The potential revenue impact to you.
  • The potential revenue impact to Autodesk.
  • Realistic timescale over which a fix would help you.
  • In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

 

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

 

Cheers,

 

Jeremy

 



Jeremy Tammik
Developer Technical Services
Autodesk Developer Network, ADN Open
The Building Coder

0 Likes