Error message and pink color items in screen after changing some values

[Mehdi_Sajjadi]

Hi everyone,

I have made some changes in DNP3 variables, but after saving the page ,all items turn to be pink and non-functional. It shows me a message about overwriting on server before saving, but I cannot remember what was that. 

I have attached screen shot of page. 

Any idea how I can fix it without needed to redesign the page?

Thanks in advance

[_Experimentalist_]

Hi

This colour usually indicates bad quality data. You can verify if this is the case for your system by selecting the 'Edit Color Palette' menu item from the context menu of the root node of the Database tree view in ViewX. Don't worry as you can cancel out of the dialog without actually editing anything.

[AdamWoodlandToo]

It shows me a message about overwriting on server before saving, but I cannot remember what was that. 

---

This usually happens when someone or something else has also modified the mimic since you opened it. Usual culprits are other users also saving the mimic, an embedded mimic or object being moved in the database causing the server to automatically update references server-side, or logic running updating properties (although that last one is more common on object properties rather than mimic content).

Most likely the second case, someone moved what you're referencing and then you tried to save the mimic and it rereferenced an invalid object.

Check the animations for those pink boxes, they should show what they reference and then check them against the database itself and hopefully it should be obvious what moved/deleted/changed.

[Mehdi_Sajjadi]

Thanks Adam

Yes, I have moved some of DNP3 variables to another group and after showing warning message, and saving changes, I notices that those variables turned to pink. 

so, regarding what you mentioned in above, even if I found out which items moved, is there any way to fix the issue without deleting defectives items?

Regards

[geoffpatton · Accepted solution]

You really have two options.

Move the points back to where they were originally and the mimic should work fine. I usually make a minor edit and save it again. Then close the mimic and move the items back to their new location and the paths will be dynamically updated.

The second option is to edit each object on the mimic that has a problem. You can manually update the Animations and the Pick Actions. This option can be a bit time consuming and it is easy to miss updating a Pick Action so double check those. You do not have to browses to each item to correct them you can just type in the new database location. I get one animation right and then copy the common part of the path and just paste it on the rest of the Animations and Pick Action for an object. Also remember that Pick Actions do not use the " in their paths.

[Mehdi_Sajjadi]

Thank you so much Geoff. Very helpful 👍