You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ ] a bug report
- [X] a feature request
- [ ] **not** a usage question (ask them on https://stackoverflow.com/questions/tagged/phpspreadsheet or https://gitter.im/PHPOffice/PhpSpreadsheet)
What is the expected behavior?
AutoFilter structure information is now maintained in a separate /table<n>.xml file in the /tables subfolder of the zip.
What is the current behavior?
AutoFilter structure information is read from the autoFilters entry in the individual worksheet files.
With changes to the structure of Xlsx files for Office365, autoFilter structure information is moved from the worksheet file. Instead, the worksheet file contains a tableParts entry:
That's just how I felt last night while I was exploring the changes. I wonder just how much else has been "moved" as well.... I want to address this as part of the work I'm planning with pivot tables, and actually have a Table Reader that handles all Excel table types (pivot, autofilter, etc); but I'll approach it step by step, with a lot of cation, especially as I'm seeing namespace use in tableParts.
This is:
What is the expected behavior?
AutoFilter structure information is now maintained in a separate
/table<n>.xml
file in the/tables
subfolder of the zip.What is the current behavior?
AutoFilter structure information is read from the
autoFilters
entry in the individual worksheet files.With changes to the structure of Xlsx files for Office365, autoFilter structure information is moved from the worksheet file. Instead, the worksheet file contains a
tableParts
entry:This may contain multiple parts, and each entry points to an entry in the
rels
file for that worksheet. This in turn has a pointer to the actual filewhere the AutoFilter structure is stored.
The actual structural definition of the AutoFilter is otherwise identical, simply moved to a new location.
The text was updated successfully, but these errors were encountered: