Improve import result message interface
See original GitHub issueFeature requests on the forum
Is your feature request related to a problem? Please describe.
Upon successful import, a null message is displayed, which is very difficult to associate with a successful import. And if import fails, the message {"message": "Internal Server Error"} is displayed all the time, which also does not say what the problem is.
Describe the solution you’d like
If import is successful, the message Import completed successfully! is displayed. And if import fails, a message is displayed that the import could not be completed, and the specific reason why (and also its solution is possible).
Describe alternatives you’ve considered
Additional context The server should give the correct error messages, which can be displayed in the web interface to the user.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
69. How to enhance the response of the inbound synchronous ...
Learning Objectives:- This unit describes:- The response of the inbound synchronous interface to have a custom-defined message type.
Read more >Import and Export Messages in LYNX
Import Extract Set Status Messages ; Duplicate Organization. Organizations of duplicate identifiers are excluded. Organization Import.
Read more >Interfaces for Importing Data - MicroStrategy
You can import data from many different data sources, such as an Excel file or a database, or by using the results of...
Read more >Data import problems - IBM
Data import problems are related to situations in which the data import fails or the data that is displayed in reports is inconsistent...
Read more >Developing Message Interfaces - SAP Help Portal
Before you can develop message interfaces in the Integration Builder, you must import a software component version and create one or more Repository ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This would be slightly more complex (for a minor issue), but it would be great to stay on the same page, and instead just get the HTTP response in a box/alert that you can then close
@ErikBjare The datastore actually already returns the exact error in aw-server-rust, it’s just a matter of sending it in the HTTP body response.