-
Notifications
You must be signed in to change notification settings - Fork 821
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FIX: Modifications to GridFieldExportButton to allow ArrayList use in…
… SS_Report
- Loading branch information
Showing
1 changed file
with
9 additions
and
2 deletions.
There are no files selected for viewing
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
Having updated to 3.1.13, I noticed that this change has resulted in an export to CSV bug when using custom export fields. Basically, if
$value
ends up being null, it will attempt to use the column heading that you've defined. If your column heading happens to contain the dot notation (for relationships), it will fail to resolve and throw an error. An example of this would be the following, where the dot notation has been used to clarify where the field is coming from..If
Field
ends up being null (which is completely valid), it will try to resolveClass.Field
incorrectly. This results in..[User Error] Class is not a relation/field on Class