Showing results for 
Search instead for 
Did you mean: 
PowerApps Staff FelixCuadrilla
PowerApps Staff

Re: Bug Report: Powerapps not enforcing required fields.

They just need to be required on Sharepoint.

Level: Powered On

Re: Bug Report: Powerapps not enforcing required fields.

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?


Level: Power Up

Re: Bug Report: Powerapps not enforcing required fields.

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.

Level: Power Up

Re: Bug Report: Powerapps not enforcing required fields.

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.

Level: Powered On

Re: Bug Report: Powerapps not enforcing required fields.

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.

Helpful resources


PowerApps Monthly Community Call!

Join us next Wednesday for our Demo Extravaganza, October 16, 2019 8am PDT.


Microsoft Business Applications Virtual Launch Event

Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.


Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020


Power Platform World Tour

Coming to a city near you


PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!


Join PowerApps User Group!!

Connect, share, and learn with your peers year-round


Power Platform Summit North America

Register by September 5 to save $200

Top Kudoed Authors
Users Online
Currently online: 194 members 4,254 guests
Recent signins:
Please welcome our newest community members: