Hi Patryk!

Well, yes, according to this article:

https://community.rws.com/product-groups/trados-portfolio/business-manager/w/wiki/5919/custom-fields

there are only 5 data types supported.

Can you please tell how you're going to use multi-selection fields? Just in detail views, or in reports? I think we can implement this, but on database level it will be a string with some delimiter (for example, semicolon).

And values for selection will be predefined? Or you want to select something from other tables?

Hi Patryk!

Well, yes, according to this article:

https://community.rws.com/product-groups/trados-portfolio/business-manager/w/wiki/5919/custom-fields

there are only 5 data types supported.

Can you please tell how you're going to use multi-selection fields? Just in detail views, or in reports? I think we can implement this, but on database level it will be a string with some delimiter (for example, semicolon).

And values for selection will be predefined? Or you want to select something from other tables?

I'm sorry for such a long delay in replying, with these fields I mean, for example, a situation in which a translator is able to provide translation services in more than one subject. For example, purely theoretically he/she can be a translator for "IT" and "Finance".

A multiple choice field with predefined subject areas would allow to enter these different subject areas for a given translator.

Data from such a field should be filterable and displayed on the Vendor list, and when you enter a Vendor, this data should be displayed in his/her card.

Hi Patryk,

Well, with this particular example, we have possibility to provide multiple languages or specializations in the vendor profile (using special tables). However, imagine how vendor list could look if you add tens of values into these tables, and these values should be displayed in a single table cell. We'll just pollute screen space with a lot of labels which will be difficult to read.

For this reason, we try not to display data from nested tables, but instead - in this particular case - make it possible to filter by languages or specializations:

I would agree that it could be nice to see supported specializations/languages right in the vendor list, but this is not about custom fields. I think this is about improving application and making it possible to view this data in some useful way.

What do you think?