Continued Import Improvementshttps://www.nextpoint.com/wp-content/themes/fildisi/images/empty/thumbnail.jpg150150Michael BeumerMichael Beumerhttps://secure.gravatar.com/avatar/6bc8c45dd498b5a340bedd2570a6fa99?s=96&d=mm&r=g
This week, we released our fourth and final installment of the improved import experience in Nextpoint. Over the past several months, we have taken time to listen to our users’ experiences and feedback as they put the load file mapper and overlay functionality to work. From that feedback, we further refined the user experience to make importing client data and produced data simpler and faster than ever before.
Outlined below are the updates incorporated in this final installment.
More flexible load file location when importing produced data
Returned the ability to dedupe by “Content Hash Only” for those times when you need to be extremely conservative with deduplication
Enabled proper handling of imports with apostrophes in the File Room path
Load File Mapper Enhancements
Smarter load file mapping with auto-mapping for closely matched fields in mapper and improved image mapping suggestions
Dynamic removal of duplicative Bates start and Bates end rows from mapper when used for image mapping
Removed image_file from destination field list in order to reduce attempts to use conflicting image mapping fields (still available for image mapping)
Added a user confirmation to the “Back” button when working in load file mapper to avoid unintentional loss of mapping settings
Informational UI Updates
Added import timings back to import batch list via DATA > Import
Expanded reporting for load file formatting errors, specifically when there is an encoding issue