It would be great that error messages when importing masters or transactions that the error messages are more specific and accurate. For instance, importing of BOM, if the record exists, please state so rather than just displaying no details inserted.
by: Caroline N. | over a year ago | General Enhancements
Comments
Or if the import falls over, report which record caused the error and why rather than just counting how many succeeded and bailing out.
The whole import process needs re-designing to be less prone to error and more useful to non-IT users.
Agreed, vague "no value" comments most unhelpful...
This idea is 3 years old, with a lot of votes. Sage, can we have some feedback on this one?
And a feedback process on the ideas website, rather than an idea hanging in limbo for many years? The 'planned' flag is good, but nowhere near enough. What about an actual Sage persons _comment_ on all ideas with a lot of votes? Please?
Import all the records which comply and report the ones that don't, just like creating an error batch in AR and AP posting. The current system is as bad as Microsoft file copy which dies on the first error.
Sage banner "We are listening" should be changed to "We are listening when we feel like it. About every 3 years or so". See the long dispute with Mike Ritchie. Search for Saggy.