After migrating a cube to a new environment, an error appears when editing or running a cube

Description

After migrating a cube to a new environment, users may find that their cube can't be run or edited. Instead, the following error appears:
"Create XXX Report Instance error. Please check the metadata. The object does not exist in the metadata."

Steps to Reproduce

• Create an Object Manager package to migrate a cube without migrating the database instance for that cube.
• Edit the cube in a new environment.
  

• Click the drop-down arrow on a table and click Edit Table.
  

• Try connecting to a DSN from a previous environment. Notice the error appears.
  

Why is this happening?

The cube fails to run because the database instance was not migrated. As a result, the database instance the cube was using in the source environment is not present in the destination environment.
This can be confirmed in Developer:

This can also be confirmed if you try to open the Object Manager package in the new environment. You will see that the database instance does not appear.

Solution

To successfully run and edit your cube, you must migrate the database instance from the source environment to the new environment.