Review a monthly records import
Give a data owner a preview of new rows before they are added to a shared collection.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
Take a selected comma-separated file, organize its rows, and prepare them for an existing structured record collection. Keep a preview of the incoming information alongside the original file so a data owner can check the columns, destination, and likely effect before approving an import.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Organize the file rows for a chosen destination, show any unclear or mismatched fields, and wait for a data owner to approve the import.”
Clear tasks, with review where it matters.
Helps a team prepare tabular file contents for an existing collection without hand-entering every row.
Columns may not match the destination, and repeated or malformed rows can create incorrect records. Keep the source file unchanged, review a preview and any existing-record conflicts, and require an authorized data owner to approve the exact destination and import before records are added or replaced.
Select an illustrative task to explore its proposed role. No workflow runs here.
Confirm the file is in an approved location and identify the existing collection that should receive its rows.
Check the headings, sample values, row count, and any missing or unexpected information.
Show how each file column corresponds to the destination and flag mismatches or repeated records.
Have the data owner review whether the import adds new rows, overlaps existing information, or could replace content.
Proceed only after an authorized person approves the source file, destination, and treatment of existing records.
Confirm the file is in an approved location and identify the existing collection that should receive its rows.
These are planning notes for the concept, not instructions for a currently available template.
Define which file locations and existing record collections are approved for this import task.
List required headings, accepted values, and how file fields correspond to destination fields.
Name who checks the preview, resolves conflicts, and approves adding or replacing records.
Try a typical file, a missing-column example, and duplicate entries to ensure each issue is visible before import.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation