Item master child creation issue

[chendersonCRKPU]

I‘m having trouble with item creation and item BOMs in Vault.

I’m using a custom Level of Detail on some iLogic assemblies, and for these assemblies only, no items are being created for their child files when I 'Assign/Update Item...' 

It shouldn't make a difference to the issue I'm having, but for extra info, the configure Assign Item settings in Vault are set to 'All ' under the sub-heading 'Rows that will be turned ON during Assign Item'

Their is a mixture of parts/assemblies within these iLogic assemblies with Normal/Purchased BOM structure. Some already have pre-exisiting items and some require new items to be created. But after assign the assembly to an item, no child items are showing under the Item master BOM, its not even picking up the pre-existing items. I've double checked the Inventor BOM and that's looks normal.

Strangely enough, I found that changing the Structured BOM properties to ‘All Levels’  on all the affected assemblies solved the problem. However, I’ve not had this issue with other assemblies that use an custom LOD, whose Structured BOM properties were set to ‘First Level’ 

Any thoughts on what could be the cause?

[cbenner]

@chendersonCRKPU 

I'm not an ilogic guy, but that term in your post seems to be the one that raised my eyebrow more than any other.  Can you share what the code is used for in these assemblies?  Or, can you share the code itself?  Maybe someone in here could find a clue in the code that explains this?

[chendersonCRKPU]

@cbenner 

The code is mostly suppressing/un-suppressing components based on conditional statements using these snippets:

Component.IsActive("ComponentName") = True

Component.IsActive("ComponentName") = False

I use a bit of code at the start of the rule to ensure the assembly is in the correct LOD before suppressing anything:

Dim oDoc As AssemblyDocument = ThisDoc.Document
Dim oLOD As LevelOfDetailRepresentation
Dim oAsmCompDef As ComponentDefinition = oDoc.ComponentDefinition
Dim LODname As String = "iLogic"

Try
'Try to set our assemblies active LOD to the above specified.
oLOD = oAsmCompDef.RepresentationsManager.LevelOfDetailRepresentations.Item(LODname)
oLOD.Activate(True)
Catch
'It didn't work so we need to create a new one and then set it.
oAsmCompDef.RepresentationsManager.LevelOfDetailRepresentations.Add(LODname)
oLOD = oAsmCompDef.RepresentationsManager.LevelOfDetailRepresentations.Item(LODname)
oLOD.Activate(True)
End Try

[cbenner]

@JamesMcMullen 

Does this ring any bells with you, ilogic interfering with Item BOM creation?  Do you know an ilogic gurus in the Inventor team that might have some insight?

[JamesMcMullen]

I reached out to our main iLogic developer.  I am hoping to get a data set from him and attempt to reproduce the problem.  I would like to narrow down whether this is an iLogic problem or Vault problem.  

[pcrawley]

If it helps your research, this looks like it may be a 2018 issue.  I worked through an example with @chendersonCRKPU using Inventor 2019 and Vault Professional 2019 without issue.

[Madhan_T]

Hi, @chendersonCRKPU ,

Assign Item relies on the information from BOM at the time of check-in. If the Assign item is NOT picking the existing children, it is possible that the BOM data is incomplete during check-in. In Inventor, when the structure is changed to All Level, BOM is recomputed and sent to Vault. This may answer why it is working. The key is whenever the assembly BOM structure is changed or if the BOM is refreshed by "Rebuild All" command, Vault will be able to process the Item information accurately.

Regards,

Madhan

[JamesMcMullen]

Thanks for the information about it being 2018.  I will look into that more.  I was indeed unsuccessful at reproducing on a more recent build but that could be because of my data set.