Troubleshooting Imports

Short answers to the problems that come up most often when importing entities and perspectives. The import messages appear in English, partly with internal terms such as "causal model" (the expected order) or "entity graph" (the entity). The full overview is in Import Entities and Perspectives: Status and Errors.

Where Do I See Why an Import Failed?

In the list of entities or perspectives, Last import shows Failed. Click the row: the details show where it failed and the error, and Copy error message copies it for support. The last successful import stays available.

"No Case ID set. The import will fail." or "Exactly one perspective key needs to be set."

The perspective has no case ID. In the perspective builder, right-click the activity that stands for a case and choose Case ID. See Create a Perspective.

"Each causal model needs to be a connected graph."

The expected order has activities without relationships, or groups that aren't connected to each other. Connect every activity to the rest, or remove the ones you don't need. See The Expected Order: Perspective Hypothesis, Shortcuts and Backjumps.

"The causal model has a cycle through … mark a relationship on it as a backjump"

The expected order contains a loop, and at least one relationship is marked as Shortcut or Backjump. As long as no relationship is marked, a loop doesn't stop the import; as soon as you mark any relationship, every loop needs a relationship marked as Backjump. Right-click one relationship of the loop and choose Backjump. See Perspective Modelling Best Practices.

"Each entity graph needs to be a connected graph."

Some objects of the entity aren't linked to the rest by a data connection. Add the missing data connection or remove the object. See Configure Objects and Relationships.

"Activity … is not configured" or "Relationship … is not configured"

An object or data connection of the entity wasn't confirmed. Open it in the entity builder and click Confirm. See Configure Objects and Relationships.

"No imported Entity Graph available"

The perspective's entity hasn't been imported yet. Import the entity first, then the perspective. See Import Entities and Perspectives: Status and Errors.

Why Can't I Import or Edit My Perspective?

Blocked due to parent entity configuration changes. means that the entity is being imported, has changes that aren't imported yet, or has never been imported. Import the entity first.

Why Can't I Edit My Entity?

Editing is currently not possible due to an ongoing import. means that a perspective built on this entity is being imported. Wait until it has finished.

The Import Fails with a Message from the Database.

Noreja couldn't read from the source, for example because the connection was refused, the password changed or a table is missing. Check the data source with Test and ask your IT. See Connect a Data Source, including the section for your system.

The Import Takes Very Long.

The details of an import show how long each step took. Large tables without indices on the key columns are a common reason. See Performance Tips for Large Imports and Prepare Your Source Data: Keys, Timestamps, Indices.

My Knowledge for Minerva Doesn't Appear after the Import.

Context for a perspective that has never been imported waits for its first import; until then it shows This context will be attached to the perspective on its next import. Context for an imported perspective is attached right away. Context for an activity works the same way, but depends on the import of its entity, not of the perspective. See Context Hub: Knowledge for Minerva.