Migration from Export to DataLake to Azure Synapse Link for Dataverse => Impact lower case headers

[joko29]

Hello,
we are migrating from Export to DataLake to Azure Synapse Link for Dataverse.
We have mayor impacts comming a) from lower case headers and b) from different file/header structure now in Synapse Link.

A) Power Query is case sensitive => one must change all related M code

B) Due to the changed Headers most of the relations in the data Model disconnect and need to be connected manually again

C) the Data Model / File structure comming from Synapse link is different from Export to DataLake: e.g. Attribute, WHSInventTable does not contain the codes directly. I am still searching for them in other files. I guess there are others
D) at the end we need to rework all our reports, since PBI Desctop is case sensitive in relation to fields located in reports (as I understand now)

Has anybody moved from Export to Datalake to Synapse link and had to handle similar impacts?
How did you solve it?
Is there a best practice?
Is there a tool to change the semantic Model integrated for all relationships AND the reports?
Any other hints?
Or do we need to do this manually for all our Models and Reports?
@Microsoft: What is the recommended way of migtation to Synapse Linke?

I hope somebody could help me.
Thank you,
Joachim

[PosturingWalrus]

Hi,

Did you manage to sort this? If so, could you share how you did it, please.

[Anonymous · Accepted solution]

Hi,@joko29 
I am glad to help you.

I'm sorry to hear that you are experiencing a case mismatch while performing the migration and need to think about changing the case of the fields and reconstructing the model relationships

At this time I have not found a good tool to help resolve your issue with migrating from Export to DataLake to Azure Synapse Link for Dataverse. Until then, I recommend that you continue to use manual human modifications to the data.

Here are some links on power query case modification that I hope will be helpful to you
url: How to tame Case Sensitivity in Power Query and PowerBI – (thebiccountant.com)
However, there is a drawback to this approach: the setting of the case parameter may not be applicable to all power query operations: you need to determine whether the change is feasible for all power query operations.

You will need to determine if the change is feasible for all power query operations.

You can try to add an extra step to the power query editor: make all column names upper or lower case (if possible). After adding this step, you will also need to make changes to subsequent power query operations.

The advantage of this is that if a similar migration problem occurs next time, you will only need to modify the current step, not the subsequent ones!

Modifying the parameter step in powerquery is very tedious, but it is very important: from the modification of the M-code to the reconnection of the data model relationships. Therefore, until a good alternative is found, I recommend that you continue to use the manual modification method.

Manual modification is the best way to manage the complexity of the relationships in the report and minimize the impact on the report.

If you can provide more detailed information about the existing problem, it will help to solve your current problem.

These are the links that may help you:

URL.
Create an Azure Synapse Link for Dataverse with Azure Data Lake in Power Apps - Power Apps | Microso...
Export to Data Lake in finance and operations apps - Finance & Operations | Dynamics 365 | Microsoft...

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.

Best Regards,

Carson Jian,

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