Transfered from EAP Ideas list
Option for the CVE's to be stored in the Drawing model or the Sheet model or the `root container` model at the top of an assembly of deeply nested attachments?
Indirect CVE update: It would be good to have the option to retain the old CVE in the Drawing model, and store the indirectly triggered update as a revision, if the CVE is re-generated in the Drawing model. I can see a lot of users using CVE's as a means to insulate their print-ready stuff from changes and tidy-up that would be needed in Mstn's 'everything is live and uptodate, no duplication' way of referencing information.
CVE proxy update in the Sheet model: maybe there should be an option to force CVE to be re-generated in the Sheet model as a 'proxy' and bypass the Drawing model(s). This would be in many ways 'cleaner' and more like the way Refs behave already. Down side would be that there would be multiple versions of the cached information, and duplicated re-generation costs. But, I think this would be expected and mirror what happens with Ref's anyway..

https://communities.bentley.com/products/betas/microstation_early_access_program/f/343352/t/98557.aspx