Direct file read of iProperties

[jjstr8]

I'm working on C# code in an add-in to read iProperties directly, rather than opening the file in Inventor.  Everything seems to be working well at this point.  The only thing I'm curious about is the FMTIds for the property sets.  For a given file, they show up as follows:

Inventor Document Summary Information {8CF58000-DA66-4AE6-8FF0-7B58406FB049}

Inventor User Defined Properties {9929ADB8-6407-413E-B3DC-CB9AD2F564B7}

Inventor Summary Information {3D38DE39-0588-4C14-BB37-18F4D5DD31C7}

Design Tracking Properties {32853F0F-3444-11D1-9E93-0060B03C1CA6}

The only one that matches the API documentation is Design Tracking Properties.  Any ideas why the other three don't match?  I can't imagine that the FMTId or property set name would change any time soon, but I'd like to future-proof it as much as possible.

Thanks,

Jeremy

Inventor 2019 

@adam.nagy 

@YuhanZhang 

[A.Acheson]

Here is a VBA rule to extract the internal names. Hopefully it might help. How did you come about those internal names you have mentioned?

[bradeneuropeArthur]

Can you upload the code, so that we can investigate what is wrong?

[jjstr8]

That code involves opening the file in Inventor. It ends up being fairly slow when reading a couple of thousand files. Autodesk is following Microsoft's standard for compound files and property set storage, so the FMTIds (Inventor's internal name) are what's actually in the file.

[jjstr8 · Accepted solution]

I hadn't seen this post until now, but it appears to explain the difference.  Autodesk originally used the Microsoft standard FMTIds for Summary Information, Document Summary Information, and User-Defined Properties.  With version 6 or 7 they created their own versions.  They kept original Internal Names for compatibility's sake. 

https://forums.autodesk.com/t5/inventor-forum/iproperties-in-windows-explorer/td-p/3432431