Passer au contenu principal
Adaptive Insights
Knowledge and Support - Adaptive Insights

Connect to Different Adaptive Instances

Explains how to connect to different instances and manage sandbox instances in OfficeConnect.

You may have access to more than one instance because you have multi-instances or a sandbox instance. Multi-instances are linked instances in a hierarchical relationship. The instances share data through account- and dimension-mapping. A sandbox instance is a clone of your production instance. You use it for test environments and what-if scenarios. 

How Multiple Instances Works with OfficeConnect

When you have access to many instances, OfficeConnect connects to your default instance. The data in the reports is from that instance.

You can connect to other instances through OfficeConnect. To connect to a different instance, change your default, or use a unique ID and password that has a different default instance.

Best Practice: Add the instance name to the file name of the workbook so you know the source of the data. Make sure your default instance is the same as the workbook's source.

Change Access to Instances

The instances you access depend on your User ID setup. This requires administrator permissions: 

  1. Clickand select Administration
  2. From the Users and Roles tile, click Users
  3. Find your User ID and click Edit
  4. Click the Instance access dropdown and select or clear the available instances. 
  5. Click the Default instance dropdown and choose the default instance.
  6. Click Submit to save your changes.

Instance access of a user from the Administration screen

Change Your  Default Instance in My Profile

If you don't have administrator access to the Adaptive Suite, use My Profile to change your default instance:

  1. Click the arrow in the User Profile UserMenu.png
  2. Click Settings
  3. From the Default instance dropdown, choose your default. 
  4. Click Save

Default instance selection from My Profile

Open Existing OfficeConnect Excel Reports

When you open existing OfficeConnect reports (.xlsxai workbooks), Adaptive verifies that your current default instance matches the instance that last populated the report. If it does, you can view and make changes as usual. If it doesn't, you get a warning message: 

Different instances warning message

Unless you are intentionally "sharing a report" across instances, click No, close the report, and log out of OfficeConnect. You can then:

  • Restart OfficeConnect and log in with an ID that has the same default as the workbook.
  • Change your default to match the instance of the workbook and restart OfficeConnect with the same ID. 

Share Reports Between Instances

Sharing reports between instances is possible but should be done with caution. 

The most common reason to share reports between instances is when you have a sandbox and production instance. A sandbox instance allows you to make changes without affecting the live, production instance. When you create reports with your sandbox instance, you may want to share it with your live instance or vice versa.  

Best Practice: Only share reports between cloned instances. Sharing reports between instances that aren't clones often results in invalid data because the element mapping may not be correct.

If you choose to share the report between instances, click Yes when you open the report and get the warning message. The report opens and uses the data of your current default instance without affecting the elemental structure of the report. In this case, be mindful of possible errors, discrepancies and invalid intersections.

To share reports between sandbox and production:

  • Keep it Cloned: Make sure the instances are the same before you share the reports.
    • If you made changes in one instance, make the same changes in the other in the exact same order.
    • If you don't want to keep changes you made in one instance, revert the changes so that it matches the original instances. 
    • If you share reports prior to making the changes to the instance, review the report elements carefully against the adaptive instance to ensure that intersections and data are valid before refreshing the report.
  • Audit Elements: Review the elements in the Review tab of the Reporting pane to make sure you are still pulling the data you expected and that the intersections are still valid. 
  • Use Labels: Label the data, especially noted discrepancies, so that you and others know what you are viewing. 
  • Develop File Name Protocols: State the instance associated with the workbook report.
    • If you built a report with changes that you later reverted, either delete the report, update it, or rename it to show its origin.
    • If you open the report with a different instance, be sure to rename it accordingly when you save and close it so you know which instance is populating the report.

What to Watch For

  • Discrepancies: If the structure or data between production and sandbox is different, there may be discrepancies in the reports.
  • "Unknown" in Cells: This may be a result of an element applied in the report from one instance that does not exist in the other.
  • Different Elements: The report from one instance may have different elements in the grid than the same report from the other instance.
  • Cet article vous a été utile ?