Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

Model Parameter Driven UDP not mapping to individual items based on model state

mike
Enthusiast

Model Parameter Driven UDP not mapping to individual items based on model state

mike
Enthusiast
Enthusiast

We have ran into an issue over here with the UDP mapping to model state defined items.
We have the thickness parameter of a part exported and mapped to vault. Each different model state has a unique thickness. All the other variations in UDP are working correctly aside from this thickness one. The UDP shows are being correct within the vault file.

mike_0-1726836359682.png

 

But then on item creation only one of these thickness values is used for all the parts. Is this something that comes down to this UDP being driven off a model parameter? Or is there some other issue behind the keyboard I am missing?

mike_1-1726836643764.png

mike_2-1726836703214.png

@CKnische 

0 Likes
Reply
214 Views
4 Replies
Replies (4)

Gabriel_Watson
Mentor
Mentor
You'll need separate items with separate part numbers for each model state:
https://help.autodesk.com/view/VAULT/2024/ENU/?guid=GUID-A6C34246-4C97-4EC9-B3CD-79B4DCB68A52
0 Likes

mike
Enthusiast
Enthusiast

That i do have. And that is the goal. But as is the unique model states have unique part numbers. But one of the User Defined Properties is keeping the unique model state value.

In my case:

- Thickness (a model parameter used for the extrusion) is not mapping the unique parameter to the respective item

- Others are working, a User Defined Property for weight that we are using for some reason or another over the model parameter of weight.

0 Likes

Gabriel_Watson
Mentor
Mentor
I'd have to see the UDP mapping from your Vault Settings to check, but as per the link I shared above, you can see a synchronization scenario that highlights the entity type 'File' or 'Item' for the mapping, and their difference. See if you have for "Thickness" an entity type set to file where it should be per item.

mike
Enthusiast
Enthusiast

The thickness property we have mapped to both the file and the item. In both cases the document is the authority and writing one way to Vault.

 

mike_0-1727183287302.png

 

0 Likes