Inventor 2019 iProperties export to excel or CSV file

[philqpr]

Hello,

I am looking into the export of a number of Inventor iProperties (standard and custom) from assemblies and parts within a project into excel or CSV file. The goal would be to make this an automated process as the design stage moves through various stages. We are looking to use ilogic to aid in the input of standard and custom iProperties.

The end goal is to import the data into a Third Party Data Management software program.

Is iLogic or Vault the best tool to export en masse the required iProperties, from a set up point of view are there Pros & Cons to each option and is one more labour intensive than the other with regards to set up & use? 

Appreciate any assistance.

Inventor Professional 2019

Vault Professional 2019

Thanks in advance

[A.Acheson]

I do not use vault so I cannot speak to how that would function when exporting iproperty data. You say your using a third party mangement software, I assume this is an inventory mangement software creating items/partnumbers, assembly orders and tracking stock correct? 

I have used our  inventory mangement software to export partnumbers, descriptions, categories etc to excel. Then used ilogic to import the data and populate parts and assemblies. Then when ready export the BOM to excel and  then into the inventory mangement software. 

Is this what you are intending to setup? 

Are you using content center to store inventory iproperties also? 

[ChristianAndersenIsmyname]

I have some experience with writing to Excel, and I would strongly recommend using Database or textfile (.csv) instead.

Excel is super slow compared to these. Database is powerful if theres several people who are supposed to use this at the same time, but if its only you, then I guess textfiles are just as good, and easier to code.

I don't have any code for iLogic on hand, but I'm using VB.net (custom made add-in I've created) to write iProperties to database.

If you're interested, I can find some snippets of my code, and you can potentially use some of it in iLogic.

[WCrihfield]

Just pointing out two of the built-in tools for working with iProperties.  There are two methods defined within the PropertySets object (PropertySets.FlushToFile  & PropertySets.RefreshFromFile ).    They both say that they require working with Apprentice, but that's not usually a problem.  The only related sample code for using the FlushToFile method is in VB.NET, but since iLogic also uses VB.NET, you could probably adapt it for use in an iLogic rule, with minimal tweaks.

If this solved your problem, or answered your question, please click ACCEPT SOLUTION.
Or, if this helped you, please click (LIKE or KUDOS) 👍.

If you want and have time, I would appreciate your Vote(s) for My IDEAS 💡or you can Explore My CONTRIBUTIONS

[philqpr]

Thank you for the reply. This is a good solution to consider. Is the iLogic code used to import the data from the inventory management system complex?

And yes we would also be looking to use content centre iproperties.

Thanks

[philqpr]

Thank you for thr reply and appreciate the comments, will bear this inmind when we look to progress the task.

[philqpr]

Thank you for the reply, appreciate you pointing out two of the iproperties built-in-tools.

[ChristianAndersenIsmyname]

If the end goal is to write these properties into a third party, I would first look up if that third party has accessible API.

If it has, you could potentially write directly to that program, and skip the excel/csv step completely.

Is it only iProperties of documents that should be written? If so, it shouldn’t be too complexed, but if you don’t have any experience with coding it might take a while.

If you spend some time looking it codes, you might understand some of the logic, and be able to rewrite already written codes.

If not, I can gladly help you, but then I need a lot more information.

[philqpr]

Thanks for the reply, I will try and find out if the third party software has accessible API and yes it should only be iProperties that are required to be exported. Thank you for the assistance, I will bear this in mind.