Logic apps support of Hierarchical partition keys in Azure Cosmos DB
I am trying to create document into a container that has 2 level of Hierarchical partition keys set. Using logic apps “Create or update document (V3)” connector, I can see that request is failing as bad request. Same request copied from logic app run history and execute directly in Cosmos DB editor it works. Wondering if Logic apps support Hierarchical partition?
Logic apps support of Hierarchical partition keys in Azure Cosmos DB
I am trying to create document into a container that has 2 level of Hierarchical partition keys set. Using logic apps “Create or update document (V3)” connector, I can see that request is failing as bad request. Same request copied from logic app run history and execute directly in Cosmos DB editor it works. Wondering if Logic apps support Hierarchical partition?
Nested For Each creating duplicates in Logic App
I have a problem where my nested For Each are creating duplicates an not sure how to correct it.
Scenario:
From system 1 we have multiple images coming into the LA, it needs to add it onto a record in D365 that can have multiple images already. I’m trying to setup the LA so that it will check the images on D365 and only add an image if that image doesn’t already exist.
Issue:
I have tried having a For each for the images on D365 nested in the For each for the images from system 1, but this created duplicates on D365. Summary of what happens:
enter image description here
Publicly available Oracle instance + LogicApp connection
I have a publicly available oracle instance and I want to connect to it from a logic app workflow. The problem is that it requires a data gateway which I don’t want to install.
On a side I have an old logic app that uses this db without any gateway. Why it’s enforced now? Was it like this always? How do I work around?
Publicly available Oracle instance + LogicApp connection
I have a publicly available oracle instance and I want to connect to it from a logic app workflow. The problem is that it requires a data gateway which I don’t want to install.
On a side I have an old logic app that uses this db without any gateway. Why it’s enforced now? Was it like this always? How do I work around?
Failed to retrieve dynamic inputs. Error details: ‘Request failed with status code 401’ – Azure Logic Apps, SQL connection
Hi I have created an API connection for connecting to SQLserver from logic Apps.
The API Connection has the default Server name, DB name, now I need to reuse the same SQL connection to connect to same server but different DB.
Failed to retrieve dynamic inputs. Error details: ‘Request failed with status code 401’ – Azure Logic Apps, SQL connection
Hi I have created an API connection for connecting to SQLserver from logic Apps.
The API Connection has the default Server name, DB name, now I need to reuse the same SQL connection to connect to same server but different DB.
Failed to retrieve dynamic inputs. Error details: ‘Request failed with status code 401’ – Azure Logic Apps, SQL connection
Hi I have created an API connection for connecting to SQLserver from logic Apps.
The API Connection has the default Server name, DB name, now I need to reuse the same SQL connection to connect to same server but different DB.
Azure Logic App POST request to Microsoft Graph API succeeds manually but fails when invoked externally via webhook
I’m experiencing an issue with an Azure Logic App (Consumption) where a POST request to the Microsoft Graph API for appRoleAssignment works perfectly when I manually resubmit the failed action, but fails when the Logic App is triggered externally via a webhook.
Logic Apps – Log Analytics Data Collector Is Not Accepting Array Variables
I added the Azure Log Analytics Data Collector connector in my Logic Apps workflow and I tried to add an array variable called result
to it but it is not showing in the list. Only boolean and string variables are showing as seen in the screenshot below.