Dear Tuuletin and Michal,
Thank you for your patience.
The development team responded to the issue REVIT-99069 [Isolate elements on a newly created view -- 12169975] and say:
I can reproduce this issue. When just 1 transaction is used to create the new view and also to isolate the element, then the isolate element fails.
However, I can get the desired behaviour using two separate transactions as follows:
- Use a transaction to create the new view. Close transaction.
- Activate the new view. This is important; isolation fails if the view is not active.
- Use 2nd transaction to isolate the wall. Close transaction.
Is this an acceptable workaround?
Note: I also tried the attached file and macros in our internal development release cannot reproduce the behaviour there.
I tested macro "test 2" which uses just 1 transaction to create the new view and isolate the wall, and when the screen updates the single wall is really and truly isolated in the new view.
So the workaround described above will not be needed forever.
I hope this helps.
Best regards,
Jeremy