Hi,
I have a "weird" bug to report:
I have two combo boxes: one has a SQL table, the second has a SQL View (containing also the id column).
When I do a Patch, the first one's value is saved correctly (I use FirstCombo.Selected.id, because it's a single selection)
while the other one with the same SecondCombo.Selected.id is saved as blank or null in SQL.
When I use the dropdown with the SQL view, it is patched correctly.
I tried using the First(SecondCombo.SelectedItems).id, same result.
Is this some sort of limitation on the combobox?
The tables are tiny, like 10-20 rows.
I don't get error messages, the Patch is executed successfully.
Solved! Go to Solution.
Hi @vladimir84
One of the first things I would check is the explicit column selection setting. This may be the reason why PowerApps returns a null ID value. If you turn this off, the stat make a difference?
Hi @vladimir84
One of the first things I would check is the explicit column selection setting. This may be the reason why PowerApps returns a null ID value. If you turn this off, the stat make a difference?
Yup, that did it.
Also, it was not noticeable in the editor. It was apparent only when the end-user was testing it.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.
User | Count |
---|---|
208 | |
70 | |
49 | |
49 | |
20 |
User | Count |
---|---|
256 | |
125 | |
84 | |
77 | |
73 |