After running a configdump import, there can be references that could not be solved in the first import. As a workaround, you can run the import again.
We should handle this automatically. It could work as follows:
- After the import attempt, check if there are items with reference problems.
- For each problematic item, try to import it again (with update as overwrite action).
- If the update also fails, show the error from the first import attempt (so the user knows the value has been set to the default)
- If the update succeeds, don't report the error to the user.
Reference problems can still happen if an object is missing from the dump. Default/skip prompt should still work for that case.