BIM 360’s “Last Updated” and “Updated By” columns are not reliable. Why though?
The “Last Updated” date is modified whenever the file undergoes actions such as publishing, renaming, moving, copying (the pasted file reflects the date of pasting), or when a description is added. Essentially, any alteration to the file triggers an update to the “Last Updated” date. This functionality diverges from the behavior observed in Windows and is strongly undesirable. We aim to avoid the date updating with every routine action that does not pertain to the data’s integrity. For instance, if the model was last updated a year ago but was recently moved to a new folder today, the “Last Updated” date would display today’s date instead of the actual last update date, which should be one year ago.
Please note that syncs do not refresh the “Last Updated” date for cloud models; instead, publishing the model will update this date.
Similarly, the “Updated by” column does not accurately reflect the last person who made a change. For instance, if a file is moved to another folder, the “Updated by” column does not show the user responsible for the move.
Although these discrepancies could potentially point the finger at the wrong person, it’s important to recognize that most users may not be looking at these columns. However, for those who do, it’s advisable to take these columns with a grain of salt.
0 Comments