You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some insights after troubleshooting a tricky import with @ramierop :
The field import silently skips rows in an import file where one of the chosen identifiers is missing, or where the cell indexes in the row are shifted due to a merged cell. And when errors are reported in a toast, they don't stay on the screen for very long and are often truncated.
A larger dialog that persists would be an improvement for reporting errors, and could include warnings with details about skipped rows.
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
@ramierop not at the moment unless you have additional suggestions or clarifications.
I need to discuss this with Trevor and figure out where it fits in our larger plans. Then at whatever point we have a pull request drafted your review would be helpful to make sure it address all the issues.
@bellerbrock I wouldn't mind if when there is an error message if we had to acknowledge that we have seen it with a close button or something of the like.
Description
Some insights after troubleshooting a tricky import with @ramierop :
The field import silently skips rows in an import file where one of the chosen identifiers is missing, or where the cell indexes in the row are shifted due to a merged cell. And when errors are reported in a toast, they don't stay on the screen for very long and are often truncated.
A larger dialog that persists would be an improvement for reporting errors, and could include warnings with details about skipped rows.
Alternatives
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: