Long object API names cause Excel corruption

[cdevelin]

Hi,

Particularly when trying to generate a dictionary from Managed Package objects, which have the package prefix, some objects with very long names cause a corruption because their API name is too long for the legal tab character length in Excel.

When this happens, you get a corruption message from Excel trying to open the file, and the tabs with extra long names have completely lost their identifier of which object they belong to, and the failed tabs are now called 'Recovered_Sheet1', 'Recovered_Sheet2' etc, with no identifer anywhere of what they actually were, since the object name is not actually in the tab's row data itself.

If I can suggest the following useability enhancements to make the Excel generated much easier to use:

1. Include the object's API name and 'friendly' Label name in the header rows of each tab (Rather than the uninformative 'SALESFORCE' at the top of each tab)
2. Create an 'Index' tab as the very first sheet, which has the 'friendly' Label name and API name and a hyperlink to that particular sheet as an index table.
3. Include a link at the top of each tab to take you back to the Index tab i.e. each tab would have a cell with =HYPERLINK("#Index!A1","Index") to take you back to the Index tab.

I did a data dictionary for an org with 1300 objects and finding and navigating the tabs was very difficult.