Unable to submit form due to 'Title' field required, but it is set as an optional field

[Tj7933]

I have looked through many responses to this issue in this forum.  Most are pre-2022, and when I try each solution, they do not work.  

The title field for the associated lists is renamed and populated immediately by a customized Power Automate approval flow.  Last week this solution worked for both lists. I had no issues with the title field being required on the form or the patch function breaking due to the title field.  I have the associated emails to prove the flow worked and the item submitted.

For some reason, this week, all my custom forms are broken.  They no longer save the data; the error indicated is that the patch is not working due to a required field.  None of the associated lists have any required fields.  All the fields are set to optional.

In an attempt to fix this problem, these are the solutions that I found in this forum and attempted but did not work.

I have disconnected the data source and reconnected it.  <- Epic Fail, the field still shows as required.
I have changed the properties of the data card such that it says the requirement is false.  <-- Epic Fail, patch function still requires the title field.
I have removed the title field card from the form.  <-- Epic Fail, patch function still requires a value for that field regardless of whether it is in the form.
I have created a new app (instead of a customized SharePoint form) <-- still indicates the field is required for the patch function to work.

This is a national project on tight timelines that did not consider that Microsoft might break things. I need an urgent solution. 

Thanks for your help
TJ

[Cr1t]

@Tj7933 

Please try this.

Go to your list settings 

Select the title field.

Select no require that this column contains information to No.

Save the list.

Go back to powerapps, refresh the datasource. 

Let me know if this works.

Please click Accept as solution if my post helped you solve your issue.

[mmollet]

Why not just pass it an empty string or blank until you figure it out? You mentioned what I would tell you to try already and I am assuming that the setting in the SP list for Title has been changed to make it not required as well. This is yet another reason I do not use forms. Its just as easy to build the form from scratch IMO and then I have 100% control over everything and I know what is going on. Maybe try using a custom built form to see if a general patch statment will take?

[Tj7933]

If you read all four things that I tried, you will see that your recommendation did not work.

That was the first thing that I did.

TJ

[Tj7933]

When I add the field and leave it blank, then the patch warning comes up and will not save.

If I must I will add the Request ID field, hide it and indicate a default value (999) on the new form, but it seems ridiculous to create a work around for a problem that did not exist last week.  At least if I do this, the workflow will update the field to the correct value.

[mmollet]

Another thing I always do is as you said; first thing when I make a new list is I do the following:

Go to list settings

Change Title to Optional Column

Go to default view

Turn title off and turn ID on and then make ID item 1

I do this because the Title column is just 100% problems. I have never had a benefit from using that column but have had many many issues while doing so. This is one of them. Also renaming it doesnt actually rename it but rather is just a label for it. I always just remove it from my lists and make new columns for all of my data.

[mmollet]

Yeah its def a bandaid I agree 100% on that. Im not really sure what is going on in your case other than as I mentioned above maybe some weird title column confusion on the part of SP and/or Power Apps. I will keep looking around for solutions in the meantime. 

[Tj7933]

@mmollet 

There is a benefit to the title field.  It is directly linked to all the forms.  Edit and View.  It is a hyperlink field.

The problem with this field is if you don't need or want the hyperlink to be an entry by the user (I use Power Automate to populate all of mine), you are foobarred.  The field is mandatory.  I like that with SharePoint online we can immediately set to optional instead of needing to use software like what was required with SharePoint Prem, but it seems that Power Apps disregards that setting.

TJ

[mmollet]

I have actually never really used the title column for anything after the first few times using it as it caused me too much headache. I will have to look into more bc you have me intrigued on what the purpose of it is and why it needs to be so fancy. I use no complex columns or lookup fields ever for any reason in SP as its always just a pain in the ass 😛 Sorry I couldnt be of more help than finding a bandaid lol

[Tj7933]

@mmollet 

Last week I had an issue with the settings wheel not showing for all my sites.  I have since been told by IT that it was a glitch on Microsoft's side.  The problem is when it returned. All our forms started glitching.  A few we were able to fix by changes to formulas or design, but I have 2 lists associated with flows whose forms will not fix. I want to scream.

Thanks for helping me search, it is appreciated.
TJ