Custom Fields [1971]

[Hangman]

In the bug fix list, it mentions

Changes/Bugs affecting all platforms

• A custom field can be given the same name as a built-in field or an existing custom field

It appears you can still name a custom field with the same name as a built-in field, though not the same name as a custom field but if you do inadvertently use the same name as an existing custom field there is no warning, e.g., 'This Field Already Exists', the custom field is simply not created which I think has the potential to confuse...

[MikeTO]

Same for me

[Hangman]

Hi @MikeTO,

Thanks for confirming...

[Jon P]

The fix for this intentionally ended up allowing users to create fields with the same names as built in fields, but should be preventing duplicate custom field names from being created.

I'll log an improvement in regards to no error/toast being shown when it fails to create a duplicate field

[Hangman]

Hi @Jon P,

Thanks for the clarification...the wording for the change/bug is perhaps slightly ambiguous in as much as it reads like a bug fix rather than an either-or but no big deal.

Thanks for logging the improvement, I think it would certainly be helpful for an error/toast to be shown otherwise it 'feels' as though there's something wrong with the app, as in, unless you're aware that duplicate custom names can't be created, the assumption it's there is an issue with creating custom fields. Logically you wouldn't want to create duplicate custom field names but I'm sure it will trip a few users up at some point...