Import Dataflow from Json: Cross Tenant Refrence Error

[Anonymous]

Hi 

New here 😊...

I had deleted a few workspaces recently which contained some dataflows and reports(for testing purposes). My Admin then restored the workpaces, after which I got all the workspaces back along with all reports and dataset, but NO DATAFLOWS. Is this a normal behaviour?

I had also exported the Dataflows to Json before deleting and now when I am trying to create a Dataflow by importing from the Json, I am getting an error : "Cannot import "Dataflow name". Error code [DataflowContainsCrossTenantReferences]

Any help would be much appreciated

Thanks

[ichavarria]

Hi @Anonymous,

When a workspace is deleted, all the resources in it, including dataflows, are also deleted. If the workspace is later restored, it will only restore the reports, dashboards, and datasets. It's possible that the dataflows were not included in the backup that was used to restore the workspace.

Regarding the error you are getting when trying to import the Dataflow from JSON, the "DataflowContainsCrossTenantReferences" error occurs when the dataflow contains references to resources that are located in a different tenant. This can happen if the dataflow was exported from one tenant and is being imported into a different tenant.

To resolve this issue, you need to ensure that all the resources referenced by the dataflow are present in the tenant where you are importing the dataflow. This includes data sources, gateways, and other dependent resources.

You may also need to update the credentials for the data sources used in the dataflow to ensure that they are valid for the new tenant.

If you continue to have issues, you may want to reach out to your administrator or Microsoft support for further assistance.

Best regards, 

Isaac Chavarria

If this post helps, then please consider Accepting it as the solution and giving Kudos to help the other members find it more quickly.

[Anonymous]

Hi all,

I was in talks with Microsoft support on restoring dataflows from JSON once the original Workspace has been deleted. I was able to restore the standalone dataflows however, Linked dataflows could not be restored.
Now, Microsoft has just confirmed that Linked dataflows cannot be restored from JSON after the workspace has been deleted and it is a limitation. There is no backup solution available for Linked dataflows and that all the Dataflows would need to be created again. 

Just wondering has anyone come across this situation and has got any workarounds? 

Any help would be amuch appreciated.

Thanks

Deepak

[Anonymous]

Hi Isaac,

Thanks for the quick reply 😊

Even though the error says about multiple Tenants, I have only one tenant. 

One thing I have seen is that I have been able to import a base Dataflow which was not referencing other dataflow. The ones which have failed are all referencing this one and othe dataflows. Now, I have read that when you import dataflows their IDs get changed so the base dataflow might have a new ID now. So just wondering if it might be do do with the fact that the other dataflows are pointing to a dataflow ID which doesnt exist anymore? If this is the case, any idea how to find the Dataflow ID ?

Thanks again

Deepak

[dougie115 · Accepted solution]

For future users searching for an answer to this issue. In my instance the error came about by having to delete dataflows to remove old connections. When exporting and importing the dataflows back in they were required to be imported in order. But in doing this the dataflow "model id" was changed.

So to repoint the dataflow to the new linked dataflows you can update the exported json file text in two places. In the entities section for referenced entities update the "model id" value. Then in the referenceModel update the "id" value. Visual studio works really well in reading the JSON files.

To get these values simply create the referenced tables in a dummy dataflow and export the json and retreive the new values.

Hope this helps. It saved me multiple days of work.

[Anonymous]

Thanks very much @dougie115 . This is what I was looking for 😀