[DONE] Cyrillic field names are replaced by field ID (e.g., `_7`) when searching fields via `@` in the new editor

[Venom]

In the new editor, when searching for fields using the @ mention feature, if a field name is written in Cyrillic, it is displayed as _7 (i.e., the field number instead of the actual name).

As a temporary solution, we have to write the field name in both Russian and English, which results in excessively long field names.

There was a similar problem in the old editor.

[DONE] When a new field is created and the field name isn't in english, the field external id is _

Hi, when I create a new field and the field name is in a foreign language (I tried with both Hebrew and Arabic, but probably same in other languages), the field external id is _ which then is incremented with 2 underscores, 3 underscores, etc. one workaround can be to use a transliterate service that will give the field a similar name in English, or give an option to also name the external-id of the field when its created (instead of creating it and then coming back and renaming it)

[Leo]

Hi @Venom,

Thank you as well for this report and for bringing it to our attention

At the moment, we do not officially support Cyrillic field names, so this is not yet covered by our standard QA, implementation, and regression testing processes.

However, since we already implemented similar handling for the previous calculation field and the required adjustment is relatively small, we’re happy to add the same support to the new calculation field as well. This will ensure that Cyrillic field names are represented properly when using variables via @ mentioning, instead of falling back to technical IDs such as _7 .

We’ll let you know as soon as the fix is live.

Thanks again for the helpful report!

Best regards and have a great day,
Leo

[Leo]

Hi @Venom,

Good news! I just wanted to let you know that we’ve fixed this issue and the fix is already live.

Cyrillic field names are now handled correctly in the new calculation field when using variables via @ mentioning, so the proper field name is displayed instead of the technical ID.

Thanks again for bringing this to our attention and helping us improve this!

Best regards,
Leo