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

[Tj7933]

@mmollet 

Please remember that I have renamed the Title field to Request ID.  This is what you will see in the customize view selections.

 This one is edit

This one is connected to the View Form.

There is another blank one that will show the value without either hyperlink.

TJ

[mmollet]

Right! The issue with renaming SP columns is that it doesnt actually rename the column and I have had this cause issues in the past far too many times lol So now I use simple columns and if I need to rename one I delete it and make a new one with a new name as to avoid all the possible issues. 

[Tj7933]

@mmollet 

The issue you are describing is because SharePoint uses GUIDs to identify everything.  So the name of the field NEVER changes, just the "Description".  You can change the name 100x and the name of the field in the address bar will always be the same.  All that changes is a new GUID is provided for the field.  So if you look at the image below, when you go into settings for the field you will see 2 things at the end of the HTML.  The GUID that changes with each change to the field and the ORIGINAL field title.  So long as you know this you can rename fields and your programming will still work.  The problem with PowerApps is you are working with both the new name AND the field name and its properties and that can mess things up.