When reference is changed - is it possible to display what has changed before reference update?

You might like to consider using Design History as an option to show changes that have occurred in your files.

What Is Design History?

Working With Design History In MicroStation V8

One way without design history and without projectwise versioning is to implement some rules / discipline that if you must change a reference file  you have to save as in a superseded folder and  put a version number or date infront so that  you can keep old and new alive .. but where the xref has been used will stay ref attached and you only make changes to the current xref... and as its not renamed it can have the previous version ref attached  and hilight on and you can see the changes ...

oh I forgot another way I used a long time ago in a previous role...

You can copy the default model inside the same file and name it with a date or Version No or a simple short description like Option A.

The default model then is the one that is ALWAYS the current  modified  version and is attached to all your plan sets and to see the changes you can self reference the duplicated original pre changes model  into the active default model with highlight set in ref manager .. this is  a very  easy way but it does make your files bigger and bigger but so does history option... but this way does save having a superseded directory.. I have used this method for optioneering  and have various models in the same file for default ( which is always current  on do not change it from default)  , option B, option C etc   very easy  to swap out which option become the current version to use later ...

One way without design history and without projectwise versioning is to implement some rules / discipline that if you must change a reference file  you have to save as in a superseded folder and  put a version number or date infront so that  you can keep old and new alive .. but where the xref has been used will stay ref attached and you only make changes to the current xref... and as its not renamed it can have the previous version ref attached  and hilight on and you can see the changes ...

oh I forgot another way I used a long time ago in a previous role...

You can copy the default model inside the same file and name it with a date or Version No or a simple short description like Option A.

The default model then is the one that is ALWAYS the current  modified  version and is attached to all your plan sets and to see the changes you can self reference the duplicated original pre changes model  into the active default model with highlight set in ref manager .. this is  a very  easy way but it does make your files bigger and bigger but so does history option... but this way does save having a superseded directory.. I have used this method for optioneering  and have various models in the same file for default ( which is always current  on do not change it from default)  , option B, option C etc   very easy  to swap out which option become the current version to use later ...

Design History

Andrew Bell suggested Design History.

Andrew Bell said:

Working With Design History In MicroStation V8

Is there a version of that Wiki for the CONNECT era?

Lorys said:

You can copy the default model inside the same file and name it with a date or Version No

You've described a manual implementation of Design History.

Barry Lothian said:

An option to consider which I use for comparison is to save a copy of the file in its original state, then reference it into the file where you are making the changes and use Level Overrides with 2 colours to visually differentiate changes between files

Another manual implementation of Design History.

Ivan Galik said:

Is something like this possible in Microstation?

What is the exact version no. (e.g. v10.x.y.z) of MicroStation that you are using? Use key-in VERSION to see the version no. in the MicroStation Message Center, or Help→About MicroStation in the backstage.

See this blog that shows you how to obtain MicroStation's version number.

latest Microstation connect.

We use comments when changing something and checking in inside projectwise but it is dependent on a user and you only see text thats something has changed but user needs to see visually what has changed. if i move one pad footing out of hundred 5cm in one direction i leave a comment "i have moved a pad" but the user referencing my model needs to also spot it visually. Does design history enable this? like clicking on the history record whos whats has been added/modified, etc. ?

All other proposed workarounds from other comments are unfeasible, no manual copying and comparing is the option. I am talking about dedicated tool to aid the designer.

In project wise we use versioning only for major changes. During design process in the early phases there are many changes within a day, its impossible to create new version all the time, there would be thousands of them eventually. 

Ivan Galik said:

Does design history enable this?

What can I write that isn't in MicroStation help?

There are a number of viewing and recovery options. You can:

• Track all committed changes
• View changes before and after
• View changes on an element level
• Select changes via a list filter
• Undo historic changes
• Redo historic changes
• Restore revisions by date and number
• Return to element changes within revisions

That's a large topic.

Ivan Galik said:

I am talking about dedicated tool to aid the designer.

Design History is that dedicated tool.

It seems promising. I will test it. Thanks

Jon Summers said:

Another manual implementation of Design History.

Let's be clear, my suggestion may be similar to a feature of Design History, but its not the same whatsoever.

Design History's implementation of highlighting changes to elements that are either New/Deleted/Modified is not the same as my suggestion. My suggestion is a 'broader strokes' approach that can be used in all situations, whereas Design History cannot.

• Design History does not let you select the highlighting colour scheme a user may want to use on the fly, you have to instead predefine values in MS_DESIGN_HISTORY_COLORS.
• Design History increases files sizes significantly (compared to the original file)
• Design History is prohibited for use with ProjectWise where file versioning is already a core feature (at least, it has been on every PW hosted project I have ever worked on)