enforce property set on a category change

[Gene.R]

 I would expect that the property set of the new category would be applied during the the category change, or at least a pickbox to force the new property set. currently you have invoke a separate command Add/Remove properties to bring them in or remove them.

[RajSchmidt]

At least add all new properties. I guess it might be difficult to remove them.

[Frodl]

Hi vault team,

we define for each new project a specific category for this project. So, we have separate file categories in each project.
With the file category we define which properties will be used in the files in the specific project.
Also, we use copies of files from old projects.

Now, if we change the category of a file with different properties, the new properties will be added. But the old one ad not needed any more are still in the file.

It would be very helpful, if it will be possible to clear the properties in the file.
And / Or that automatically only that properties will be used in the file which are definition in the category.

In the forum you can find the solution to delete or add properties to a file manualy.

Gelöst: Re: Hide/Delete Property for Category - Autodesk Community

This should be work by the settings in the category.

[ihayesjr]

@Frodl 

Thank you for posting the idea. If you are using Copy Design for the copies into the new project folder, you can clear out the properties from the old category.

[Frodl]

Hi Irvin,

thank you for the notice. That helps us when we copy a project.
But some times we change the definition for used properties in the category in a running project. For this it would be very helpful, if the changes will be applied to all files with this category. Otherwise each file (that can be more than 500 drawings) have to edited manualy.
Best regards
Stephan

[Gene.R]

All,
It's great to see some support gathering, much appreciated.
My original Idea was for Item workflows, but I see how this would also be beneficial for Files and Folders.

I have rules that set the Item category on file assignment, this works great for the most part.
We also from time to time will reserve a block of numbers with a default category without any properties, users then later picks a category and it pulls in the assigned properties, sometimes is the incorrect category, so they change category and then it pulls in additional properties, if changed again it pulls in more properties and then you end up with numerous non-pertinent properties in the item and have to invoke the add/remove command to remove the offenders.
As an administrator I find myself correcting existing released items to correct the property sets.

If the file has the wrong property value that is propagating into the item well then that is much more intrusive.

change item state to "quick-change"> edit file properties>update item>Save Item>add/remove>select properties>select OK>save>change state>repair stored ERP Item links.

Here are some suggestions:

• add a tickbox to change category dialog to remove the old category unique properties, keep the shared properties, and add any new unique properties of the new category.
• add a tickbox to add/remove dialog to do the same as above.
• right click on multiple items to do the same as above.
• administrative role for unconditional corrections for properties and categories.
  • no change in state
  • no change in version number

Gene