Review and Troubleshoot an Import

Start with the summary

The import workspace is designed around one question: what does Rivolq still need to know before it can add these records? After parsing, Rivolq states how many assets, maintenance schedules, vendors, and parts it found. It also reports how many columns it mapped automatically and how many source-evidence rows it set aside. If the summary looks right, answer the questions shown on the page. You do not need to walk through a mapping wizard or row table as a mandatory sequence.

Questions you may see

• Facility: choose where records belong when the file does not make that clear.
• Duplicates: decide whether similar records should update, create, or be skipped.
• Column: confirm an uncertain field mapping.
• Fixable values: accept or inspect a safe normalization.
• Needs attention: open the affected rows when Rivolq cannot make a safe automatic choice.

The Add to Rivolq button stays unavailable while required questions remain.

Optional power views

Use Check the column mapping, Browse all rows, or the duplicate comparison when the plain-language question is not enough. Changes made there return to the same workspace and update the open-question count.

Before adding records

Read the final sentence listing new assets, asset updates, maintenance schedules, vendors, and parts. If it does not match your intent, stop and inspect the questions or the detailed views. Nothing changes until you press Add to Rivolq. During the write, Rivolq shows progress and then opens the result for the completed batch.

After completion

Use the result to find everything created by the import, inspect failures, and assign any cleanup work. Keep the original source file for reconciliation. For file preparation and the overall flow, see import assets and facility data; for labeling the records you just created, see scanning assets.