416.467.9100 | Dundas Data Visualization | Login
Welcome Guest
This is the support page for the legacy Dundas Dashboard application. For assistance with the current Dundas BI application please click here.
Dashboard v5.0

This site makes extensive use of JavaScript.

Please enable JavaScript in your web browser and reload the page before proceeding.

Copying Objects or Projects and Rewiring

Hide navigation
RSS
Modified on Wed, 02 Jul 2014 11:48 AM
Click to return to: Documentation | Getting Started


Overview

This article shows how to:


These options allow users to quickly re-use and re-locate existing business objects with little effort.

Project Copy and Duplicate

When you login to Dundas Dashboard as an administrator, the Copy Project and Duplicate Project buttons will be located at the top of the Design Explorer:

The 'Copy Project' and 'Duplicate Project' buttons.

The 'Copy Project' and 'Duplicate Project' buttons.


You can also copy or duplicate a project from the Administration screen:

The 'Duplicate Project' button.

The 'Duplicate Project' button.


You can find more information on these operations below:


Note: The duplication and copy options only allow you to copy and duplicate objects within the same data store. If you want to copy the project to a new data store, use the project manager utility.

Copy project items to another project

This option copies all objects in a project (including all data objects, dashboards, mashups, and resources), into another project that you specify. A new copy is created, and the items in the source project are not affected. The copy project window allows you to specify the target project for the operation:

The 'Copy Project To' window allows you to specify a target for the copy.

The 'Copy Project To' window allows you to specify a target for the copy.


Duplicate a project

This option creates an exact duplicate of the current project. The source copy is not affected by this operation. This is useful when you want to work on a copy of a project, without changing the original. A new project will be created in the current data store. The project duplication window allows you to name the newly created project:

The 'Duplicate Project' window allows you to specify a name for the newly created project.

The 'Duplicate Project' window allows you to specify a name for the newly created project.


Note: For large projects, duplication might take a long time, and may even time out (error message: HttpRequestTimedOutWithoutDetail) depending on the ClientCommunicationTimeout setting on the Dundas Dashboard Configuration File. To resolve this issue, increase the timeout value. Make sure that you've removed the start and end comment tags and Recycled the App Pool.

Copy an object to a new project or folder

Most business objects can be copied between projects or folders using the Copy and Paste commands in the Design Explorer:

The 'Copy' command copies a business object into memory.

The 'Copy' command copies a business object into memory.


The 'Paste' command creates a business object from the in-memory copy.

The 'Paste' command creates a business object from the in-memory copy.


Copying and pasting between projects or folders is a shallow copy, meaning the dependencies for those objects are not copied. For this reason, when copying between projects it is recommended that you either copy the dependent objects to the new project first (starting at the data connector and moving up the chain), or copy the entire project and delete objects that you don’t need.

When the shallow copy operation completes, if the object has dependencies, the rewire dialog will appear automatically. If the copied object has any dependencies which do not have compatible objects in the target project, you will not be able to complete the paste operation; you will have to copy the dependent objects (or create new, compatible objects) before performing the copy/paste operation.

Note: The Cut operation is used for moving objects between sub-folders in the same project; it does not support copying objects between projects. If you want to perform a cut operation between projects, copy and paste the object into the new project, then delete it in the original.

Rewiring

The rewiring feature allows users with 'designer' or 'developer' rights to quickly and easily change the underlying data and resources on which an object depends. This allows you, for example, to change the KPIs, filters, and resources used by a dashboard, without having to edit the dashboard manually.

The rewire dialog allows you to specify new dependencies for the object.

The rewire dialog allows you to specify new dependencies for the object.


The rewire dialog will appear whenever you:

  • Paste an object with dependencies to a new project.
  • Choose Rewire from the context menu of an object in the design explorer.

Note: You can only rewire an object when it is checked out. If an object is checked in, the rewire option will not be available. Additionally, the rewire option will be unavailable if the object is open for editing in the content area.

Dependencies will be automatically updated when an object is created as part of a project copy or project duplication, to use the newly created items in the target project.

The following table shows the dependencies that can be rewired, for each type of business object:

Object Type  Dependencies that can be rewired 
 Data Connector  N/A 
 Virtual Table  Data connector, columns from source table, view, stored procedure or function 
 Virtual Cube  Data connector, source cube 
 Dimension  Data connector, virtual table 
 KPI/dataset  Data connectors, virtual tables/cubes, dimensions 
 Dashboard/Dashblock  KPIs/datasets, Resources (Templates, Images, Maps), Filters, Dashboards/Dashblocks 
 Analytical Dashboard/Dashblock  Virtual Cubes, Resources (Templates, Images), Dashboards/Dashblocks 
 Templates  Images 

Additional information

When rewiring an object, or copying an object between projects, the following rules will be observed:

  • Copying an entire project will copy all annotations for KPIs or datasets defined in that project. Copying only a KPI or dataset will not copy annotations.
  • Copying an entire project will also copy all annotation groups defined in that project. Copying a KPI or dataset will copy any annotation groups defined on that KPI or dataset.
  • When rewiring a virtual table, virtual cube or dimension, you can only change the data connector if there are no KPIs or datasets referencing that object.
    Tip: To work around this restriction, you can duplicate your object first, and then rewire your KPI or Dataset to use this duplicate object.
  • When duplicating projects or copy/pasting dashboards, notifications will not be copied.
  • Access rights will be preserved on objects that are copied across projects.
  • Check-in history will not be preserved during project duplication or when copying objects to a new project or folder.
  • When rewiring an existing KPI/dataset to use a different full dimension, any existing annotations on that KPI/dataset will become orphaned (invisible).
  • When duplicating a project or copying an item across projects, the new items will always be in a checked-out state. The copy will be the version which is visible to the current user; that is to say, the new object will be a copy of:
    • The checked-out version, if it is checked out to the current user.
    • The checked-in version, if it checked out to another user.

Example: Renaming a native database table

Suppose you have a standard virtual table that is based on a native SQL Server database table. If you subsequently modify the name of the native table (e.g. via SQL Server Management Studio), and then try to edit/checkout the virtual table, Dundas Dashboard will display an error telling you that:

Some of the underlying native structures have been renamed or deleted. You may want to rewire the current business object.

Follow these steps to rewire your virtual table:

  1. In the Design Explorer, right-click on the corresponding data connector. From the menu, choose Discover Data Structures. This will ensure that your data connector is updated with information on the renamed table.
  2. Right-click on your virtual table. From the menu, choose Rewire. The Modify Virtual Table Dependencies dialog is displayed.
  3. In the Data Connector Dependency Mapping section, choose the new data connector for your virtual table (should be the same as before).
  4. In the Native Structure Dependency Mapping section, choose the new (e.g. renamed) native structures to map to.
    Virtual table rewire.
  5. Click OK.

You can now edit your virtual table.

Notes

  • When duplicating a standard virtual table, depending on the order in which you applied filtering and aggregation on a column, the duplicated virtual table may have a different effective query than the source table. In this case, you will need to edit and reconfigure the duplicated table. For example, you will need to do this if you applied filtering first on a column, set an aggregator on the column, and then performed the duplication afterwards.

Related topics


Click to return to: Documentation | Getting Started

About Dundas | Contact Us Follow us on Twitter! | Privacy Statement | Report Site Issues

Copyright © 2009-2014 Dundas Data Visualization, Inc.