Skip to main content
G
GParreiras
Contributor
May 13, 2025

Best Approach for Exporting and Importing a Dashboard into a New Application

  • May 13, 2025
  • 1 reply
  • 0 views

Hi all,

What is the best way to export and import a dashboard into a new application?
Do I need to select all its components every time, even if some already exist in the destination?

I’ve noticed that if you select only the dashboard or the embedded version, the components don’t appear in the XML file.

Thanks in advance!

1 reply

J
OneStream Employee
JackLacavaOneStream Employee
OneStream Employee
June 3, 2025

If components already exist at the target, you should not need to import them again. Yes, only selected items are placed in the exported file, even if they are linked to other items.

To reduce this kind of work, consider keeping the dashboard and all its objects in a separate workspace or maintenance unit, and then export/import the entire Workspace or MU.

    G
    GParreirasAuthor
    Contributor
    June 3, 2025

    I’ve noticed that when I export a dashboard, I still have to select components that already exist in the target environment, not just the new items. So I’ll need to export all dashboard components each time or, as you mentioned, the entire workspace.

    Thanks.

    R
    Rithik_Prem
    Newcomer
    June 4, 2025

    Yes, I too believe this is the best approach. Exporting and importing the entire workspace or maintenance unit that contains the dashboard, and all its components simplifies the process and helps avoid missing dependencies. Also, if components already exist in the target application, there’s no need to re-import them, which saves time.

      Terms & ConditionsAccessibility statement