How do I read the import report?

Every import writes a report in plain language. It lists anything that did not come across exactly, where it is, and what to do about it. Nothing is dropped without a mention.

Open the report

1. #

   Open an imported course. The header shows the number of findings, for example 3 findings.

2. #

   Select the findings count. The Import report opens.

3. #

   Choose Close report or press Escape to go back to the slides.

Work through the findings

1. #

   Start with Needs your attention: features that could not be carried across, or source data that was broken.

2. #

   Then read Please check: things Xogogy could read more than one way, and questions whose answer key was not in the file.

3. #

   Good to know lists small differences, such as an effect that plays a little differently.

4. #

   Each finding is one plain sentence and says What to do. Repeated findings are grouped with a count, so one fix can cover many.

5. #

   Under each finding, the places it occurs are listed once each, with a count when it occurs more than once in the same place. Objects the original file names only by an internal code are listed by what they are, such as Shape or Group.

6. #

   Where the importer recorded technical detail, such as file names inside the package, open Technical details under the finding to read it. The saved report keeps it too.

The findings count in the header and the Import report heading always show the same number.

Fonts and variable names

Two more lists appear when they apply:

• Fonts not in the project names fonts the course uses that have no font file in the project. Learners who do not have one installed see a similar standard font instead. To choose the fonts yourself, change the heading and body fonts in theme colours and fonts, or ask your AI assistant to replace the font across the course. The list updates by itself once the course no longer uses those fonts.
• Text that names a missing variable lists text that refers to a variable the course does not have, such as %BreaksPlaned%. Fix the spelling or add the variable; see show a variable in text.

Checks on the course itself

The report also checks the course as it was built, so you catch problems the original already had before your learners do. These lists are not import losses: they do not add to the findings count, and nothing changes until you change it.

1. #

   Buttons that do nothing lists buttons with no link and no interaction.

2. #

   Triggers to check lists triggers whose order makes them misbehave, such as two that undo each other on one click, or a jump that stops the triggers after it. Each row is marked Mistake, Check this or Tidy, says what happens in plain words, and links to each trigger involved. Choose one to open it on the Interactions tab, where Xogogy offers a fix when it has a safe one. See fix a trigger order warning.

3. #

   No way forward lists slides and layers a learner can reach but cannot leave, such as a slide with Next hidden and nothing else that moves on. Never means no path leads on; Sometimes names the condition that does. Choose the row to go to the slide or layer.

4. #

   Text that does not fit lists text boxes whose text is cut off or that run past the edge of the slide. See find text that does not fit.

5. #

   Spacing and punctuation lists small typing slips, such as two spaces or a word typed twice, each with its own Fix button. See fix spacing and punctuation slips.

The Course overview in the Inspector shows the trigger count too, on its Advanced entry, for example 2 triggers to check.

Find the slide

1. #

   Switch between By finding and By slide to see the report the way that suits you.

2. #

   Type in the filter to narrow the list.

3. #

   Select a named slide or object to jump straight to it in the editor.

Keep a copy

1. #

   Choose Course settings › Advanced.

2. #

   Under Import report, choose Save report. Xogogy writes fidelity-report.md into the project folder.