dev/mailing#56 dev/mailing#57 Ensure that we don't pass in any namesp… #15779
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.
…aced fields when building the row array for mailing reports
Overview
Following the datepicker conversion for some mailing smart groups, some mailing job fields started to be name spaced which then lead to e-notices of undefined property as per dev/mailing#57 and mailing reports showing incorrect information dev/mailing#56
This resolves it by using the name key for the fields as that will be the non unique / non name spaced version
Before
unique field name used causing e-notices
After
non unique field name used
ping @eileenmcnaughton @totten @demeritcowboy