Getting "An entry is required or has an invalid value. Please correct and try again." error when submitting a customized form.

[lumberjacklurch]

I've seen various posts about this error, but they are all from 2018 or older.  I've tried making my Title column in my list to not being required (apparently it fixed the error for some folks), but it didn't fix my error.  Not sure why it's saying its missing something when all fields are populated.  Has anyone else gotten this recently?

[Anonymous]

Dear All, I had to confirm the solution here. Basically I had the same irritating error, reloaded my [dbo] and checked the data and all that. I was almost giving up. then, I did this: 

1. Update ALL DataCards in the EditForm to ensure property of Required = false
2. Refreshed Database, Saved the app, Closed it and Reopen
3. It is working without error. 
4. The fun part, I re-instated the DataCards properties one by one back to Required = true
5. It is working. 

As a history when my SQL Datasource Table was reloaded there was no changes in column names and its content and format of data. It was OTHER columns that was changed - exclusive of the columns that I had set to Required = true before the error popped up. 

Doing the above saved me at least 3 hours at least before I gave up and decided to go the rabbit hole of deleting my entire form with the already built-in reference to multiple VIEW tables and the formulae I had for my Combo Boxes. Let me know if this helps with fellow community members - happy to help if needed example. 

[J_W_]

@RandyHayes  I'm not the OP but your answer solved my problem. I had repurposed a DataCard to hold other controls, without realizing the card itself was tied to a field and required was set to true. Deleted what was in the "DataField" property of the card, and changed required to false, and solved my problem. Thanks!

[Elin1]

If you have created new forms, make sure you save the correct form, You will see in SharePointIntegration which form is loaded when you create a new item.

[CharlesMoi]

Try going into your datasource and check for any default restrictions e.g. a text field may have a character limit of say 100 letters. Make the change, save and refresh on the app side.

Increasing these may resolve the issue like it did for me.

Cheers

[Sandracere]

LLevo con el error 3 días y la solución es:

Mirar el límite de caracteres de los campos del origen de datos, el problema es el límite de caracteres que hay que ampliarlo y volver actualizar el origen de datos.

Espero que os sirva porque me he comido la cabeza 3 días y estaba desesperada.

[TearsOfJoy]

@lumberjacklurch I am adding this in case anyone like me is out there reading old threads in desperation. I had the same weird error, and I tried everything - refreshing, deleting and replacing the data source, deleting and replacing the form, etc etc etc. Then I tried one last thing and it worked - I simply renamed my form. Bingo! Worked like a charm! Saved me from rebuilding the whole thing!

[nikk_diamond]

Check if all types of the fields in the PowerApps form correspond to the types of the fields in the SharePoint. Wherever there is a text filed in SharePoint, you should send text. Wherever there is a date, you should send a date, etc. Another key option is, if the corresponding field is required. The requirements of the fields should match also. If your field in PowerApps form is marked as required, nevertheless that your corresponding field in the SharePoint is not, you'll continue to receive this error.

Microsoft should do much better job in description of the received errors.