Lakehouse error with source control

[DennesTorres]

Hi,

I'm not sure how to reproduce this error or if there is anything I could check to fix it, but it seems to be a serious bug.

Consider the following lakehouse:

Mind the name "test". It's on a Test workspace, intended to be the "Test" stage on the development process (dev/test/prod).

The error:

If I open the lakehouse and change the top-right drop down from "Lakehouse" to "SQL Endpoint", Power BI takes me to the SQL endpoint of the Dev environment, not test environment. This means that out of the blue I end up in a completely different lakehouse, in a different workspace.

When I try to change back to "Lakehouse", an error happens and I can't change back.

If, instead of opening the lakehouse, I open the SQL Endpoint directly, it works fine.

The error started after a merge was done from the Development Branch to the Test Branch. A deployment pipeline could not be used because of the ownership of the objects, a problem I described before in another message.

Is there something I could check about this?

Kind Regards,

Dennes

[Anonymous]

Hi @DennesTorres ,

Thanks for using Fabric Community.

Apologies for the issue you are facing. 

Inorder to reproduce the issue, I had created a sample workspace (dev) and then moved dev to test using developement pipeline.

Dev Workspace:

Deployment Pipeline (dev to test) :

Test Workspace:

After creation of test environment, I am able to switch between Lakehouse and Sql Endpoint within the test environment without any issues.

Can you please share few more details so that I can help you in fixing your issue or filing a bug?

[DennesTorres]

Hi,

I'm not using development pipeline for the move between Dev and Test.

Each one is linked with a different source control branch in Azure DevOps, I did a pull request between them and a merge in Azure DevOps.

This is the scenario. However, I'm not confident about steps to reproduce. 

Kind Regards,

Dennes

[Anonymous]

Hi @DennesTorres ,

Apologies for the issue that you are facing.

This might require a deeper investigation from our engineering team about your workspace and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

[Anonymous]

Hi @DennesTorres ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to create a support ticket. If yes, please provide the ticket number here as we can keep an eye on it.