Forum Discussion

Nari1998's avatar
Nari1998
Helper II
2 years ago
Solved

There was an error when processing the data in the dataset.

Hi,

I noticed that refreshed in the desktop version gives no error and even to publish normally, however when the scheduled or manual refresh is done is get the following error in power bi service:

 

Last refresh failed: 2/22/2024, 6:24:30 AM
There was an error when processing the data in the dataset.

Data source error:[ValidateMarkupTags][ccon]Expression.Error: The key didn't match any rows in the table.. Key = [ccon][Id = "a70e6289-ff62-47e0-b017-0e6db5ed4a48"][/ccon]. Table = [ccon]#table({"odata.type", "odata.id", "odata.etag", "odata.editLink", "[email protected]", "Id", "Title", "Items", "IsLeaf", "ItemKind", "ItemName"}, {})[/ccon]. [/ccon];[ccon]The key didn't match any rows in the table.[/ccon]. The exception was raised by the IDbCommand interface. Table: Project Comments.
Cluster URI:WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID:f9c93654-a2c0-46e5-9f28-9ed5728c20b8
Request ID:6221f96e-b7ff-4914-8994-98e1036ef5f5
Time:2024-02-22 09:24:30Z

 

Can anyone help me with this ?

Need Help
  • Nari1998's avatar
    Nari1998
    2 years ago

    Hi all lbendlin and Anonymous , thank you for the reply, it just seemed to be a credential issue by which i had to edit the credentials for web in power bi service and then the issue was fixed 

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Nari1998 ,

     

    1. Please check that the rows in the template query are not referenced incorrectly, i.e. the primary key between the template query and the regular query is correct. For detailed information, please refer to the link: Solved: how to resolve Power BI error - the key didn't mat... - Microsoft Fabric Community.

     

    1. Please check that all data sources used in the semantic model are properly configured for scheduled refresh in the Power BI service. This includes authentication credentials, gateway configuration (if applicable), and any semantic model parameters that may affect how data is loaded and processed. For detailed information, please refer to the link: how to fix this Power BI Service Error: the key didn't match any rows in the table (pbivision.com).

     

    If your Current Period does not refer to this, please clarify in a follow-up reply.

     

    Best Regards,

    Clara Gong

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

  • Nari1998's avatar
    Nari1998
    Helper II
    2 years ago

    Hi all lbendlin and Anonymous , thank you for the reply, it just seemed to be a credential issue by which i had to edit the credentials for web in power bi service and then the issue was fixed 

  • snehal123's avatar
    snehal123
    New Member
    1 year ago

    Last refresh failed: 11/18/2024, 11:07:26 AM
    There was an error when processing the data in the dataset.Hide details

    Data source error:{"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Cloud data source refresh is not allowed in gateway setting."}}],"exceptionCulprit":1}}} Table: SalesRegisterTbl.
    Cluster URI:WABI-SOUTH-EAST-ASIA-redirect.analysis.windows.net
    Activity ID:9ce895e7-3425-4cb1-a6fe-298f838cbfa4
    Request ID:cd20fe3c-44c5-758e-5231-b84fd71f3d12
    Time:2024-11-18 05:37:26Z

     

    im facing this error can anyone help me out for this i have published dashboard in bi service and data contains from 2 diffrent server and five excel files from sharepoint 
    and i have setup geteway only for sql server dataset but still getting this error

    Error

     

    Data source error: {"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Cloud data source refresh is not allowed in gateway setting."}}],"exceptionCulprit":1}}} Table: SalesRegisterTbl.

     
    how to solve it