iAssembly - BOM export issue/error "InvalidArgument"

iAssembly - BOM export issue/error "InvalidArgument"

bogdan946KV
Contributor Contributor
841 Views
10 Replies
Message 1 of 11

iAssembly - BOM export issue/error "InvalidArgument"

bogdan946KV
Contributor
Contributor

Dear community,

 

Please help to find out where is the problem/issue.

iAssembly work perfectly fine. I can place in to other assembly, change member, see BOM. But when it comes to export BOM in to excel, I receive this message (see below). Did not do anything related to this, so it sort of strange and I do not understand where to look.

If I place iAssembly in to another assembly, and trying to export BOM from there (structure level all), it exportin without any error. But it rather a way around.

 

Any ideas? 🙂

 

image.png

 

0 Likes
842 Views
10 Replies
Replies (10)
Message 2 of 11

CGBenner
Community Manager
Community Manager

@bogdan946KV 

 

Can you share the files here?  Use Pack & Go, Zip the files, and attach to your reply.

 

Also, to clarify your workflow, are you seeing this error when you export the BOM from the iAssembly parent file, opened by itself?  Are you trying to export the BOM for all instances (the entire factory) at the same time?  Just need to know the steps you took leading to the error so we can try to reproduce it.

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M

Message 3 of 11

bogdan946KV
Contributor
Contributor

Hallo Chris,

 

Thank you for interesting in this issue.

Yes, error pop up during export of the BOM from the iAssembly parent file.

I have also try to change in BOM to export All members together, or single member - same error.

I am not able to share the file here. But I am sending link for download directly to you. 🙂 

 

Appreciate your help.

0 Likes
Message 4 of 11

CGBenner
Community Manager
Community Manager

Is the file proprietary? I saw your PM and replied before I saw your post here.  If you cannot share it because it is private, I will try to take a look myself.

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M

Message 5 of 11

bogdan946KV
Contributor
Contributor

Hallo Chris,

 

You are correct, file is proprietary, and I can not share it publicly (hope for understanding).

But if any other would like to look in to this subject, I can forward the link for download in PM.

 

Thanks.

0 Likes
Message 6 of 11

CGBenner
Community Manager
Community Manager

@bogdan946KV 

 

Using the files you sent me, I was able to reproduce the error, but once I hit Continue, I was able to export the BOM to a .xml file with no further problems.  I will send you this file in the PM, so you can examine it and see if it is what you expect.

 

@johnsonshiue does this sound like normal behavior when exporting BOM from the Factory of an iAssembly?

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M

Message 7 of 11

bogdan946KV
Contributor
Contributor

Thanks Chris for your time.

I also able to export in to xml file. But it not something I used to do. And I am not able to import xml  properly in to excel, as I do with direct export from BOM.

 

Question here not really about this particular iAssembly. I would like to understand what happened(root cause), so I know for future what actions can trig this problem/issue.

 

Thanks again and hope other experts can look in to this.

For sure should be some explanation. 🙂

 

0 Likes
Message 8 of 11

CGBenner
Community Manager
Community Manager

@bogdan946KV 

 

I am becoming more convinced that the issue is with exporting the BOM of the entire factory at the same time.  Inventor may be seeing this as Multiple BOMs, instead of one really big one.  I would love to hear from @johnsonshiue on this one.  But, my feeling right now is that exporting the BOM for only one instance of the iAssembly at a time is probably the correct workflow.

Did you find a post helpful? Then feel free to give likes to these posts!
Did your question get successfully answered? Then just click on the 'Accept solution' button.  Thanks and Enjoy!



Chris Benner

Community Manager - NAMER / D&M

Message 9 of 11

bogdan946KV
Contributor
Contributor

Maybe this is important information that I forgot to mentioned.

Previous version of this iAssembly consisted of 11 members (variants) and everything worked fine. I was able to export BOMs. Than I added another 11 members (variants) and this error appear. Can it be because of members quantity? Maybe? I can run a test and delete some of them.

0 Likes
Message 10 of 11

bogdan946KV
Contributor
Contributor

And now I can confirm that that is the issue.

If I delete one member (variant), no mater which one - this error disappear and I can export BOM normally.

 

Is it any limitation on Member quantity? Currently it is 22. If it is 21, it work fine. 🙂

0 Likes
Message 11 of 11

johnsonshiue
Community Manager
Community Manager

Hi! I believe it is a bug (or limitation due to incomplete implementation). The iAssembly BOM has a lot of room for improvement. The BOM table in the factory assembly is a bit confusing. If you want to see the member specific BOM, you may insert the member to an assembly and then look at the BOM. You will be able to use Structured -> All-Level and Part Only BOM Views.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes