The article discusses the limitation of the Logic App Standard SQL Connector in monitoring row version of SQL Views and how this functionality can be imitated until it gets rolled out. It explains that the built-in trigger for SQL tables cannot be used for monitoring SQL views.
The article suggests a workaround by using parent and child workflows to pass triggered values and use them as a where condition in the child workflow, which executes a Get rows action on the SQL View using the where condition. The article also mentions that the approach can be customized based on specific requirements and how the SQL View gets updated.
Trigger SQL Views with Logic App Standard with the built-in SQL Connector is a feature of Azure Logic Apps that allows users to trigger a SQL view with a Logic App. This feature allows users to easily create an automated workflow by connecting their SQL view with a Logic App, allowing the Logic App to be triggered when specific conditions are met. This is useful for automating tasks that are triggered by changes in data stored in a SQL view, such as sending notifications when certain conditions are met or when data changes. Additionally, users can use the SQL connector’s built-in support for stored procedures and functions to call stored procedures and functions from their SQL view.
Mar 13, 2023 — This article shows how to access your SQL database from a workflow in Azure Logic Apps with the SQL Server connector. You can then create ...
Doesn’t include: built- | Must include: built-
YouTube · OurCloudSchool · Nov 13, 2022
Apr 25, 2021 — I am using a HTTP trigger to start the workflow. Add an action and search for SQL. We can see two connector options. Built-in and Azure.
When we see the code view behind this logic app it will be similar to the one ... An Append query is often referred to as an Insert Query because the SQL ...