I've noticed something annoying with my edit forms. Even though I have a data card's requred property set to true, the form still allows the submition of blank information in that card's upload property, and then blank fields end up in my data source.
This is happenig on several different edit forms, and when using both exel tables and share point lists as data sources.
Solved! Go to Solution.
Thanks Felix @FelixCuadrilla
If I wanted a Text input to be required, but only if another Text input had info in it, I would need to define that condition within powerapps. I have such a scenario and have added the releveant code.
Therefore, if it must be required at the SP list end, I would run into trouble because in reality I would only want it to be required based on a condition found with powerapps. Sharepoint would think it was always required. On the flip side, powerapps needs sharepoint to to be set at required for it accept the requirement.
Bit of a Catch-22
It is only possible then to make a field either required or not then?
What if your field was initially not required in SharePoint and now is required in SharePoint? Even if you refresh the connection this does not appear to update.
Anyone find an update to this?
I have also found that powerapps doesn't pick up required fields after they have been made required. So far, not impressed with PowerApps...I guess you get what you pay for when these tools come for basically free with O365. I feel sorry for someone who is paying for P1 or P3 when money could be spent on better forms technology.
As of yesterday there is still at least one bug related to this still in the system.
I was able to save a form with a blank required CDS field yesterday. I can't recreate it today.
Also, and this is my bigger problem, the required field setting for a field (in CDS) is not respected when doing an import.
I imported some data from an Excel file which mistakenly had blanks in some of the required fields. The import process blithely created records for each line from the Excel file, even those with blanks in the required fields.
These empty required fields created some serious issues in our downstream processes.
Since the required field flag is a property of a CDS field, not of a form, it should be respected (and fail the insert attempt) whether the data is coming through a UI form, an import, or anywhere else, its 'required'.
This is a bug.
Check out new user group experience and if you are a leader please create your group
Did you miss the call?? Check out the Power Apps Community Call here!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.