Quantcast
Channel: Open XML Format SDK forum
Viewing all articles
Browse latest Browse all 1288

HELP NEEDED! : Worksheet with multiple TableDefinitionParts causes issue due to Uri naming.

$
0
0

Creating a TableDefinitionPart with TableDefinitionPart tdp = worksheetpart.AddNewPart<TableDefinitionPart>() causes tables to be added following the naming convention (table.xml, table2.xml, ..., tablea.xml, etc.).  These Uri paths are created with hex values, though the id in the actual table xml is UInt32 (1,2,3,...,etc.).  It appears if I go over 12 tables then something with the name of the part and ids gets confused inside of Excel.  So two questions:  Is there any way possible to control the name (Uri) of the part when it is created(added).  If not, is there anyway to control how the SDK is choosing to number the tables (i.e. don't use hex).

If none of those options is viable, can anyone think of any other workaround?

Thanks in advance.


Viewing all articles
Browse latest Browse all 1288

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>