BUG::SQL ENDPOINT::LEAK ACROSS WORKSPACES

[Element115]

ISSUE:

2 different workspaces, a new LH in the workspace on the left, and therefore I create the first new SQL query in its SQL endpoint.  

Why is this new query numbered 8 instead of 1, and obviously looking as if it is following the sequence #s from the queries in the other LH SQL endpoint in the other workspace???

[Anonymous]

Hi @Element115 ,

Thanks for using Fabric Community.
When I tried to reproduce your scenario, I cannot observe any issue - everything is working normally.

Can you please let me know the steps you followed, so I can repro this scenario at my end?

[Element115]

STEPS:

0__after logging into Fabric and navigating to a workspace, copy the URL

1__open a new browser Window, place it to the right (the source window is on the left) and paste and go to the URL

2__in the right window, navigate to an old workspace where you have a LH and a bunch of SQL queries in the endpoint and open the LH SQL endpoint and navigate to the SQL queries

3__in the left window, create a new workspace and a new LH

4__open the respective SQL endpoint and create a new SQL query in this endpoint

You should see the new SQL query numbering follow the sequence from the queries in the right window, which are in a different workspace.

[Anonymous]

Hi @Element115 ,

Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it.

Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link 

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Hope this helps. Please let us know if you have any other queries.

[Anonymous]

Hi @Element115 

We haven’t heard from you on the last response and was just checking back to see if you got a chance to open a support ticket.

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thanks

[Element115]

Yeah well not gonna do that. No time anymore.

[Anonymous]

Hi @Element115 ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to look into my previous comment.

Thanks