Make Parametrically Driven Properties Visible but Read-Only in Inventor Data Sheet

[pmartick]

Inventor Professional ver. 2023.4.2 and Vault Professional 2023.4.2

I am learning about and working on customizing Vault Data Standard to be used by my team.  On some of our templates the Part Number and Description are parametrically driven:

When they are parametrically driven, the property becomes Hidden in the Vault Dynamic Properties Grid/Datasheet in Inventor, but still visible in Vault.

(Description should be between Part Number and Wear Part)

In case anyone asks, I do have the Description property mapped to this Category in Vault and have it listed and set to visible in DynamicProperties XML files:

Can someone point out where the logic is that automatically determines parametrically driven properties to be hidden?

I've seen on some older forum posts that making a property Read-Only in the dynamic properties grid is not possible.  Is that still true today?

The best case scenario is to make the parametrically driven properties visible but read-only.

If this isn't possible then I'll take a look in the Ideas forums to help make this possible.

Thanks for your help.

[Markus.Koechl]

You can set Dynamic Category Properties ReadOnly or disable editing by extending the XAML file. You can review a sample for both here: VDS-Sample-Configurations-2024/VDS-MFG-Sample/CAD.Custom/Configuration/Inventor.xaml at master · koe.... Navigate to line #132 for ReadOnly or line #107 for IsEditable.

[pmartick]

Those 2 things are good to know for the future. It seems to be an all or nothing approach if I can't change the ReadOnly or IsEditable variables dynamically via the dynamic property xml files or programming it in the powershell script.

None of these that I tried worked in the powershell:
$dsWindow.FindName("Part Number").IsReadOnly = $true
$dsWindow.FindName("Part Number").IsReadOnly = "True"

So this may be useful for properties you want on permanent read-only and only changed via programming or admin-only purposes.

What about the initial problem of making the property visible when the iProperty is parametrically driven, is there no way around that?

[Markus.Koechl · Accepted solution]

Hi @pmartick, I am sorry I missed getting back on your latest question/line: there is no workaround to hide these driven properties, it is "hard coded". So I suggest submitting an idea post.