topic Vault Data Standard empty Dynamic Properties in Vault Customization Forum

Vault Data Standard empty Dynamic Properties

daniel_luescher — Wed, 24 May 2017 09:38:49 GMT

Hi everybody,

I noticed that in the Dynamic Properties you can't edit a property to some value, e.g. "123", and then set it to "" (empty).

The property will be set agian to the value "123". According to Vault settings it's not a "muss Feld".

Can this behaviour be changed?

Thanks,

Daniel

Re: Vault Data Standard empty Dynamic Properties

wangdu — Mon, 29 May 2017 06:40:35 GMT

Hi Daniel,

Did you have customizations of DS dialog and/or powershell scripts applied? Does this happen to all the properties visible in the Dynamic Properties grid?

If you have some changes applied, you can either check the scripts and find out yourself or post in the the relevant changes in ps1, cfg and xaml files that would help to understand this behaviour.

Wangdu

coolOrange

www.coolOrange.com

Re: Vault Data Standard empty Dynamic Properties

daniel_luescher — Mon, 29 May 2017 11:41:17 GMT

Hi Wangdu,

the posted problem only applies for Inventor, Vault works fine.

I used the out-of-the-box VDS, and an unconfigured Vault Profeffional.

The occurrence applies to all the properties.

Daniel

Inventor Professional 2017 and Vault Professional 2017

Re: Vault Data Standard empty Dynamic Properties

wangdu — Mon, 29 May 2017 11:57:51 GMT

Hi Daniel,

Are you using DataStandard 2017 Update 1? This bug seems to have been fixed with the Update 1. You should try it.

Autodesk Vault Data Standard 2017.0.1 Hotfix
https://knowledge.autodesk.com/support/vault-products/downloads/caas/downloads/content/autodesk-vault-data-standard-201701-hotfix.html?v=2017

HTH,

Wangdu

coolOrange

www.coolorange.com

Re: Vault Data Standard empty Dynamic Properties

Markus.Koechl — Mon, 29 May 2017 12:37:46 GMT

Daniel, do you have Inventor updates and VDS 2017.0.1 installed? I remember a problem in the past that "empty" iProperties had to be worked around with " ". I am no longer able to reproduce the issue in my current 2017 environment.

Re: Vault Data Standard empty Dynamic Properties

kefer_kb — Thu, 16 Aug 2018 08:38:58 GMT

Hello,

i have the same issue in AutoCAD Mechanical 2018 (2018.0.1 Update) and VDS Vers. 23.2.34.17827

If i set a filled property to empty, Independent of dynamic property area of VDS or 'my configured' property field in VDS Dialog, property retains original value and empty value would not be set!

Is this a configuration mistake or a program bug?

Please help!

Franz

Re: Vault Data Standard empty Dynamic Properties

daniel_luescher — Wed, 13 Feb 2019 10:35:41 GMT

Hi everyone,

I still have some Problems with my dynamic properties, this time with VDS 2019.

In Vault we have the property "Description" (System name). We renamed this property "Zeichnungsname" (Property name).
We mapped this property to Inventor: "Zeichnungsname" <-> "Title" (don't ask why we did this mess)
When we open an Inventor file and check the dynamic properties in the VDS-Mask, the dieplayed name of the attribut is "Titel" (seems like the Inventor property, I thought that the property informations come from Vault?).
We used "UIStrings.xml" to translate "Titel" -> "Zeichnungsname", without success. We tried this in german and english.
What did we wrong?
In AutoCAD, I create new files, define the Category. When I open the VDS-Mask (both new and opened from Vault), the dynamic properties grid does not show the properties for this category. The file "AutoCadDynamicProperties.xml" is not filled up with entries. Editing "AutoCadDynamicProperties.xml" has not effect.

Re: Vault Data Standard empty Dynamic Properties

Markus.Koechl — Wed, 13 Feb 2019 14:15:30 GMT

1) Inventor default properties can't get an override using UIString mapping. This applies only to Inventor custom iProperties. Also notice that Inventor default iProperties automatically adopt the UI language. That's the simple reason, that VDS does not apply a localization string mapping to these.

2) For AutoCAD it is different, follow these basic rules and steps to get all category properties displayed. To demonstrate I use the uggly looking AutoCAD Mechanical Title block attribute "GEN-TITLE-DES1"

Map UDP "Description" to AutoCAD file property "GEN-TITLE-DES1". Don't use another name, as the block attributes. This is key.
Add the UIString mapping: <UIString ID="GEN-TITLE-DES1">Description</UIString>
Register the block name in AutoCAD.cfg. <TitleBlock>ISO_TITLEA,ISO_TITLEB, DIN_TITLE</TitleBlock>
Register the block name at ADMS server, disable reading from prompt.

Now the VDS AutoCAD dialog will recognize, the file property "GEN-TITLE-DES1" has a corresponding block attribute and update the attribute value on Dialog close immediatly.

Re: Vault Data Standard empty Dynamic Properties

LaurenDrotar — Tue, 18 May 2021 12:30:03 GMT

It looks like I'm having a similar issue where no matter how I edit the cfg or xml file, my properties associated with my category do not appear in the AutoCAD data standard window. All properties display as expected using the Vault new file datasheet dialog, but I cannot get anything besides the default properties to appear in AutoCAD. I have already mapped all of the properties and double-checked they are correct. I've deleted the AutoCADDynamicProperties.xml, but it just keeps re-populating with the basic properties. Any advice?

Re: Vault Data Standard empty Dynamic Properties

Markus.Koechl — Wed, 19 May 2021 07:28:06 GMT

Hi Lauren,

There is no need to edit the cfg or XML file for adding properties to a category listing. The critical setup is the mapping. Did you follow or compare your steps with the step-by-step instructions given in the VDS Tutorial, Chapter 04? Based on the given details, this is the only advice I can do for now.

Re: Vault Data Standard empty Dynamic Properties

tech — Thu, 20 May 2021 12:33:01 GMT

It would appear that my issue lies in the fact that I do not have file properties set up on these templates, only block attributes, so for new file creation, it sounds like the data standard dialog will not recognize this? Aside from the file property mapping piece, I have completed all other steps.

Re: Vault Data Standard empty Dynamic Properties

Markus.Koechl — Thu, 20 May 2021 16:28:03 GMT

It is required to have a file property mapping as primary mapping. The block attribute mapping is the secondary. And as documented in the tutorial, ensure that the file property name matches the attribute name.