admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2022-03-31 17:00:01 +00:00
parent 156ef81b51
commit 9f05df3c04
6 changed files with 18 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/8.0/ayanova/docs/adm-import.md
View File

@@ -38,6 +38,10 @@ If no errors are found then the record is saved into the database and a success
If errors are found during validation no save is made and the error message is added to the results list displayed in the Import form once import has completed.
When import has completed the *import* result list will show any errors or imported records and "Process completed".
Records not imported due to already being present will not show in the *import* result list.
### Import items are automatically tagged
To make it easier to identify and if necessary mass delete imported records (for example if a mistake was found), imported records are automatically tagged with a unique time-stamped import tag. The time stamp is the same for that entire batch imported at once making them easy to identify.
@@ -70,6 +74,10 @@ The key (usually `Name`) field can not be updated as it's used to match records.
Unlike the import process, updated records are _not_ automatically tagged (the only way to undo an update is to [restore from backup](ops-restore.md)) however you can still see which records were updated if necessary by viewing the [User history](ay-history.md) of the User who ran the update.
When update has completed the *update* result list will show any errors or updated records and "Process completed".
Records not updated due to not matching an existing record will not show in the *update* result list.
### Partial record updates
There is often a need to only **partially** update existing records in **specific** fields.