I'm connecting my App with SQL through gateway
when I add fields to the App I notice all these fields in view mode !
it should me in edit mode and showing the textboxes that I have to use
is it normal ?
what is the best practice in my case ?
Solved! Go to Solution.
Please note: you cannot edit items in a form while using a SQL View. It’s not possible in PowerApps because you are looking at a View not the table itself.
SQL Views are read-only!
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
@mdevaney is correct. This is not a PowerApps constraint, just how SQL works. If you load data from a view and want to save it back, you can a) use Patch() to update the underlying table(s) or b) pass the updated data to a SQL stored procedure. I do a lot of this type of work in my PowerApps and typically don't use forms myself.
Did you add an Edit Form or a Display Form? You should be adding and Edit Form.
After you added the Edit Form you need to unlock each Card one-by-one. Its 100% normal.
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Insert two buttons on the form and OnSelect:
Button 1
Newform (YourFlowName)
Button 2
EditForm (YourFlowName)
After clicking on the button the form will change
------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.
Did you try my idea?
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Please note: you cannot edit items in a form while using a SQL View. It’s not possible in PowerApps because you are looking at a View not the table itself.
SQL Views are read-only!
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
@mdevaney is correct. This is not a PowerApps constraint, just how SQL works. If you load data from a view and want to save it back, you can a) use Patch() to update the underlying table(s) or b) pass the updated data to a SQL stored procedure. I do a lot of this type of work in my PowerApps and typically don't use forms myself.
@ElMeSaFeR
Honestly, don't even bother with the form control in this instance. Just place the controls on the Canvas directly and write a PATCH function
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
199 | |
52 | |
41 | |
39 | |
35 |
User | Count |
---|---|
261 | |
86 | |
71 | |
70 | |
66 |