Data Import History and Troubleshooting

This page covers the Import History view, the job detail page, the 30-day data retention policy, and symptom-by-symptom resolutions for common Data Import issues.

Import History

The Import History tab at Setup > Manage > Import Data > Import History shows every past import job in a paginated table (20 jobs per page). Columns:

Click any row to open the Job Detail page.

Job Detail

The Job Detail page shows:

• Status banner — success, partial, cancelled, or failed with the error message.
• Statistics — total rows, succeeded, failed, status.
• Settings summary — target, operation, matching field, file name, initiator, start time, completion time.
• Download links for the Success and Failure CSV files (when available).

Data Retention

Import logs and result files are retained for 30 days from the import date. After 30 days, the log entry remains in the history list but the Success and Failure files are removed and become unavailable for download. Cleanup runs automatically each time a new import is executed.

Download files you need to keep for compliance or audit purposes within the 30-day window.

Symptom: A Target Doesn't Appear in the Wizard

Cause: The corresponding integration or module isn't enabled on the portal:

• Salesforce Entity requires an active Salesforce CRM integration.
• Dynamics CRM Entity requires an active Microsoft Dynamics 365 integration.
• Course Quiz requires the LMS module.

Resolution: Configure or enable the missing integration / module, then reopen the wizard.

Symptom: Many Rows Fail with "Required Field Missing"

Cause: A required field on the target entity isn't mapped, or the mapped CSV column has empty cells.

Resolution:

1. Return to the Map Fields step. Required fields are at the top, marked with a red asterisk.
2. Confirm every required field has a CSV column mapped.
3. Open the CSV and confirm the mapped columns are populated on every row.
4. Re-run the import.

Symptom: Lookup Field Rows Fail with "Not Found" or "Multiple Matches"

Cause: The lookup resolution method can't find the related record by the value in the CSV.

Resolution:

1. If using Match by Name and the related entity has duplicate names, switch to Match by Field with a unique field or Match by ID.
2. If using Match by ID, confirm the IDs in the CSV are valid 19-character Magentrix IDs (not Salesforce 18-character IDs).
3. For User/Owner lookups, consider Assign to me if all records should be owned by the importing user.
4. Spot-check 2–3 failing rows: do those values actually exist in the related entity?

Symptom: Picklist Field Rows Fail

Cause: The CSV value doesn't match any of the picklist options on the target field.

Resolution: Open the entity's field metadata and confirm the exact picklist option labels. The template hint row also lists valid options. Update the CSV values to match exactly (case sensitive in most cases) and re-import.

Symptom: Type Validation Warnings on Map Fields Step

Cause: Sample values in the CSV don't look like the expected field type (e.g., text in a Date field, missing @ in an Email field).

Resolution: Warnings are informational and don't block the import, but they predict per-row failures. Address them before running by fixing the CSV.

Symptom: Import Cancelled but Some Rows Already Imported

Cause: Cancellation is non-rollback by design. Rows processed before the cancel stay; rows after are skipped.

Resolution: Open the Job Detail page and download the Success File to see exactly which rows landed. To remove them, use the target system's normal delete workflow or run a corrective import.

Symptom: WebSocket Progress Stops Updating

Cause: The WebSocket connection was interrupted (network blip, proxy timeout). The import itself continues on the server.

Resolution: Refresh the page. The wizard falls back to polling for progress and the running job reconnects. Alternatively, navigate away and check Import History in a few minutes.

Symptom: Failure File Download Returns 404

Cause: The job is more than 30 days old and the result files have been cleaned up.

Resolution: Result files are retained for 30 days only. If you need the failure list, re-run a fresh import.

Symptom: Activation Emails Aren't Arriving (Portal Users Target)

Cause: Email delivery issue or the user's Contact lacks a valid email address.

Resolution:

1. Confirm the portal's email configuration is healthy (check the Email logs).
2. Confirm the user's Contact has a valid email address.
3. For large imports, allow 5–10 minutes for email delivery; large batches stagger.
4. Check spam folders.

Symptom: GIFT Import Skipped Questions

Cause: Malformed GIFT syntax, unsupported question type (Numerical, Matching), or missing blank line between questions.

Resolution:

1. Open the Job Detail page; the Failure File and the preview parse warnings list which questions were skipped and why.
2. Fix the GIFT file: ensure blank lines between question blocks, escape special characters with backslash, use TRUE/T/FALSE/F for true-false questions.
3. Re-import.

Symptom: Translation Import Many Rows Fail with "Item Not Found"

Cause: The underlying translatable items (fields, picklist options, etc.) were deleted or renamed between when the template was downloaded and when the file was uploaded.

Resolution: Re-download a fresh template, copy your translations into the new file, and re-upload.

<< Importing Course Quizzes (GIFT)