Hi @rth
I know this is old, but in case it is useful to someone else looking for a solution, there is another option, but does also involve some set-up in SQL. That is putting an SQL 'update' trigger on your tables column.
This trigger then fires anytimethat column, and only that column, changes.
Second you then add an action to the trigger which will insert the values of the changed reocrd, so you can identify it, to another new table.
This second table has a primay key. You then run your flow of this second table.
So in your example , below would be the trigger, just make sure you create the new table first
create TRIGGER [dbo].[IsActive_change] ON [dbo].[Original_SQLTable]
AFTER UPDATE
AS
if (update (IsActive))
BEGIN
SET nocount ON;
IF EXISTS (Select * FROM Original_SQLTable)
BEGIN
INSERT INTO NewTable (PersonId, Name, IsActive , DateAdded)
SELECT i.PersonId, i.Name, i.IsActive, GETDATE() from inserted i --inner join inserted i
END
END
GO
ALTER TABLE [dbo].[Original_SQLTable] ENABLE TRIGGER [IsActive_change]
GO
I've used this a few times, I hate having to have set-ups in SQL and flow to support an automation, but in this case, it adds extra maintenance, but can't see there is another option, other than using a difernet type of DB like SharePoint DB with version control.
Hope this helsp somebody
Hi I know this is old, but in case it is useful to someone else looking for a solution, there is another option, but does also involve some set-up in SQL. That is putting an SQL 'update' trigger on your tables column.This trigger then fires anytimethat column, and only that column, changes. Second you then add an action to the trigger which will insert the values of the changed reocrd, so you can identify it, to another new table.This second table has a primay key. You then run your flow of this second table. So in your example , below would be the trigger, just make sure you create the new table firstcreate TRIGGER [dbo].[IsActive_change] ON [dbo].[Original_SQLTable]
AFTER UPDATE
AS
if (update (IsActive))
BEGIN
SET nocount ON;
IF EXISTS (Select * FROM Original_SQLTable)
BEGIN
INSERT INTO NewTable (PersonId, Name, IsActive , DateAdded)
SELECT i.PersonId, i.Name, i.IsActive, GETDATE() from inserted i --inner join inserted i
END
END
GO
ALTER TABLE [dbo].[Original_SQLTable] ENABLE TRIGGER [IsActive_change]
GOI've used this a few times, I hate having to have set-ups in SQL and flow to support an automation, but in this case, it adds extra maintenance, but can't see there is another option, other than using a difernet type of DB like SharePoint DB with version control. Hope this helsp somebody
