Started a form as a new one but the fields aren't visible and able to fill

[marilia_mattia]

Hey guys, need some help in here!

I'm connecting in a SQL Server db to a specific table and want to create a form (as a new form to submmit answears later). As default, I know that the type of form is insert > edit fom and that I can change this property for new so it shows when F5 is pressed. However, my form only shows the column names, without the fields and when I alter its properties such as color of the datacardvalue, it's still not possible to enter any kind of data. I've also connected a second table to see if this happens as well and with this 2nd table its all ok. I've noticed that the cards properties (datacardvalue) are differente types, the one with error is showing as a text label and the one that is functioning accordingly is a text entry type, but I don't know why they're different because the user has all permitions for both tables in SQL Server. Does anyone know how to help me out?

[DBO_DV · Accepted solution]

Hey @marilia_mattia ,

Have you tried manually changing the controls to a text input instead of a text label?

What is the displaymode set to?

[marilia_mattia]

I tried to change the control type in the cards but the text input option wasn't available, I was trying to see if there's a possibility to do that in a different way than manually, but I'll have to try this instead

[DBO_DV]

Since the form gets created automatically it will always create the same result. sadly there is no other way than manually. 

[marilia_mattia]

I just tried your approach but in this case it doesn't have the update property to define in the card. Do you know any other thing that might be wrong, maybe in SQL Server that's not allowing the form to appear in the correct form? I have permission to alter, insert, select and update for that table.

[DBO_DV]

I'm no expert for SQL but wouldn't you need Create rights?

Have you tried creating a Record from outside of  Power apps? could you try and Set the Form to edit and use the First(Database) just to see if it works. If it works I assume that you don't have the appropriate privileges. But as I said I'm  really no expert for SQL.

[marilia_mattia · Accepted solution]

I'm extremely thankfull for your time and efford to help me out but I've managed to figure out what was wrong! I ended up forgeting to configure a primary key to the table. Came here to record the solution so other people that might be facing this same issue can find the solution! 

[DBO_DV]

That's great news. 

Thanks for sharing the solution with everyone.