Using Dataflow Gen2 to Populate Dataverse Incident Table

[stephanjenner]

Ok, so I have an Excel Spreadsheet with a bunch of customer complaints, and I want to ingest the spreadsheet and create incidents (cases) in Dataverse. I attempted to do it via the Power Apps Dataflow, but it does not support the Customer Polymorphic lookup column nor other lookup columns like Subject (It only supports custom lookup columns)

SO I then went to Power BI and set up a Dataflow Gen 2 after linking my Dataverse environment to Fabic.

I now have a well-structured Power query, and I have set all the appropriate fields (including the customerid and the customerid_entity_type) But when I run the data refresh with the destination set to the incident dataverse table I get the error:

Case_Incident_WriteToDataDestination: There was a problem refreshing the dataflow: 'Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: AzureDataLakeStorage failed to get contents from 'https://onelake.dfs.fabric.microsoft.com/753c6c76-5e1f-45d1-9d3b-6ccc22369522/1be27d51-a43f-460e-971...'. Status code: 405, description: 'MethodNotAllowed'. Details: Reason = DataSource.Error;ErrorCode = 10266;DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;DataSourceKind.2 = AzureDataLakeStorage;DataSourcePath.2 = https://onelake.dfs.fabric.microsoft.com/753c6c76-5e1f-45d1-9d3b-6ccc22369522/1be27d51-a43f-460e-971... = https://onelake.dfs.fabric.microsoft.com/753c6c76-5e1f-45d1-9d3b-6ccc22369522/1be27d51-a43f-460e-971... = User'. Error code: Mashup Exception Data Source Error. (Request ID: 75e350ea-c65e-4ff6-8edf-c73f9c65f4c5).

Is this not supported? as In I cannot write to the dataverse incident table or am I missing something

[v-sathmakuri]

Hi @stephanjenner ,

I hope the information provided is helpful. Feel free to reach out if you have any further questions or would like to discuss this in more detail. If responses provided answers your question, please accept it as a solution so other community members with similar problems can find a solution faster.

Thank you!!

[v-sathmakuri]

Hi @stephanjenner ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the responses has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you!!

[v-sathmakuri]

Hi @stephanjenner ,

May I ask if above provided information is helpful? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you!!

[burakkaragoz]

Hi @stephanjenner ,

Hello! The problem you are experiencing indicates that there is a permission problem when writing data to Dataverse with Dataflow Gen2. Here is the key point in the error message:

403 Forbidden - AccessDenied
Microsoft.Data.Mashup.MashupSecurityException.Reason = AccessDenied

This indicates that Dataflow does not have permission to access the DataverseIncidentTable directory in Lakehouse that you specified as the target.

Possible Causes and Solutions:
1. OneLake Access Authorizations
Make sure that the user account Dataflow is running on has write permission to the target folder (DataverseIncidentTable) in OneLake.
Go to the relevant folder in the Fabric portal and authorize the user or service account as “Contributor” or “Owner” in the “Manage Access” section.
2. Linked Services and Credentials
Power BI Dataflow Gen2 uses Linked Service in the background. Make sure that this connection is configured correctly and that it works with valid credentials.
If necessary, try deleting and recreating the Linked Service.
3. Polymorphic Lookup Limitations
It is true that Power Apps Dataflow does not support polymorphic lookup fields. However, it may not be possible to write these fields directly with Power BI Dataflow Gen2.
Alternatively, you can import data into a staging table before writing to the incident table and then use Power Automate to move data from this staging table to the actual incident table.
4. Import Excel File Directly into Dataverse
If Dataflow becomes too complicated, you can also import the Excel file by connecting it directly to Dataverse with Power Query. But again, special solutions may be required for polymorphic fields.
Suggestion:
First, check the access authorizations to the destination folder within OneLake. This is usually the most common and easily solved problem.

[v-sathmakuri · Accepted solution]

Hi @stephanjenner ,

Thank you for reaching out to Microsoft Fabric Community.

Currently Dataflow gen2 does not support dataverse tables as destinations. please go through the below documentation for reference.

https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-data-destinations-and-managed-se... 

If you feel that this feature should be added, I recommend submitting your detailed feedback and ideas through Microsoft's official feedback channels, such as the Microsoft Fabric Ideas.  

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!