Forum Discussion

Paolo_Zorzi's avatar
Paolo_Zorzi
New Member
3 years ago
Solved

DM_GWPipeline_Gateway_MashupDataAccessError

Buongiorno a tutti, creando un nuovo report che si basa su di un nuovo set di dati, ricevo questo errore quando cerco di aggiornare il report : Errore dell'origine dati: {"error":{"code":"DM_GWPipel...
  • v-yueyunzh-msft's avatar
    3 years ago

    Hi , Paolo_Zorzi 

    Thanks for the detailed error message providing and based on my research and query on them, I think the error message you are seeing indicates that the key does not match any row in the table. This error can occur when the name of a table or sheet has been changed or dropped for any reason.

     

    To fix this error, you need to modify the M script for the failed query in Power BI Desktop. You need to go back to the original .pbix file of this report or download the .pbix file again. You can do this by opening the Power Query Editor and navigating to the affected query. If you don't see the exact error, click on Refresh Preview and the same error will be visible there. If you click on Advanced Editor, you will see the M script. You can fix the issue by changing the name to the new name or by clicking on "Edit Settings" button in the alert message.

    Here's one blog that also explained the root cause for this error message in detail, please also kindly refer to:

    Understanding The “The key didn’t match any rows in the table” Error In Power Query In Power BI Or Excel - Chris Webb's BI Blog (crossjoin.co.uk)

     

    Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

     

    Best Regards,

    Aniya Zhang

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