[BUGFIX] Set correct export field uids #1217
Merged
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
As all filter requests are forwarded from the dispatch action to the list action, the request is evaluated as "invalid" and submitted form values are used by default. To ensure the current (new) field uids for an export are taken into account, the corresponding attribute "respectSubmittedDataValue" needs to be set.
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.
As all filter requests are forwarded from the dispatch action to the list action, the request is evaluated as "invalid" and submitted form values are used by default. To ensure the current (new) field uids for an export are taken into account, the corresponding attribute "respectSubmittedDataValue" needs to be set.
Maybe related to: #1180
Resolves: #1089