Feature: create a data quality check which check extra_data value types

[macintoshpie]

Note, this is a request for feedback/suggestion, something to discuss.

context

TODO: add more info Basically, not all extra_data in seed is stored how we'd like it to be, sometimes everything is just a string. But users can specify the data type in the column settings for the org. As seed works on a paginated inventory list, the current implementation requires that the users have "valid" data in their extra data. Also, this would be useful to users as they are importing their data

task

• create data quality checks which will check the extra data values and determine if they are "castable" into the specified column type. E.g. if column foo is specified as a float, and one of the properties has the value 'hello', this would fail the data quality check and get flagged. If one of the properties had the value '5' then it'd pass (the string 5 can be cast to a float). Or if it's null that might be ok to let it pass too??
• make this a default DQ check for all orgs

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[RDmitchell]

see also #3749 -- users need to set the data type of extra data fields, and right now they have to do it after import, which users don't know they need to do.

They should be able / required (?) to set the data type in the mapping step in data import.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.