Any tips to fix this matter? I hope it’s an error by me, but seems like a bug 
I have seen this error before, 1-2 months ago. It reappeared in my Apps today.
To fix it the last times I had to duplicate the entire dialog and delete the old.
Hi Lynfot, and thanks for reaching out!
It seems to be a bit challenging to recreate this issue, so I hope you can provide me with some more details about this.
Has this setting previously been checked, but unchecked recently?
Does it exist any duplicate dialog with the app bar turned on?
Does it appear in this dialog across all environments?
If you toggle the checkbox and deploy to test, does it still appear?
Hi.
Olav and several other have access to our Solution so it’s possible to check the App UI directly there
Has this setting previously been checked, but unchecked recently? No
Does it exist any duplicate dialog with the app bar turned on? No and we don’t use the App bar for any dialog in this App
Does it appear in this dialog across all environments? I checked now and the error seems to be consitent in all enivornments. I see it in dev og production
If you toggle the checkbox and deploy to test, does it still appear? It seems like I don’t even need to toggle the box. By deploying to Test I solved the issue. That’s nice however the error is still there in PROD since I have not deployed to PROD yet and the error came out of nowhere and snuck into PROD. It would be very unfortunate to have to check all dialog boxes manually each time we deploy to check if this error has snuck in this time or not.
There is one thing that may cause this;
We used to have App bar turned on and there was data in the Title field.
We then turned them off. It seems like the Title field is not properly cleared.
The reason I suspect this is that the title seen in the print screen above should have been purged and removed months ago. I.e the system should not store it when the App Bar is turned off.
Only way it could refind the old title is that it somehow still stored that data.
Similar these values used to be required. For all actions where we delete items.
I have made them not required, but now they are back to required again.
Again, I can’t rule out that I have forgotten to change these to not required, but I made the change weeks ago and since then we have had testers adding and deleting items without any issues.
Seems strange that we have forgotten to change this on about 10 actions.
I can only guess that some older version / states of these actions have taken precedence over the last saved state / version.
Hi, you’re right, this does seem a bit strange.
I will report this issue to our developer team so they can have a look at it, and we will get back to you with updates. Thank you so much for the detailed information, this is very helpful to our investigation!
Have a nice evening!
Tonje