Configuring Uploader's "Recall" functionality
In this section you will learn how the Uploader automatically recalls previously mapped and cleaned data making subsequent uploads easier and faster.
Last updated
Was this helpful?
In this section you will learn how the Uploader automatically recalls previously mapped and cleaned data making subsequent uploads easier and faster.
Last updated
Was this helpful?
Once the fields and data are initially mapped, subsequent upload logic can be recalled based on the optional , "userID" and "userGroup". Which, unlike other parameterized fields, are defined outside the schema.
Here's an example of using the userID
parameterized field to populate a field called user_id
for every row by pulling the property curUserID
from the browser.
There are two applications of Parameterized Fields in this example:
The curUserID
becomes the value of the userID
parameter, which is used to control recall.
Also, the userID
parameter is being used to populate the field user_id
within the uploaded data itself - this is optional.
If you are user neither userID nor userGroup, it will recall by uploader token. This means recall will be performed on the uploader level.
If you are passing a , it will recall by userID first.
If you are passing a , it will be recalled next by the userGroup.
While the Recall and the Auto-Mapping behavior is usually useful to speed up mapping and ease the upload process, there are some scenarios where it is undesired. Here are the settings to .