+> **PowerApps does not work with dynamic schema**. Dynamic schema is the possibility that the same action may return a different table with different columns. Examples of the conditions that may cause the columns in the tables to be different include the action input parameters, the user or role executing the action, or the group the user is working in. For example, SQL Server stored procedures may return different columns if run with different inputs. The connector documentation shows **The outputs of this operation are dynamic.** as the return value for actions with dynamic schema. Flow does work with dynamic schema. Using Flow may provide a work-around for your scenario.
0 commit comments