Anybody using this?
Pros and cons?
Hi Thomas, this new enhancement allows you to update your reference presentation attributes from those of the source saved view and to push changes you may have applied to the referenced view to the source. It does work and the pros and cons could depend on how it would fit in your workflow.
Product Manager, MicroStation
Bentley Systems intl
Your wording makes me unsure.
Update from Saved View - I assume is from SV in Composition Model to Drawing (in case any is changed)
Accept changes and Push to Saved View - should be the opposite> You have changed the level mask in the Drawing and can push this back to the original SV in the Composition Model.
Q1 - accept what changes? Level mask in what view?or which SV?
Q2 - what workflows will make use of this?
regards / Thomas Voghera
that is what I meant, you basically have a "two way" sync with a referenced saved view: you can "pull" into your master file changes made to an attached saved view presentation settings and you can "push" to the source saved view the changes that you may have done in a referenced instance of it.
Maybe the documentation, which I am sure you have already read, explains it clearer than my attempts :)
Update From Saved View — Updates the reference´s view attributes to match the source saved view´s view attributes.
Accept Changes and then Push to Saved View — Saves the changes in view attributes to the source saved view.
Q1: changes to view presentation attributes that are generally saved into a saved view.
Q2: I can't really give a recommended workflow but it could suit some practices. For example: let's say you have a saved view referenced into a file, you think it's not exactly 100% as you want it so you start manipulating the view in the master file until you get it as you really want it. You can use the push function to save the changes to the original source saved view so that his will be available to other files/users, who would only have to use the "pull" functions to update their files.