Technical documents for protocols, computer languages, standards support, and data portability. The goal with Open Specifications is to help developers open new opportunities to interoperate with Windows, SQL, Office, and SharePoint.
Hi Jan Havlicek,
I have to take back some of my previous comment. I discussed this with our Excel team and while the full story is going to be way more complex than we need to go into here, I can give you a more general rule of thumb. I have a little more testing to verify all the dxf related attributes for Table (from 18.5.1.2) but I wanted to get this to you now to clear up some confusion.
Tables deal with dxf's a little differently than other components and elements. The main thing is that when you specify those dxf related attributes, they do actually get processed by Excel but will only (in general) show up as different formatting (if there is a difference from the style or direct formatting of the table definition) when you grow the table, for example when you add a new column or row. They do not affect existing cells in the table.
I have a simple example using headerRowDxfId. I've attached the style and table parts to demonstrate. If you use these in your test workbook and add a column, you'll see that the new column header does respect the desired differential formatting index referenced by headerRowDxfId.
Note: if you insert a new column or row, table style or direct formatting of existing cells is respected but not dxf formatting.
Once I have tested with all of the dxf related attributes to make sure they follow this, I will file a bug to get some general explanation added to MS-OI29500 saying that basically Table dxf processing only affects new cells added to a table but not existing cells.
Let me know if you have more questions about this or if it's not clear.
Best regards,
Tom Jebo
Microsoft Open Specifications Support