Check mapped data for blanks #5127
Open
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.
Any background context you want to provide?
If a user imports data that does not match the expected data type, SEED will attempt to parse it, and if it fails it will default to
None(or blank).This isn't an issue for Text or extra data fields. Extra data is saved in the db as a string, and anything can be converted to a string.
This behavior isn't obvious to the user during the "Save Mapping" step.
What's this PR do?
How should this be manually tested?
Import a file that has data type mismatches for numeric canonical columns (ex: Gross Floor Area = 'abc'). Ensure a warning appears during mapping. Clicking "Back to Mapping" will not clear the error, but clicking "Map your Data" will.
What are the relevant tickets?
#5080
Screenshots (if appropriate)