- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
This sounds like it could potentially be a somewhat large project. First of all, I would have to say that if you can do it manually, then there's hope that it can be done by iLogic. Have you tried to do any of this manually yet? In an assembly's BOM, you can manually add columns for standard & custom iProperties. If those iProperties were reflections of parameters, that were being kept accurate, then you may have all the data you need in one place, as you are wanting. Of course, since this is the BOM we're talking about, any columns you add to it for custom iProperties will effect/encompass all components listed in the BOM, so if that custom iProperty doesn't exist yet, it will create that custom iProperty within the document of every component listed. It can be quicker/easier to mass create custom iProperties this way when needed. The manual alternative would be to first open every component, and add the custom iProperty manually, then save them. But it sounds like some of the information you are wanting shown within the BOM may need to be retrieved into these properties by iLogic rules which inspect those components and ensure the values of those properties are accurate. Do you already have the rules needed to collect all the needed data from your model files into the parameters & properties?
Wesley Crihfield
(Not an Autodesk Employee)