Forum Discussion

jose_henrique's avatar
jose_henrique
Frequent Visitor
1 year ago
Solved

SQL Endpoint error: Failed to complete the command because the underlying location does not exist.

Hello everyone. I have a lakehouse that's connected to Dataverse with the Link to Fabric function. Also, I'm connected to Customer Voice preview feature. The problem is: I ran a Logic App that star...
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi jose_henrique 

     

    Sorry for the late response. I don't find a specific API or something else that can help refresh the SQL Endpoint of a lakehouse automatically. I captured the trace of the "refresh" action in Explorer. It seems trigger a metadata refresh of the SQL endpoint. But I failed to covert it into a valid call we can use for the automation process.

     

    You may try setting a longer waiting time after starting the capacity. If this still doesn't work, I would suggest creating a support ticket to ask escalation engineers to help check the failue. This looks more like a synchronization issue.

     

    In addition, a lakehouse generates a default semantic model. You can manage the default semantic model or create customized semantic models from it. Maybe you can consider using the default semantic model or customized semantic models for your reports. Default Power BI semantic models - Microsoft Fabric | Microsoft Learn

     

    Best Regards,
    Jing