Microsoft Dynamics 365 | Integration, Dataverse...

Is it possible to display data from one environment in another environment (same tenant)?

(3) Share

Report

Posted on by Varshitaa

Hi Everyone,

We have two environments in one tenant - Sales and Service. We have removed case table usage in Sales since Service org deals with all Service-related work. Our client now wants to see and work on case data from Sales.

The following process map:

Opportunity data in Sales environment
Case data in service environment
Both environments have Contact data common. They are maintained in their respective tables in each org, but we have a sync in place.

Our requirement:

Show case data in Sales environment, on the Opportunity form; in a tab or a sub-grid or any way possible.
Users should be able to perform CRUD operations on said Case data.
We will also add a new case button to the Opportunity form in Sales, clicking on it and creating a case should save the case record in Service org only, not in Sales.
Users should also be able to link Opportunities to the cases in Sales and same in Service too.
We don't want any Case data saved in Sales environment to avoid duplication and Storage issues.

Can you give me different methods to achieve this?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

#ManoVerse 360 on at

Like (1)

Report

Is it possible to display data from one environment in another environment (same tenant)?

Method 1 :

For CRUD support : Create a Canvas App connected to the Service environment. Embed this app on the Opportunity form in Sales. for this UI might feel separate from the dynamics experience. but will work for all.

Method 2 : You can use the virtual table in Sales Environment and configure it for Case , it will allow you to display data from an external source without storing it in local database.

But this would be limited for CRUD operation it can only show the data in read only , would be complex if you want to CUD.

Was this reply helpful? Yes No
Varshitaa 8 on at

Like (0)

Report

Is it possible to display data from one environment in another environment (same tenant)?

@#ManoVerse Thank you for your response.

Problem with Virtual Tables is that the provider we tried - OData V4 provider - is not allowing us to connect to Service org. Based on the information in the web, OOTB connectors will not allow one dataverse org to connect with another dataverse.

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/virtual-entity-odata-provider-requirements#odata-v4-data-provider-best-practices

We are planning to try out the Canvas App method - Creation of cases should work, I believe. What about linking the cases to Opportunities in Sales?

Was this reply helpful? Yes No
Suggested answer

#ManoVerse 360 on at

Like (0)

Report

Is it possible to display data from one environment in another environment (same tenant)?

You’re correct a virtual table won’t be suitable for this scenario due to its limitations.

For linking case to opportunity :

While creating a case in the Service environment by canvas app, save the Opportunity ID (GUID) on the case record. This will let you retrieve and update data later in the Canvas app based on particular Opportunity record. One opportunity can have multiple cases so it would be better to store opportunity id in service environment.

Was this reply helpful? Yes No
Suggested answer

Tom_Gioielli 2,572 Super User 2025 Season 2 on at

Like (0)

Report

Is it possible to display data from one environment in another environment (same tenant)?

Some of the requirements feel a bit contradictory, as you can't really "link" records together in an environment in any formal way without the records existing in the database. An embedded canvas app might work to be able to show the information, but the amount of synchronizing, duplicate checking, and background work for this will spiral out of control quickly.

I might recommend taking a step back, and asking if there is any reason that you can't simply merge the two environments together and use separate model driven apps and standard security settings for this? You already have a common Contact/Customer base, you want Opportunity and case information to be available to both groups, at this point wouldn't a migration be much simpler than trying to basically duplicate both databases in separate environments?

Was this reply helpful? Yes No