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

Problem with derived assembly

jan.pomplun
Contributor

Problem with derived assembly

jan.pomplun
Contributor
Contributor

Hi,

 

I have a problem with creating a derived part of an assembly. The assembly looks like the following:

assembly.PNG

When I derive it into a part via the GUI ("Ableiten" means derived part in english)

button.PNG

The derived part looks similar. When I do it via the API:

var partDoc = (Inventor.PartDocument)InventorUtil.InventorApplication.Documents.Add(Inventor.DocumentTypeEnum.kPartDocumentObject, "", false);

DerivedAssemblyDefinition defAss = partDoc.ComponentDefinition.ReferenceComponents.DerivedAssemblyComponents.CreateDefinition(invDelegate.Document.FullDocumentName);
defAss.InclusionOption = DerivedComponentOptionEnum.kDerivedIncludeAll;
defAss.DeriveStyle = DerivedComponentStyleEnum.kDeriveAsSingleBodyNoSeams;    
partDoc.ComponentDefinition.ReferenceComponents.DerivedAssemblyComponents.Add(defAss);

The derived part however looks like:

part.PNG

I do not understand why the marked feature is shown in the part - marked with the red circle.

I can only reproduce it in the GUI when I change the following to include the bounding box:

GUI.png

notice the green rectangle (should be bounding box instead of the plus).

 

I do not understand why this would be the default behaviour via the API - while it is not via the GUI.

Further (and more important) I do not know how to deactivate it. I tried around with following ptions which did not help

            defAss.InclusionOption = DerivedComponentOptionEnum.kDerivedIncludeAll;

            defAss.DeriveStyle = DerivedComponentStyleEnum.kDeriveAsSingleBodyNoSeams;
            defAss.DeriveStyle = DerivedComponentStyleEnum.kDeriveAsMultipleBodies;

            defAss.IncludeAllTopLevelWorkFeatures =DerivedComponentOptionEnum.kDerivedExcludeAll;
            defAss.IncludeAllTopLevelSketches = DerivedComponentOptionEnum.kDerivedExcludeAll;
            defAss.IncludeAllTopLeveliMateDefinitions = DerivedComponentOptionEnum.kDerivedExcludeAll;
            defAss.IncludeAllTopLevelParameters = DerivedComponentOptionEnum.kDerivedExcludeAll;

Does anyone know how to export the assembly without the "bounding box" features?

 

Thanks,

 

Jan

0 Likes
Reply
369 Views
2 Replies
Replies (2)

bradeneuropeArthur
Mentor
Mentor

Hi,

 

For this you should (could) use a View representation in the inventor assembly with that specific part suppressed.

Than use this View representation in your derived definition too...

 

Regards,

Autodesk Software: Inventor Professional 2018 | Vault Professional 2018 | Autocad Mechanical 2018
Programming Skills: Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Dimension Component! | Partlist Export! | Derive I-properties! | Vault Prompts Via API! | Vault Handbook/Manual!
Drawing Toggle Sheets! | Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !

Regards,

Arthur Knoors

Autodesk Affiliations:

Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:Drawing List!|Toggle Drawing Sheet!|Workplane Resize!|Drawing View Locker!|Multi Sheet to Mono Sheet!|Drawing Weld Symbols!|Drawing View Label Align!|Open From Balloon!|Model State Lock!
Posts and Ideas:Dimension Component!|Partlist Export!|Derive I-properties!|Vault Prompts Via API!|Vault Handbook/Manual!|Drawing Toggle Sheets!|Vault Defer Update!


! For administrative reasons, please mark a "Solution as solved" when the issue is solved !

0 Likes

jan.pomplun
Contributor
Contributor

So is it correct that the API automatically includes the bounding box opposed to the GUI behaviour?

For this functionality the API can not reproduce all commands that would be done via GUI?

 

Thanks for the workaround, I will try.

0 Likes