Issue 2216 resolve office365 auto filter structure move #2218
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 9 commits
July 9, 2021 13:06
…oFiter information, either on the sheet itself for older files, or in the tables/tableX file for more recent files
…ork toward the eventual goal of moving it into its own dedicated AutoFilterTables class
…er and Office365 variants of the files used to store AutoFilter structure
PowerKiKi
deleted the
Issue-2216-Resolve-Office365-AutoFilter-Structure-Move
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is:
Checklist:
Why this change is needed?
With Office365, MS have changed the way that autofilter structures are defined in the Xml, moving information from the worksheet file to a separate tables file, as described in Issue #2216