Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
I've created a simple report + dataset on Power BI service. The dataset reads from a local SQL Server database.
I've registered a local gateway in order to read the SQL Server database.
Working in the Power BI service environment, I've created a Power App by putting in a form two input text boxes
(for the customer code and description fields), a button, a data connection to the SQL Server database using
the above local gateway: when I try the Power App specifying a value for the code and the description and
pushing the button nothing data is inserted in the customer SQL Server table.
Any suggests to me in order to solve this issue, please?
Many thanks
Solved! Go to Solution.
Hi,
to solve the issue, inside the PowerApps environment, I've specified for the OnSelect action a similar function:
Collect('<data_source>'; {<mySQLField1>:TextInput1.Text; <mySQLField2>:TextInput2.Text}).
Thanks
Well, sounds like you did the right sorts of things. However, that's more of a PowerApp issue so I would use their forums.
https://community.powerapps.com/t5/PowerApps-Community/ct-p/PowerApps1
Hi Greg,
thanks for your reply but I thought that my question was a basic one for the Power BI community.
Likely it is enough that anyone remembers how has used PowerApps for inputting data into a SQL table linked to a Power BI dataset.
Thanks
Hi,
to solve the issue, inside the PowerApps environment, I've specified for the OnSelect action a similar function:
Collect('<data_source>'; {<mySQLField1>:TextInput1.Text; <mySQLField2>:TextInput2.Text}).
Thanks
I guess my perspective on this is that the Power BI aspect of this issue is completely superfluous. Your problem, as stated is that PowerApps is not pushing a new item back into the SQL Database. I don't see how Power BI is related to this issue, that's a problem with your PowerApp.