Updaters and Workshaing

[Anonymous]

As we have previously discussed, Updaters are not called in response to reload latest.  However, I'm experiencing that the registered deletion updater is in fact being called just after RL.  The registered addition and modification updaters are not.

This is just a heads up for anyone trying to wrangle worksharing.  This is being seen in Revit 2016

Can anyone else confirm or deny that they are seeing this as well?

[jeremytammik]

Dear Ken,

Thank you for pointing out this interesting, slightly weird and possibly worrying fact.

If you would like to provide a reproducible case to prove it, I will happily pass it on to the development team for analysis and verification that this behaviour is in fact expected... or not, as the case may be:

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

Thank you!

Best regards,

Jeremy

[Anonymous]

Hi Jeremy,

Here is a reproduction test app similar to the one I posted for the checkout issue.

Reproduction: (assuming app is installed/setup)

1. Create a new file, enable worksharing, save, SWC relinquish all

2. Become user 1, open central with create new local option,  create a beam, SWC

3. Become user 2, open with create new local option, delete beam, SWC

4. Become user 1, open local file, reload latest -> deletion updater called.

Note, that I added a check.  When the deletion updater runs you will be asked if you deleted the bar locally or have just reloaded latest.  Just wanted to be able to flag the situation.

Hope you're able to reproduce this one too

Thanks,

-Ken

[jeremytammik]

Dear Ken,

Thank you for your reproducible case and nice, clear, succinct instructions.

I logged the issue REVIT-86348 [API: reload latest trigger deletion updater but not addition and modification updaters] 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 us with additional information at any time quoting the change request number or this case 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 of the 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.

Thank you!

Best regards,

Jeremy