topic Assign/Update Items is different via API then UI in Vault Customization Forum

Assign/Update Items is different via API then UI

Majjek — Mon, 25 Sep 2023 08:31:39 GMT

Hello,

In this example I've got an Inventor file with part number 12345 checked into the Vault.

There's also an existing Item with with Item number 12345.

When I use the Assign/Update Item command via the UI in the Vault client, the file will get linked to that existing Item as a secondary link (as I would expect).

But when I use the API function to Assign/Update an Item (via the link below), it will create a new Item (with a different number), instead of linking it as a secondary link to the existing Item.

Is this a separate step that needs to be done first if I do this via API?

Or am I missing something?

https://justonesandzeros.typepad.com/blog/2014/04/assigning-a-file-to-an-item.html

Re: Assign/Update Items is different via API then UI

Markus.Koechl — Mon, 25 Sep 2023 09:32:24 GMT

You need to set the option autoAssignDuplicates to true. The API call is independent of the Item assignment setting in the behavior configuration.

Re: Assign/Update Items is different via API then UI

Majjek — Mon, 25 Sep 2023 09:56:26 GMT

Thanks Markus, so simple...

Re: Assign/Update Items is different via API then UI

Majjek — Fri, 29 Sep 2023 13:36:19 GMT

@Markus.Koechl I do have another issue.

When I have an assembly and perform a Promote action on that assembly file alone, I can see the the associations with (3) underlying parts are created correctly in the ItemsAndFiles object (with the ItemAssignAll setting set to Yes).

But when I select all 3 underlying parts and the assembly in 1 Promote action, I can see all items are created, but not all associations to the children, only 1 association to 1 file is created..

When I commit the Item, I can see in Vault that the 2 other rows are disabled in the Item.

Any idea what' causing this?

Re: Assign/Update Items is different via API then UI

Markus.Koechl — Tue, 03 Oct 2023 16:10:29 GMT

If I understood your workflow correctly that you are looking at the assembly's Item BOM result, you need to change the setting "Rows that will be turned on during Assign Item" to "All"

Re: Assign/Update Items is different via API then UI

Majjek — Thu, 05 Oct 2023 12:22:19 GMT

That setting is turned on, that's why I assume it should show all rows.

And it does show all rows and assign all items when I perform the Assign/Update action on just the assembly (without selecting the child parts).

But when I select the assembly and the 3 children and then perform the Assign/Update action, it shows only 1 of the 3 rows, but creates all items.

I can confirm that this is not only the result from my own code, but also when using the Assign/Update Item button from Vault.

So they're behaving the same.

I tried looking at the BOM object of the file, but couldn't find anything strange in there.

Then I created a copy of that .iam (not the children) in Inventor and checked it in into the Vault.

When performing the same actions, it now behaves as expected, so the BOM is complete.

The only thing that's different between the BOM object of the old and new file, is that the old BOM object still refers to the first file versions (file ID) of the parts, because it was never checked in to Vault from Inventor after the initial check in.

The new .iam uses the latest file versions (which makes sense of course).

But that shouldn't be an issue in my opinion, and also, it still shows 1 item, instead of 0.