cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

tag update dialog box with conflicting tags

tag update dialog box with conflicting tags

The idea came from this forum post:
https://forums.autodesk.com/t5/autocad-plant-3d-forum/ask-to-replace-tag/m-p/13209722#M72461

Sometimes when I assign a TAG, it asks me to choose another one or give the TAG to this piece of equipement. That is good, but rare.

 

But otherwise it just displaying an error saying the tag is already used, which is a very limiting way of showing this data. You don't know which is the other component. A dialog box could open up here to let you fix the scenario.

 

MichielValcke_0-1734092163877.jpeg

There are basically three scenario's
The tag of the original component is correct, you change the tag for the current component

The tag of the original component is wrong, you change the tag for the original component and can then confirm the chosen tag for the current component.
The tag is not used by a component and only exists in the database tag registry. You have to clean up the database.

I think it would make the software more user friendly and make it feel more powerful if you had an interface or dialog box at that point that allowed you to edit both tags. It would allow you to change the existing component's tag and continuing with yours, but it would also help with catching erronuous tags in existing components and general understanding of a project if you can actually see which component has the conflicting tag. I can see a lot of *Oooh, Right ...* kind of moments to be had.

There's also the case where a tag can exist in the PnPTagRegistries table of the processpower database after Plant 3D experienced a crash, but there is no actual component with that tag in the database. It will cause the above error, but if you don't know what's happening it can be hell to figure out how to fix it. 
The dialog box would be able to check and see that the tag only exists in the tag registry but has no component linked to it and would give the user the option to either remove it from the registry, or reassign it to the current component or pick an untagged component of the same class to link it to.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea