Outlined below is a list of Protected System Fields in every Nextpoint database.
Data cannot be imported into any of the below fields because they are generated by the Nextpoint application. If you’d like to map any of the below values into your database, you must set up a field with a different name.
Common fields replaced and suggested replacement values provided in parenthesis.
NOTE: All Default Fields and Document Attributes can also be considered Protected fields as we will prohibit creation of duplicative fields (because they already exist in every database). See the full list here >>
|Protected Field||Suggested Alternative|
|Filename||(use existing File Name)|
|Filepath||(use existing File Path)|
|Bates||(use existing Bates_start and Bates_end as applicable)|
|Created_at||(use existing Created_Date_Time)|
|Original_filename||(use existing File Name)|
Is Document Date also a protected field?
Technically, yes, Document_Date is a protected field as it cannot be created as a Field in your database.
However, we often refer to Document_Date (and Date) as Default Field, meaning you do not need to set up a new field under SETTINGS > Coding. Instead, if you have a header value in Row 1 of your load file, make sure that the load file value matches the fields outlined in Product Data Import Exhibit A >> https://support.nextpoint.com/hc/en-us/articles/360032944171.
I hope this information is helpful!
Please sign in to leave a comment.