Item category assignment rule based on Primary File (extension)

Item category assignment rule based on Primary File (extension)

sbrandsen
Contributor Contributor
2,603 Views
4 Replies
Message 1 of 5

Item category assignment rule based on Primary File (extension)

sbrandsen
Contributor
Contributor

Hello,

 

We are switching to Items based management instead of files.

Is there any way to automatically assign an ITEM category based on the Primary file extension?

 

I know this is possible in File categories:

sbrandsen_0-1711105032673.png

It's not there in Item rules: 

sbrandsen_1-1711105113484.png

 

Other things I've tried:

  • Using the Item Name Property. It does not include the extension in Items
  • Assigning a Category to the File and then using this value, it chooses the assigned item category, not the files.
  • Creating a Custom Item property "IsSoftwareCategory", and then choosing Provider other items, my extension is zap, so doesn't fit the standard providers, hoping it would have a file property "Filename". But it doesn't: sbrandsen_2-1711105488449.png

     

 

FYI: Assembly, Part, Purchase and DWG files seem to have a not very well documented built in type for assigment based on primary file type, thats how these automatically get assigned properly. I don't know if its possible to add types to this:

 

  • Assembly: Property Type is assembly
  • Part: Property Type is part
  • DWG: Property Type is document
  • Purchase: Property Type is purchase (This comes from the BOM structure type in Inventor, also Content Center items seem to have this automatically)

 

Am I missing something or is it just not possible?

0 Likes
2,604 Views
4 Replies
Replies (4)
Message 2 of 5

CGBenner
Community Manager
Community Manager

@ihayesjr 

This feels like it should be possible in two steps.
 

1. Change the File category to (ex) Part (or set it on creation using a rule)

2. Create an Item Rule based on Category Name to set Item Category to (ex) Parts

But Item Category doesn't seem to change based on a Rule upon Assigning the Item, is this correct?  It's been a long time since I've done this, I'm sure I missed a step somewhere!  😂

 

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M


0 Likes
Message 3 of 5

sbrandsen
Contributor
Contributor

Thanks for the reply,

 

Unfortunately it seems like it does not look at the FILE category at all:

sbrandsen_1-1711116129629.png

I've set the file category to Software. Then with the rule read the Category name Software.

But I think when assigning it looks at the Item Category Name, not the FILE one...

 

sbrandsen_2-1711116214013.png

 

This results it my default category, which is Part Item

sbrandsen_3-1711116227388.png

 

 

0 Likes
Message 4 of 5

ihayesjr
Community Manager
Community Manager

@sbrandsen 

You will not be able to perform what you are asking for files which Vault cannot read file properties.

I will try to explain.

Vault has what are called Property Providers. These providers enable Vault to ready standard and custom properties inside of the file. For your Zap file, there is no property provider and therefore it can't ready any of its properties. 

As you have already tried, the Item rule is only going to look at Item properties to set the category.

You would have to push a file property into the Item property for it to run the rule and set the category you want. 

 

For example, Vault now has a property provider for PDF files. You have the ability to push the PDF file property into an Item property. Then create a rule which looks at the Item property and set the category. 

In my example below, I am extracting the Title property from the PDF into the Item Title property.

Then I created a rule that looks at the Item Title property for containing "pdf."

I make sure that the Title in the PDF contains PDF and assign the Item. 

The assignment then sets the proper category. 

I cannot do this for a JPG, because there isn't a JPG property provider.

ihayesjr_1-1711124044912.png

 

ihayesjr_0-1711124002889.png

 

 

Hope this helps.

 




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 5 of 5

sbrandsen
Contributor
Contributor

Ah ok thats too bad. Thanks for the explanation

 

Seems like it should be possible. Item based management without this is not viable for files other than the provided ones.

 

sbrandsen_0-1711354258819.png

It would be perfect if they added the option to just bind to the source filename, as this data is already available (even in the same screen)

 

If I ever find a workaround I will post it