Operations
Import mappings
Map source columns into LynkPIM fields and reuse the mapping across jobs.
For workspace users and administrators · Updated October 1, 2026
What this module is for
Map source columns into LynkPIM fields and reuse the mapping across jobs.
Use this page when you need to complete the task yourself and understand what each action changes. The steps name the relevant screen, explain why the action belongs in the workflow, and state what to verify before moving on.
Before you start
- Sign in with a role that can view or change the records in this guide.
- Have the product, file, channel, or workspace information ready before starting an action that saves data.
- Use a small test record or file first when an action affects multiple products or a connected channel.
1. Create a mapping
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 1.1
Do this: Open Imports > Mappings and add a mapping with a descriptive name.
Why this matters: This keeps the create a mapping work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 1.2
Do this: In Column Mappings, pair each source column with its destination field.
Why this matters: This keeps the create a mapping work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 1.3
Do this: Save and test the mapping with a small file; correct unmapped or invalid values before a full import.
Why this matters: This keeps the create a mapping work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
2. Maintain mappings
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 2.1
Do this: Review mappings whenever a source system changes its file layout.
Why this matters: This keeps the maintain mappings work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 2.2
Do this: Delete selected mappings only after confirming no repeat job depends on them.
Why this matters: This keeps the maintain mappings work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
Events and statuses to watch
Actions such as saving, importing, exporting, connecting, publishing, and approving can either update a record immediately or create background work. Wait for the on-screen confirmation and then check the relevant list, detail view, or job status before repeating an action.
- Saved or created: confirm the record appears with the intended values.
- Queued, running, or processing: wait for completion and open the job or event detail if progress stops.
- Failed, partial, rejected, or blocked: read the specific message, correct the source data or permissions, then retry only the affected work.