Unanswered

Import Dataverse tables from one Tenant Environment to another Tenant Environment

(0) Share

Report

Posted on by dheeraj_g

Hi,

Currently I'm trying to import a cloud flow from one environment to another environment in a different tenant. This is done by exporting the process from the first environment and importing the zip file to the second environment in a different tenant.

The cloud flow involves actions to read and write data to and from a Dataverse table but while importing the flow facing the following issue:

From the error message it looks like it is looking for a Dataverse table with a specific name however, each table created has a unique name and we will not be able to create another dataverse table with the name 'crf1c_globalvariables'. Since Power Automate assigns a unique prefix to a dataverse table, even if we were to create another one with the same name a different and unique prefix is assigned to the table in the new environment.

This is true even when we are trying to import a dataverse table from one environment to another

Can someone help us with this issue and guide us on how to configure the Dataverse table in order to make it importable.

Thanks

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

powercorner 477 on at

Like (0)

Report
Copy link

Link copied!

Hello @dheeraj_g

looks like your exported/imported solution contains something that your tenant does not contain.
Can you show us what is all inside your solution?

With regards,
Kevin

Was this reply helpful? Yes No
dheeraj_g 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @powercorner . Yes. As mentioned above, the dataverse is not part of the tenant. The reason being, the name of the dataverse is unique in each of the tenant and when import/export is done there is an error as the names dont match

Was this reply helpful? Yes No
powercorner 477 on at

Like (0)

Report
Copy link

Link copied!

Hi @dheeraj_g

in order to help you more, you need to give me more info. Show me your solution. Explain the process what you are doing. What kind of enviroments do you have? Dev? Default? Prod?
Is the solution managed / unmanaged?

It would be the easiest for me to create your scenario in my tenant to see where the problem could be located.

With regards
Kevin

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @dheeraj_g,

You should be using a solution to transport all your customizations and it's dependencies. Ideally you would create a custom publisher in your source environment and create your components within a Solution using that publisher. That way the prefix will be the same when moving it across the Environments.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No