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

I think the nuance that I was missing is the difference between the "Definition" and the "definitionDocumentType". Welds are not their own Document, but they are their own Object.

 

So oOcc.Definition.Type is kWeldsComponentDefinitionObject

 

but the DOCUMENT for the Welds Object is whatever assembly they reside in...

image.png

 

For example, in the above Screenshot, the "Welds" is it's own object and is of the type kWeldsComponentDefinitionObject. The DOCUMENT that the Welds object exists in is the assembly doc ETM-TEST4.iam, so the oOcc.DefinitionDocumentType is kAssemblyDocumentObject.

 

I would imagine that there may exist some sort of feature which is an object that you would add to a part file that is derived from a  PartFeatureObject. In that case:

  • oOcc.definition.Type = kSomeSortOfFeatureComponentDefinitionObject because that's the Type of the actual object
  • oOcc.DefinitionDocumentType = kPartDocumentObject because that's the Document that oOcc resides in is a part