Andy Butland

Closing this one now as related issues are closed and CMS updates released.

The CMS update to resolve the issue was in 12.3.8 (which I'm getting from the [PR](https://github.com/umbraco/Umbraco-CMS/pull/15593) linked above).

Hmm... then unfortunately at this point I'm afraid you will need to keep form relation tracking off, or upgrade to 13. As 12 was a short-term-support version, it's now end...

We'll be providing this option from the next release, allowing passing of additional data as a dictionary when rendering forms. It will be associated with the record and made available...

Yes, the current approach I'd recommend to use would be what you have in your second example (but without the square brackets, that doesn't look to be needed and clashes...

It's difficult to remove things like this as you'll appreciate it could be other customers are relying on them as CSS hooks, and we'd break their implementations. If you aren't...

Might get a bit messy in the template, but maybe. We did similar when we introduced [semantic rendering for fieldsets](https://github.com/umbraco/Umbraco.Forms.Issues/issues/1038) before making the new behaviour the default in a major...

Could you share some further details about your permissions set up please? - What values do you have in configuration for the settings `ManageSecurityWithUserGroups` and `GrantAccessToNewFormsForUserGroups` (or if you don't...

Thanks for the extra detail. Unfortunately though having been testing this morning, I've not been able to replicate the issue.

Will close this one now since being unable to replicate and no further discussion .