Automap SharePoint list columns and review the saved mappings
Automap to QA list on an Add SharePoint list item action creates/updates QA columns and saves generated value mappings. It is rules-based mapping, separate from AI PDF mapping, and changes the connected SharePoint list immediately.
Run Automap
- Give the service components stable Field IDs and save the service.
- Check where the QA site link points. QA and Production can point to the same physical list; the environment label alone does not isolate data.
- Open Add SharePoint list item. In add-new mode choose the site and QA list. For upsert choose the earlier lookup action that supplies the site/lists.
- Use Fetch/Refresh lists if metadata is missing, then select Create column mappings automatically → Automap to QA list.
- Read and confirm the dialog, then review the notification, generated columns and saved mappings.
Automap completed means generated mappings were saved. Apply is needed if you edit them afterwards. Repeating Automap overwrites generated mappings; unrelated mappings remain. It does not remove obsolete columns when a field is renamed or removed.
Generated columns reference
| Source | Generated mapping |
|---|---|
| Submission reference | SharePoint Title is displayed as _submissionId, with {{ form.submissionId }}. Its internal name stays Title. |
| Ordinary fields | Text columns named after component IDs, with field_to_text values. Multiline content uses multiline text. Dates/numbers/choices do not become native SharePoint types automatically. |
| Address | Separate line1–line5, postcode and country columns, even if the current address layout collects fewer parts. |
| File/document/map | The documented file-name/ID/download, document or configured map-display parts. Review actual suffixes and expressions. |
| Auto-generated component IDs | generatedId_... components are skipped. Set meaningful IDs for values that need columns. |
SharePoint display and internal column names can differ. Automap reuses a matching internal name or unambiguous display name; do not invent internal names or duplicate columns to make them resemble a Field ID.
Handle partial results
Some columns can change even when other changes fail. Successful generated mappings can be saved while errors identify the remaining columns. There is no automatic rollback of external column changes.
If saving mappings or refreshing failed, inspect the QA list before retrying. Resolve ambiguous display names at SharePoint, then Refresh lists. The editor has a 200-row mapping limit. Avoid repeated clicks while the operation is running.
Prepare Production and upsert
A separate Production list is not changed by QA Automap. Create compatible Production columns with matching display names, including _submissionId, then choose/refresh the Production list and Apply the reviewed action. Matching between environments ignores display-name case; internal names can differ.
For upsert, refresh/save the earlier lookup as well as the write action and verify aligned column order/value mappings. Automap does not synchronise the lookup's saved metadata. Test lookup-then-upsert in QA, then deploy the saved service separately.
Darcy can edit action settings but ordinary form-editing tools do not execute Automap or create external columns. Use this Builder control to perform the operation. See List add actions, List lookup actions and SharePoint site links.