# Explain: "Override changes with current model" **URL:** \ **Category:** General\ **Created:** [May 26, 2026, 2:55pm UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258 "2026-05-26T14:55:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\ **Post date:** [May 26, 2026, 2:55pm UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/1 "2026-05-26T14:55:16Z")
To me, the explanation behind the ‘i’ button is not clear. Please explain better what this toggle does do: ![image](https://canada1.discourse-cdn.com/flex011/uploads/qonic/original/1X/247cdc6d1373816cec3bca10b4ed9a346678f871.png) ---
**Author:** ![Jacob\_De\_Sutter](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/jacob_de_sutter/32/9_2.png) [@Jacob\_De\_Sutter](https://community.qonic.com/u/Jacob_De_Sutter)\ **Post date:** [May 27, 2026, 7:40am UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/2 "2026-05-27T07:40:08Z")
Hi Johan, By default, when the toggle is **off** , changes made in Qonic will be merged with the uploaded revision. So if you upload a new _model\_v1.ifc_ in Qonic, then make some changes to this model in Qonic, and then upload a revision _model\_v2.ifc_, the changes made in Qonic will be applied to this new version v2 (or to put it more correctly: the diffs between _model\_v1.ifc_ and _model\_v2.ifc_ will be determined and these diffs will be merged with the changes that you applied in Qonic). When this toggle is **on** , the model wil be overwritten by the newly uploaded model. Any changes made to the model in Qonic will be lost. It’s effectively the same as uploading this file as a brand new model in Qonic, but with the added benefit that you still retain the model’s version history so you can still do things like version compare. I hope this clears things up! Jacob ---
**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\ **Post date:** [May 27, 2026, 10:51am UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/3 "2026-05-27T10:51:04Z")
So it could also be called “dismiss unpublished changes” with the toggle on/off reversed? Maybe simply adding “unpublished” to the current name of the toggle could be a good clarification? ---
**Author:** ![Jacob\_De\_Sutter](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/jacob_de_sutter/32/9_2.png) [@Jacob\_De\_Sutter](https://community.qonic.com/u/Jacob_De_Sutter)\ **Post date:** [May 27, 2026, 2:56pm UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/4 "2026-05-27T14:56:07Z")
This is unrelated to published/unpublished changes. What I meant is: when this toggle is enabled, you **overwrite** the model completely, that means also changes you have published earlier. As explained earlier, it’s basically uploading this file as a new model, and putting it on top of the previous models’ version history. ---
**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\ **Post date:** [June 4, 2026, 1:15pm UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/5 "2026-06-04T13:15:29Z")
OK, I think it is clear now. Maybe in the past I understood it would automatically ‘solve conflicts’ by using the new model upload as primary. And that’s why it didn’t behave as I expected. ---
**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\ **Post date:** [June 23, 2026, 9:00am UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/6 "2026-06-23T09:00:43Z")
I think I found the reason again why I didn’t think this was the way it works. I just updated an IFC model as a revision and thicked the “Override changes with current model” for that revision. But I still have “Sync Issues”. Which shouldn’t be possible if the revision overrides all previous changes, right? ---
**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\ **Post date:** [June 30, 2026, 7:24am UTC](https://community.qonic.com/t/explain-override-changes-with-current-model/258/7 "2026-06-30T07:24:36Z")
Another example of this today: - Yesterday I made changes to a model. I deleted some beams and replaced them with a copy of another beam - Today we want to replace the entire model (all beams were sized incorrectly). So we thick the “Override changes with current model” - Result is: - Many sync issues =\> we selected to use all of those from the new upload. But we shouldn’t have to with that toggle on, right? - The “new” beams that I created yesterday (by copying) are still there, overlapping with the new ones from the latest upload (in correct sizes…)