Vault property change will delete 'fx' property expression?

[checkcheck_master]

When I change/modify the value of the Description property via Vault, the 'fx' property expression disappears.
I hope this is not the intention, am I doing something wrong?

[CGBenner]

@checkcheck_master 

Let me see if I understand.  You have the Description iproperty in Inventor set up with an expression.  Inside Vault, you manually change the description property value and then push that down to the file.  Is that about right?

Can you share what the expression is that you have on the Inventor side?

[checkcheck_master]

Thank you for your response.

For example, something that is purchased at a certain length and made to length in a project.
The Description in Inventor for such a component can then be:
'=Cable Tray L=<d0> (from L=3000)'
Resolved: 'Cable Tray L=1300 (from L=3000)'

Editing that Description in the BoM editor leaves the Parameter link intact.
Copy Design such a component in Vault ditto.
We did have trouble with this, which we have overcome through:

https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles... 

[CGBenner]

@checkcheck_master 

I think that what you are seeing is actually correct.  An expression entered into an iproperty is still text, though it reads other parameters and changes the value of the final string.  So when you manually enter a value for the property in Vault and then synchronize properties with the CAD file, it interprets that as a text change, and it does not care that what it is overwriting is an expression.  I think the best advice in a situation like this is to just not change that value in Vault at all.

@ihayesjr does this sound like a good explanation? Anything I missed?

[checkcheck_master]

Thanks again for your response.

I see a 3D CAD Program with the possibility to enrich properties with data from parameters.
The tool to manage the data, Vault, with the ability to deeply manipulate those properties, does not seem to notice it, nullifies them by definition.

I'm talking from practice, a company where Engineering is building a library that is managed via Vault and where, for example, colleagues from Purchasing add their value to the various components.
With regard to 'Just not change that value in Vault at all' I see considerable limitations.

How can this be set up in a good way?
Can it be made visible in Vault when there is a linked property?
Can certain properties only be made accessible to certain people/applications?
Your advice please.

[ihayesjr · Accepted solution]

@checkcheck_master @CGBenner 

Sorry for responding late.

Technically, the value of the iProperty is the formula. Therefore if you edit the iProperty in Vault, it will erase the formula and put in the value you specified. 
This is similar to editing the property in Inventor, you have to edit the formula or it will be replaced with the value entered.

If the formula must stay, the property mapping should go in one direction, from File ->Vault. That way a user cannot edit the property inside of the Vault Client.

The reason this looked like it worked for the BOM edit is that you are editing the BOM which contains the value retrieved by the formula in the BOM, not the iProperty.

For Copy Design, as long as you don't have a rule that changes the iProperty value, the formula is not removed.

[checkcheck_master]

Thanks for your clear explanation.
So we need to properly set up the property assignment in the Vault.
Could you please help me where I can find that in the Vault settings?
Thanks in advance.

[ihayesjr · Accepted solution]

Tools -> Administration -> Vault Settings -> Behaviors tab -> Properties

Edit the Description property

Select the Inventor Mapping as shown by the red box in the image below.

[checkcheck_master]

Very nice, thank you very much for the quick response.

I'll take the liberty of asking another question.
In Vault Copy Design you can choose 'Copy All Properties' or 'Default Rule Set', see picture.
We would like to use the latter option as default but do not know how to set this.
I looked here but again I don't know where to find this:

https://knowledge.autodesk.com/support/vault-products/learn-explore/caas/CloudHelp/cloudhelp/2021/EN... 

---------

Now I'm getting a little embarrassed on my cheeks but I'll do it anyway.
This post has helped me on my way but I would like some more depth regarding the following.

https://forums.autodesk.com/t5/vault-forum/how-to-prevent-vault-folder-to-check-out-set-permissions-... 

In short, we are misusing a project folder as our Library and would like this folder to behave as if it were the Vault Library.
I mean that a normal user cannot check out the files, they are not updated so no green dots and that administrator rights are then needed to be able to access the files.

Are we on the right track with regard to the previous post and if not can you add something to it?

I look forward to your response, thanks again in advance.

[ihayesjr]

For the Copy Design question.

First, it looks like your menu is not set to the default settings and you are missing a button.

1. Launch Copy Design
2. Next to the drop-down click the button indicated in this image.
   
3. Click the Reset Toolbar option
   
4. Click the Define... button
   

[ihayesjr]

For the Folder question.

You should set the Administrators group to have all access and the Everyone Group to have Read and Download access like the following image.

[checkcheck_master]

@ihayesjr

Hello,

Regarding 'In Vault Copy Design you can choose 'Copy All Properties' or 'Default Rule Set', see picture.
We would like to use the latter option as default but do not know how to set this.'

I just found the answer, it's at Copy Design options.

[checkcheck_master]

Sorry missed your answers.

[checkcheck_master]

Thanks again for the quick answer.

I think I set it up this way before and had colleagues who didn't have access to the 'Library'.
Could it be that the 'Everyone' group is not set up correctly?
In other words, everyone doesn't belong to the Everyone group by definition/default?

[ihayesjr]

The Everyone Group is a system group that cannot be modified. Everyone belongs to the Everyone Group always.

[checkcheck_master]

Thanks again.

I set it up this way but it looks like the 'locking' is only for files who are released.

We have lots of files who are still in 'Work In Progress'.

Is there a way to lock also these files?

[checkcheck_master]

@ihayesjr 

Hello.

Is it possible to have 'Work in Progress' files locked?

[ihayesjr]

@checkcheck_master 

You can lock a file in any state the same way you lock the files in the Released state.

Change the security setting in the Security tab of the Work in Progress state.

[checkcheck_master]

@ihayesjr 

Thanks again.
I wanted to say, am I right that this applies to all Work in Progress files?
If so, I mean to apply this to the WIP files inside the restricted folder and not outside it.
In other words, all files within the restricted folder cannot be checked out.

I see that at Category you can choose Folders.
I just don't see how quickly I can choose a specific folder, in this case the project folder that we are misusing as Library.

[ihayesjr]

@checkcheck_master 

If you change the security setting on a File Lifecycle Definition, the security will be set on all files in that state regardless of the folder they are in.

So you may want to have the same Lifecycle Definition on all files but control who can modify the files in the folder by the folder level security.