LogicAppsUX icon indicating copy to clipboard operation
LogicAppsUX copied to clipboard

When using SQL command, connections always goes to default and process doesnt work afterwards.

Open Blegun0723 opened this issue 1 year ago • 10 comments

Describe the Bug with repro steps

My process doent work, because my SQL connection always goes to default and not to the connection it suppose to have

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

No response

Screenshots or Videos

No response

Browser

Chrome

Additional context

No response

Blegun0723 avatar Sep 09 '24 13:09 Blegun0723

Snímek obrazovky 2024-09-09 153627

Blegun0723 avatar Sep 09 '24 13:09 Blegun0723

Hi @DanRandy23, could you provide steps to reproducing this issue? Which action are you using to have this happen? If you could provide a sample workflow, that'd also be helpful. Thanks!

Elaina-Lee avatar Sep 09 '24 20:09 Elaina-Lee

@Elaina-Lee, this might be linked to https://github.com/Azure/LogicAppsUX/pull/5612 which will be set to ETA 9/20. Let's see if we can get a repro first though and verify the fix

Eric-B-Wu avatar Sep 09 '24 20:09 Eric-B-Wu

@Elaina-Lee, this might be linked to #5612 which will be set to ETA 9/20. Let's see if we can get a repro first though and verify the fix

ah okay perfect, thanks for the update!

Elaina-Lee avatar Sep 09 '24 20:09 Elaina-Lee

@Eric-B-Wu @Elaina-Lee - No that feature is different, the issue customer facing here is while using SQL connector any operation it chooses the default server and database whenever we create the sql connection.

@DanRandy23 - What type of connection are you creating? Does it specify the server and database name in it.. Do you also see a dropdown for the server and database fields to change from default?

preetriti1 avatar Sep 09 '24 23:09 preetriti1

@preetriti1 I am using SQL query to get data from my database and it lets me to choose my created connection. But once I save it and exit the browser (or just refresh it), once I open the query, firstly it shows the connection is default, but if I click somewhere else and than again to the query, it shows the right connection. And because of this, triggering the Logic app automatically doesnt work, because the connection is default when triggered automatically.

Blegun0723 avatar Sep 10 '24 09:09 Blegun0723

@DanRandy23 What type of connection are you creating in SQL in the designer? image

With Sql server and windows authentication you already give the db name, so the above question. Also please share the definition snippet of your sql action from codeview so I can check from where default is coming in.

Could you please clarify what you meant by triggering the LogicApp? I am assuming when you open the designer you see default in the input but when you click somewhere else it is automatically updated... and you are not saving the logic app yet so how is it picking up intermittent value while triggering

preetriti1 avatar Sep 11 '24 15:09 preetriti1

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

github-actions[bot] avatar Sep 14 '24 16:09 github-actions[bot]

@preetriti1 I have an API connection to Microsoft SQL server, with authentication type Windows Authentication. Snímek obrazovky 2024-09-15 171538 Snímek obrazovky 2024-09-15 171558 Snímek obrazovky 2024-09-15 172752 I will try to explain the problem again. So I want the Logic App run (maybe I confused running logic app with triggering) at the start of every week automaticaly. But it is failing because of the connection being default (as in picture 1), even though I saved the connection (like in picture 2). And it always shows firstly default when I enter designer before it shows the right connection.

Blegun0723 avatar Sep 15 '24 15:09 Blegun0723

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

github-actions[bot] avatar Sep 18 '24 16:09 github-actions[bot]