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

Long-term-stable ass'y w/ skeleton part producing "unexported in the source" msg

AlexFielder
Advisor

Long-term-stable ass'y w/ skeleton part producing "unexported in the source" msg

AlexFielder
Advisor
Advisor

Hi all,

 

This is an odd one; for a customer we have been maintaining (but not adding to) a "configurator" that when I first looked had over 5,000 lines of iLogic code within it.

 

I refactored it down to around 1800 lines of iLogic and all has been mostly okay in the 18 month period since that last massive change.

 

The customer is upgrading to 2019 and of course wanted to continue using the configurator we had built for them.

 

I have migrated all the necessary files and during testing the following error appears on multiple occasions:

 

 

0000013469-Configuration Top Level Assembly-1-V4.iam: Errors occurred during update
     0000013469-LHC Door Assy-1-V4.iam: Errors occurred during update
       0000013469-LHC Door Intumescent-1-V4.ipt: Errors occurred during update
         One or more derived objects have had their Export status turned off in the source. Use the Design Doctor for treatment options.
           Type 6 Seal:2 : has been unexported in the source.
           Seal:2 : has been unexported in the source.
           VP Bead 1:4 : has been unexported in the source.
           VP Bead 7:4 : has been unexported in the source.
           VP Bead 4:4 : has been unexported in the source.
           VP Bead 236:4 : has been unexported in the source.
           VP Bead 7:3 : has been unexported in the source.
           VP Bead 5:2 : has been unexported in the source.
           VP Bead 4:3 : has been unexported in the source.
           VP Bead 236:3 : has been unexported in the source.
           VP Bead 1:3 : has been unexported in the source.
           Type 6 Seal:1 : has been unexported in the source.
           Seal:1 : has been unexported in the source.
           VP Bead 8:2 : has been unexported in the source.
           VP Bead 8:1 : has been unexported in the source.
           VP Bead 7:2 : has been unexported in the source.
           VP Bead 4:2 : has been unexported in the source.
           VP Bead 1:2 : has been unexported in the source.
           VP Bead 236:2 : has been unexported in the source.
           VP Bead 7:1 : has been unexported in the source.
           VP Bead 5:1 : has been unexported in the source.
           VP Bead 1:1 : has been unexported in the source.
           VP Bead 236:1 : has been unexported in the source.
           SP Bead 7:32 : has been unexported in the source.
           SP Bead 1:32 : has been unexported in the source.
           SP Bead 236:32 : has been unexported in the source.
           SP Bead 7:31 : has been unexported in the source.
           SP Bead 1:31 : has been unexported in the source.
           SP Bead 236:31 : has been unexported in the source.
           SP Bead 7:30 : has been unexported in the source.
           SP Bead 7:29 : has been unexported in the source.
           SP Bead 1:30 : has been unexported in the source.
           SP Bead 1:29 : has been unexported in the source.
           SP Bead 236:30 : has been unexported in the source.
           SP Bead 236:29 : has been unexported in the source.
           SP Seal:16 : has been unexported in the source.
           SP Seal:15 : has been unexported in the source.
           SP Bead 7:28 : has been unexported in the source.
           SP Bead 1:28 : has been unexported in the source.
           SP Bead 236:28 : has been unexported in the source.
           SP Bead 7:27 : has been unexported in the source.
           SP Bead 1:27 : has been unexported in the source.
           SP Bead 236:27 : has been unexported in the source.
           SP Bead 7:26 : has been unexported in the source.
           SP Bead 7:25 : has been unexported in the source.
           SP Bead 1:26 : has been unexported in the source.
           SP Bead 1:25 : has been unexported in the source.
           SP Bead 236:26 : has been unexported in the source.
           SP Bead 236:25 : has been unexported in the source.
           SP Seal:14 : has been unexported in the source.
           SP Seal:13 : has been unexported in the source.
           SP Bead 7:24 : has been unexported in the source.
           SP Bead 1:24 : has been unexported in the source.
           SP Bead 236:24 : has been unexported in the source.
           SP Bead 7:23 : has been unexported in the source.
           SP Bead 1:23 : has been unexported in the source.
           SP Bead 236:23 : has been unexported in the source.
           SP Bead 7:22 : has been unexported in the source.
           SP Bead 7:21 : has been unexported in the source.
           SP Bead 1:22 : has been unexported in the source.
           SP Bead 1:21 : has been unexported in the source.
           SP Bead 236:22 : has been unexported in the source.
           SP Bead 236:21 : has been unexported in the source.
           SP Seal:12 : has been unexported in the source.
           SP Seal:11 : has been unexported in the source.
           SP Bead 7:20 : has been unexported in the source.
           SP Bead 1:20 : has been unexported in the source.
           SP Bead 236:20 : has been unexported in the source.
           SP Bead 7:19 : has been unexported in the source.
           SP Bead 1:19 : has been unexported in the source.
           SP Bead 236:19 : has been unexported in the source.
           SP Bead 7:18 : has been unexported in the source.
           SP Bead 1:18 : has been unexported in the source.
           SP Bead 236:18 : has been unexported in the source.
           SP Bead 7:17 : has been unexported in the source.
           SP Bead 1:17 : has been unexported in the source.
           SP Bead 236:17 : has been unexported in the source.
           SP Bead 7:16 : has been unexported in the source.
           SP Bead 7:15 : has been unexported in the source.
           SP Bead 7:14 : has been unexported in the source.
           SP Bead 7:13 : has been unexported in the source.
           SP Bead 1:16 : has been unexported in the source.
           SP Bead 1:15 : has been unexported in the source.
           SP Bead 1:14 : has been unexported in the source.
           SP Bead 1:13 : has been unexported in the source.
           SP Bead 236:16 : has been unexported in the source.
           SP Bead 236:15 : has been unexported in the source.
           SP Bead 236:14 : has been unexported in the source.
           SP Bead 236:13 : has been unexported in the source.
           SP Seal:10 : has been unexported in the source.
           SP Seal:9 : has been unexported in the source.
           SP Seal:8 : has been unexported in the source.
           SP Seal:7 : has been unexported in the source.
           SP Bead 7:12 : has been unexported in the source.
           SP Bead 1:12 : has been unexported in the source.
           SP Bead 236:12 : has been unexported in the source.
           SP Bead 7:11 : has been unexported in the source.
           SP Bead 1:11 : has been unexported in the source.
           SP Bead 236:11 : has been unexported in the source.
           SP Bead 7:10 : has been unexported in the source.
           SP Bead 1:10 : has been unexported in the source.
           SP Bead 236:10 : has been unexported in the source.
           SP Bead 7:9 : has been unexported in the source.
           SP Bead 1:9 : has been unexported in the source.
           SP Bead 236:9 : has been unexported in the source.
           SP Seal:6 : has been unexported in the source.
           SP Seal:5 : has been unexported in the source.
           SP Bead 7:8 : has been unexported in the source.
           SP Bead 1:8 : has been unexported in the source.
           SP Bead 236:8 : has been unexported in the source.
           SP Bead 7:7 : has been unexported in the source.
           SP Bead 1:7 : has been unexported in the source.
           SP Bead 236:7 : has been unexported in the source.
           SP Bead 7:6 : has been unexported in the source.
           SP Bead 1:6 : has been unexported in the source.
           SP Bead 236:6 : has been unexported in the source.
           SP Bead 7:5 : has been unexported in the source.
           SP Bead 1:5 : has been unexported in the source.
           SP Bead 236:5 : has been unexported in the source.
           SP Seal:4 : has been unexported in the source.
           SP Seal:3 : has been unexported in the source.
           SP Bead 7:4 : has been unexported in the source.
           SP Bead 236:4 : has been unexported in the source.
           SP Bead 1:4 : has been unexported in the source.
           SP Bead 7:3 : has been unexported in the source.
           SP Bead 236:3 : has been unexported in the source.
           SP Bead 1:3 : has been unexported in the source.
           SP Seal:2 : has been unexported in the source.
           SP Seal:1 : has been unexported in the source.
           SP Bead 7:2 : has been unexported in the source.
           SP Bead 236:2 : has been unexported in the source.
           SP Bead 1:2 : has been unexported in the source.
           SP Bead 7:1 : has been unexported in the source.
           SP Bead 236:1 : has been unexported in the source.
           SP Bead 1:1 : has been unexported in the source.

Which of course is less than ideal. The one and only result on Google basically says: "open each Derived Component Object in the erroring part and DO NOTHING, then click okay" that I simply have no idea how to circumvent using the API.

 

 

These part files have not been modified in any way during the migration process (aside from the obvious save), so what on earth is going on and how do I fix it?

 

Thanks,

 

Alex.

0 Likes
Reply
1,137 Views
27 Replies
Replies (27)

JamieVJohnson2
Collaborator
Collaborator

So what is inventor doing to your documents; and what is it doing during the opening of components.

First the migration may have had issues resolving the database changes properly, like not chasing all the reference files, leaving links out of whack.  So the given solution would be to let Inventor's engine auto fix it when the file is opened. 

 

Next after the component part is opened what is Inventor doing?  Likely just autorunning the .Update or .Update2 commands as it does on all files where we don't set 'defer updates' every time it opens something.  So to force this via API, get the derived part's definition, go through to its components, get the individual file names, run an open (hidden), update, save, close.  Dissecting derived parts is not something I've done personally, because I haven't dealt much with derived parts in the api (more than creating one).

 

Another thought (because your project is revamping an older one), you may already know well, the iLogic compiler now supports VB.Net code.  You could write in Visual Studio using pure VB.Net, where it is easier to write and test thoroughly, then copy back into iLogic as is.

 

jvj
0 Likes

AlexFielder
Advisor
Advisor

Hi @JamieVJohnson2,

Thanks for replying. I had thought of using the API to process each file in the working folder that contains a derived component, and in theory the code to do so is quite simple:

'Pseudo-code follows:

For Each File as Document in WorkingFolder
    If TypeOf(File) is PartDocument then
        Dim partDoc as PartDocument = File
        If partDoc.Contains(DerivedComponent) then
            Open PartDoc
            Navigate Part Browser to DerivedComponentFeature
            Run Edit Derived Component Command and wait for the user (me) to click okay
        End if
    End if
Next

This of course relies upon me finding the correct command using the Event Viewer.

And being able to navigate to the correct part feature in the browser before activating it.

 

One could argue that doing all this is likely to take longer than manually clicking through the 200 or so parts that I know for definite contain derived components, but I think it's probably worth it in the long-run as it'll mean that whoever picks up this project if I were to move on, (or if I have to migrate it again in future) the manual work is eliminated.

 

My OP was a "WTF Autodesk, should this happen?" observation as well as a cry for assistance that hopefully help myself/others in future. (By way of a patch being produced or a comprehensive workaround that doesn't involve countless hours of "Open offending part, edit derived-component, click okay")

 

Thanks,

 

Alex.

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

 

To enable surfacebody of derived component as "Export Object", try SurfaceBody.Exported Inventor API. For more details, refer below API help documentation link.

 

http://help.autodesk.com/view/INVNTOR/2019/ENU/?guid=GUID-2D66B9DC-CBF3-4E83-8E33-AEB7AD6DFCD8

 

After marking SurfaceBody as "Export Object", try Document.Update API to update. Hoping that this will help

 

Thanks and regards,

 


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

AlexFielder
Advisor
Advisor

Hi @chandra.shekar.g,

 

The problem isn't that we need to export the objects, it's that they already are exported and during migration(!?) it seems these same parts are randomly having the "export object" setting turned off.

 

Ideas?

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

"open each Derived Component Object in the erroring part and DO NOTHING, then click okay" that I simply have no idea how to circumvent using the API.

 

To achieve above task, Inventor API(SurfaceBody.Exported) suggestion is recommended. It is also mentioned that only some parts having "Export Object" setting turned off. For these parts, need to turn on the settings for "Export Object" by opening through Inventor API.

 

Thanks and regards,


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

AlexFielder
Advisor
Advisor

Okay, so you answered my question as to how to circumvent the error using the API.

 

It doesn't however address the underlying problem which is a seemingly random situation of previously exported objects becoming unexported for no good reason other than because they do.

 

Am I the only person experiencing these kinds of issues?

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

To investigate the issue, can you please provide reproducible data set and workflow? Please make sure that files are non confidential.

 

Thanks and regards,


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

AlexFielder
Advisor
Advisor

I can provide files certainly, can you escalate this to an internal case please so I can add the files to your system?

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

I checked with engineering team about this issue. Team is expecting reproducible data set and workflow to reproduce the behavior. So, can you please provide data set and workflow to reproduce? please make sure that files are non confidential.

 

Thanks and regards,


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

AlexFielder
Advisor
Advisor

I have had some issues accessing the partner centre system. My colleagues are looking into it as we speak. 

0 Likes

AlexFielder
Advisor
Advisor

Just adding some files to case number 14913088 as we speak.

 

 

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

 

Please provide link to download the files.

 

Thanks and regards,


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

AlexFielder
Advisor
Advisor

the file links are contained within the Partner Centre case file.

0 Likes

chandra.shekar.g
Autodesk Support
Autodesk Support

@AlexFielder,

 

Files are attached with case number 14913088. Able to download the same.

 

Is there any specific workflow to reproduce the behavior?

 

Thanks and regards,


CHANDRA SHEKAR G
Developer Advocate
Autodesk Developer Network



0 Likes

Jon.Dean
Alumni
Alumni

Hi @AlexFielder,

I can see the files in the case mentioned, I can pass them onto @chandra.shekar.g, so he can investigate, I will also do the same.

Cheers

Jon



Jon Dean

0 Likes

YuhanZhang
Autodesk
Autodesk

Hi @AlexFielder, can you tell your workflow to reproduce the problem? Do we need to run any iLogic rule to see the problem? And I see your data were migrated using Inventor 2019_136 build, so can you send us some part files without migration so we can reproduce the problem of flipping the Export Object flag? Otherwise it would be difficult to know whether it is Inventor issue or iLogic issue.



If this solves the problem please click ACCEPT SOLUTION so other people can find it easily.



Rocky Zhang
Inventor API PD
Manufacturing Solutions
Autodesk, Inc.

0 Likes

AlexFielder
Advisor
Advisor

Hi @YuhanZhang,

 

Please have a read of the case in your system, the steps to reproduce the error are there. I have also today added a 2015 format dataset which includes the exact same files pre-migration for you to test.

 

Regards and Thanks,

 

Alex.

0 Likes

YuhanZhang
Autodesk
Autodesk

Hi Alex,

 

I migrated your data to inventor 2019, and can't see any problem here, can you help to explicitly tell which part file has the Export Object flipped(surface body/work feature/sketch etc..) if you already see one?



If this solves the problem please click ACCEPT SOLUTION so other people can find it easily.



Rocky Zhang
Inventor API PD
Manufacturing Solutions
Autodesk, Inc.

0 Likes

AlexFielder
Advisor
Advisor

Hi @YuhanZhang,

 

I sent a detailed reply to @Jon.Dean last week explaining the full workflow and how these files are affected by the tool we created for our customer.

 

I've yet to receive any word back as to what the next steps are.

 

Thanks,


Alex.

0 Likes