Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST]: Improve field import message reporting #922

Open
bellerbrock opened this issue Mar 14, 2024 · 4 comments · May be fixed by #1114
Open

[REQUEST]: Improve field import message reporting #922

bellerbrock opened this issue Mar 14, 2024 · 4 comments · May be fixed by #1114
Assignees

Comments

@bellerbrock
Copy link
Collaborator

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

@ramierop
Copy link

ramierop commented Apr 2, 2024

@bellerbrock Do you need anything from me on this?

@bellerbrock
Copy link
Collaborator Author

@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.

@ramierop
Copy link

ramierop commented Apr 2, 2024

@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.

@bellerbrock
Copy link
Collaborator Author

@bellerbrock bellerbrock linked a pull request Dec 11, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants