'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Power Automate SQL Server Trigger Dynamic Content Error
Question details
The user needs to resolve an issue where a Power Automate trigger does not populate table names or dynamic content, leading to a key-matching failure.
- Product
- Power Automate / SQL Server
- Device & OS
- not provided
- Scenario
- Configuring a SQL Server trigger in Power Automate to fetch dynamic content using a gateway connection.
- Observed behavior
- A SQL Server gateway connection produces a trusted-source URI error. Entering a custom table name manually causes a 'key didn't match any rows in the table' error, and dynamic content fails to load.
Ensure you have administrative access to your Power Platform environment and verify that your on-premises SQL Server data gateway is online and updated to the latest version.
Recreate the SQL Server Connection and Trigger
Resolving connection corruption and selecting the table directly from the UI dropdown typically fixes the key-matching failure.
The 'key didn't match any rows in the table' error often occurs when a custom table name is entered manually, or when the underlying SQL Server gateway connection has become desynchronized from the environment.
Navigate to the Data > Connections menu in the Power Automate portal, locate your SQL Server connection showing the trusted-source URI error, and delete it.
Click 'New connection', select SQL Server, and re-enter your valid credentials and gateway details to establish a fresh connection.
Open your problematic flow in Edit mode, delete the broken SQL Server trigger, and add a new 'When an item is created' (or similar) SQL Server trigger.
Instead of typing a custom table name, click the dropdown arrow in the Table field and select the target table. This ensures the schema loads correctly and populates the dynamic content.
Enhance Your Daily Workflow with WPS Office
While WPS Office does not manage Microsoft Power Automate flows or SQL server triggers, it is an exceptional, lightweight alternative to Microsoft Office for your daily documentation and data management needs. Experience a seamless and familiar interface without the heavy subscription fees.
- 1. Download the software: Visit the official WPS Office website and download the free installation package for your device.
- 2. Install and launch: Follow the simple on-screen instructions to install the application, then open the WPS Office desktop client.
- 3. Open existing files: Drag and drop your existing .docx, .xlsx, or .pptx files directly into the workspace to start editing immediately.
Frequently Asked Questions
Why does Power Automate show 'The key didn't match any rows in the table'?
This error is typically triggered when you manually enter a custom table name that the system cannot validate against the database schema, or if the connection metadata in your environment is outdated.
How do I fix the trusted-source URI error in a SQL Server connection?
Recreating the connection entirely within the Power Automate portal and ensuring your on-premises data gateway software is running the newest version usually resolves trusted-source URI errors.
Why is dynamic content missing from my SQL trigger?
Dynamic content relies on Power Automate successfully reading the table schema. If the table name is unverified or the gateway connection fails, the system cannot fetch the columns to display as dynamic content.
