As usual for Microsoft, a half-baked solution claimed as a completed.
As per my comment, "Full CRUD (add, update, delete, read irrelevant) trigger for SQL. I want to provision SharePoint sites / libraries / folders based on rows added, updated, or deleted in a SQL table on-premises via the Data Management Gateway", we wanted a complete implementation.
Yet the so called solution doesn't support on-premises SQL tables.
Why do you always do this, Microsoft? You never complete a product, and just leave it as a three legged chair, just about able to claim the thing is chair-like but still unable to sit on it. And then make annoying announcements like "Completed", "Solved", etc. in your forums claiming victory.
THIS IS NOT COMPLETED. The request as per the above commentary specifically stated on-premises to be supported. You simply haven't delivered.
Please remove the "completed" status and keep this open until the on-premises SQL tables are supported.
I am new to Power Automate, and I am working on creating an item in Microsoft 365 SharePoint list when an item is created in my On-Prem SQL table. I have the gateway and connection working. I can write the conditions that I need, but it is duplicating the primary key in the SharePoint List.
You can now trigger based on new or updated SQL rows, read more about it here: https://flow.microsoft.com/en-us/blog/q3-2017-update/