Rename Table Display Name - causes issues

[LenC]

In a Solution, I had renamed a table's Display Name. I am facing multiple issues creating new solution elements, such as custom command bar commands, and 'classic' dataverse Processes such as Workflows and Actions. Are there known issues when table display names are changed? 

In the command bar case, when I first went to create the modern command bar commands (PowerFX), there were errors. Opening the underlying custom command 'app' revealed that the app instantiated the data source using the original table display name. I managed to wrangle it by deleting and re-adding the data source...the designer also frequently references the old table display name, so I manually patch it up. 

With regards to custom Processes, I am trying to build a workfow with an Update Record step, which updates a table record when a child record changes. When I click Properties of Update Record , an error pops up, without useful information, shown below.

Invalid Argument Invalid Argument.
	Timestamp: 3/18/2022 3:19:28 PM UTC Service Request Id: f31b3189-3ddf-40f5-a687-81a2f65c6169 Hide Technical Details Tenant Id: xxxxxxxxxxxxxxxxxxxx Url: https://xxxxxxxxxxxxxxx.crm.dynamics.com Organization Id: xxxxxxxxxxxxxxxxxxxxxx Type: CustomerTest Unique name: unqd369e80d88f1460c88c469e5168f3 Created on: 11/5/2021 3:45:24 PM State: Enabled Security Group: Not set

This only happens with the one table where the Display Name was changed. I compared the URL's the editor invokes. For the table in question, this query string parameter is the only difference: 

&user_lcid=1033

I never intentially ventured into localization.

I am tempted to rename the table back to it's original, but concerned this will cause a larger quagmire for existing solution components, such as the custom commands.

Any other fix? Is there something under the covers that needs to be fixed up to avoid these issues? How would one go about diagnosing this?

[LenC · Accepted solution]

Resolution here: Microsoft Support diagnosed the issue. Some controls on the main forms were 'corrupted'. Deleting most fields and re-adding resolved the issue.

Support said this was a common issue...when you get an error loading the Properties window of the Update Record action, if the main form has some hidden issue, you get the error page. Support could not diagnose exactly what control(s) had issues, they just deleted controls until it started working. 

Hope this helps someone here.