Overview
An Import Run creates one Mobaro Assignment for each ready Import Row in its scope. Rows can succeed or fail independently, so review the results before retrying.
At a glance |
|
Who can do this | Active Mobaro Users; a write-enabled organization API key is needed to import. |
Where | Assignment Importer › mapping screen › Import to Mobaro |
Works on | Assignment Importer desktop app (Windows x64 / macOS Apple Silicon) |
Availability | Contact your CSM |
Review before importing
Confirm the API key belongs to the intended organization and permits writing.
Review title and description templates, Location, Assignee, Assignment Definition, Priority and any Asset.
Resolve attachment problems, or decide explicitly whether missing files may be omitted.
Choose Save Project to preserve the preparation state.
⚠️ Heads-up: The toolbar’s Import to Mobaro imports every R row in the Import Project, including ready rows hidden by filters or outside your selection. To import only selected rows, use the grid’s right-click Import to Mobaro action.
Run the import
1. Choose the scope
For a small first run, select only the intended R rows, right-click and choose Import to Mobaro. Every selected row must be ready for that action to be available. For the full ready batch, use the toolbar action.
2. Review any missing-file decision
If Missing attachments detected appears, cancel to fix the files or deliberately choose Continue without missing attachments. Do not treat continuing as a promise to add the omitted files later.
3. Let the Import Run finish
Watch Importing to Mobaro... and the row counter. Keep the app open while the run processes. Attachments upload before the Assignment is created for each row.
4. Review and save the outcomes
Successful rows receive a Mobaro ID, show C and become locked. If failures occurred, read the failed-row numbers and first error shown above the grid. Choose Save Project immediately to persist the created IDs, then verify sample Assignments in Mobaro.
🛑 Critical: An Import Run does not automatically save the new Mobaro IDs to the .mobproj file. Reopening an older saved copy can leave already-created work looking ready again. Save after the run. If the app closes, the network response is lost or a save fails, verify what exists in Mobaro before retrying.
Retry only the work still needed
For a completed run with clear row-level failures, correct the reported problem and review the remaining rows. Rows with a saved Mobaro ID are excluded from future Import Runs in that Import Project. A failed response does not always prove that Mobaro created nothing: reconcile uncertain outcomes first. Creating another Import Project from the same workbook does not carry over the existing IDs.
Manage created work in Mobaro using How to create and delegate an assignment and Resolving, documenting, and reopening Assignments.
Best practices
Import and inspect a small sample before the full batch.
Keep the saved Import Project with its created IDs as your record of the run.
Record the failed-row list before changing filters or retrying.
Frequently asked questions
Does one failed row roll back successful Assignments?
No. Import Rows are processed independently. Successful Assignments remain in Mobaro when other rows fail.
Can I use Assignment Importer to update created Assignments?
No. Created rows are locked and skipped by later Import Runs. Make changes to the resulting Assignments in Mobaro.
Why is the selected-row import action disabled?
Every selected Import Row must have status R. Remove incomplete, skipped or created rows from the selection, and wait for any current import, attachment scan or reference-data reload to finish.