When we try to import user authorizations, the import stops when it finds a 3rd-party module that uses subclassing, forcing us to laboriously go through the import file and delete every line that mentions a 3rd-party module, then after the import, manually enter them. The more Sage depends on 3rd-parties, the more they are responsible for enabling them to work.
by: Stephen C. | over a year ago | Setup / Environment
Comments
Importing will always be subject to the nitty gritty detail. Just the way it is.
But Agree that all importing could have a 'pre-test screen that shows those lines that will fail, so removal / rectification can be done in bulk.
Feature requested Mar 2019
Sage - please put an AUTOMATIC "Date Entered" field on all posts