Admins Need To Have Ability To Use A Separate Record ID For Imports
Admins need to have the ability to import via a separate record ID than what is displayed for end-users.
For better usability, most Record ID's are setup with multiple fields; such as, Auto Number, Category Field, Another Field.
However, for an admin, we often export large amounts of data, update in a spreadsheet, then need to import back in.
In the current setup, we must include all the fields that used in the Record ID, even if they are not the fields being updated. If we don't remember to include them, then all the work done in the spreadsheets is lost when we have to export again.
We need to be able to import and specify a different field as the record ID - such as a single "counter" type. In the classic version, we could import via Record Locator, or any other field we specify.
John McGarvey
shared this idea
2 comments
-
Matt Cox
commented
having to change the record ID to a counter requires all imports to be done after hours or have users be utterly confused during the time you are importing. having the ability to import based on an admin record id or a unique field in the table would be a huge help.
-
Anonymous
commented
Janky way around this that I've found:
Make the Record ID a calculated field, we'll call it "ID". Make a dropdown called "Import". In the ID field: The calculation says that if "Import" isn't "yes", do a concatenation for whatever ID you want to show. If it is "yes", make it the field you want to use for import. When importing, change all records so import is yes. Import, then change back. Not the most elegant, but it does work.