Hello,
I am trying to hide pipe specs in design by unsetting the stext of text element pipe specs and also deleting the text element. But it always appears in edsign module and is fully usable.
How can i get around this problem?
Thanks in advance
Hello,
I am trying to hide pipe specs in design by unsetting the stext of text element pipe specs and also deleting the text element. But it always appears in edsign module and is fully usable.
How can i get around this problem?
Thanks in advance
You need to enable the Restricted attribute of the SPEC in order to hide that piping SPEC in design so that the users will not be able to select it in the Create Pipe form, Modify Pipe form, Spec/Bore form etc.
Existing piping model that uses the piping SPEC that you just restricted will now return a warning mesage in the data consistency check, I think. The user still need to reselect to new piping SPEC for those existing piping model.
Thank you for the helpful sugegstion. It works perfectly well.
I am glad to hear that it went well.
Just remember to ask your users to restart their AVEVA E3D Design, or perform a "Reload Specifications".
yes . For sure
Thanks again
Could you please explain what to do in case of Structural specification. I wish to add some new Structural Spec in to default window.
Hello,
What are the values in the Purpose attribute of your SPEC and SPWL?
I see, STL is the correct purpose attribute. So I am not sure why it is not appearing.
Can you show a screenshot of the default window that you mentioned?
Can you also check the Description attribute of your SPEC? I think that each SPEC should have unique Description attribute to properly show in the Properties form.
BTW, where is the location of restricted attribute?
how about if the spec is DB read only? any suggestion?
Hello, Restricted is an attribute of a SPEC element. By default, it is located in the bottom in the Attribute window and you have to scroll down to see it.
There are several possible situations if your spec DB is read-only. The best option is talk to the admin who manages those DB, since there might be reason why it is set as read-only.
One possible course of action to make an editable project copy of that read-only DB if it is a foreign-include DB. You still need to coordinate with the admin who manages your reference projects where that foreign-include DB is located.