- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Thank you very much Krieg for this explanation, very clear.
Thanks also for your warning, the extraction I want to make must indeed be a reflection of the BOM as such with a production release date.
For many suppliers, translating the drawing into production numbers/material/material thickness, etc. remains a manual task.
In this way we think we can reduce the margin of error on both sides.
See screenshot as such a picture could look like, a QR code also seems useful to me.
I once programmed a QR code on documents in the past, does iLogic understand that too?
Just your comment about 'don't use the componentoccurrences collection'.
Do you mean not to use it by definition?
Or not for the purpose.
I'm using 'componentoccurrences' to recursively iterate through the assemblies and get the underlying components, isn't that a correct method?
The way I now get the total numbers, by going through the BrowserPane, I also get the numbers of the Phantoms in the main assembly, as far as I know I don't come across those in a BOM when they are Phantom.
How do you see that?