M-Files Vault List

• Why do you have two value lists with the same names?  Is there a reason they're either not the same list, or they have different names?
• You can add items to external value lists.  You need to configure the "INSERT" query properly; this document on the user guide details what needs to be set up: Connections to External Databases for Value Lists (m-files.com)

I think I expressed the problem incorrectly. I'm not talking about two lists of values ​​with the same name. I'm talking about two values ​​with the same name with different ids in a value list. What can I do to separate them?

I think I expressed the problem incorrectly. I'm not talking about two lists of values ​​with the same name. I'm talking about two values ​​with the same name with different ids in a value list. What can I do to separate them?

My apologies - you did say that, but I misread it.

That's difficult.  Why do those two items with the same name exist?  Do they mean different things?

In general terms you'd want to clean the data before it goes into the lists.  You'd then perhaps want to stop users from adding their own values, so you don't get different ones with the same names (or with slight differences like capitalisation).

To explain the situation better, I have a value list with people's names and surnames. In this case, when there are two people with the same name, I want to do something to distinguish the people. Each person has his or her own unique id. In this case, I couldn't come up with an idea about what I could do with these two. Thanks in advance for your help

Thanks in advance for your help.

You should convert the value list to a object type. That allows you to add more properties to each item. In this case it might be a comment field, or it might be relevant to add address and/or telephone number, email address etc.
If you wish to stick with a value list, you will have to insert something in the names directly to be able to differentiate them.

Actually, I have an object called personnel that is connected to an external database. In my list definitions with list properties, I use a list of values ​​based on the content of this object. The content of this object includes name, surname and singular id. How should I follow to distinguish between two people with the same name and surname?

If two people have exactly the same name then, as Karl mentioned, you'll need to add something to the display value which allows you to differentiate.

Maybe their job title?  You could concatenate their first name, last name, and job title, into a calculated value.  If this value is set as the name for the object then that will be displayed in lists and you'll be able to see who is who.

There are too many values ​​in the object's content. How can I implement this situation you mentioned? Could you explain it a little more clearly?

Does this help: Property Definition Automatic Values (m-files.com) ?

Is automatic value calculation a logical solution in an object-based value list with approximately 1800 values?I wonder if I can create a new value list that combines the two property values ​​of the class and holds this new value?

You can use it with larger lists, as a general case.  There will be an initial calculation (not immediate for 1,800 items, but it shouldn't take too long), and then the calculated value will only be re-calculated when the object is modified.  Note that it will make a change to the object when it does so.

I'm not sure that duplicating data to another list makes much sense.

I know I've asked you in the past whether you work for an end-user or a reseller and you've not told me, which is fine.  If you work for an end-user then I would suggest you reach out to your partner for some assistance; they'll be able to take a closer look at what you have and what you want to achieve, and guide you on some of these built-in features.  If you work for a partner then open an Implementation Support Request and get guidance from our dedicated partner-support teams.

I remember saying it, but let me say it again. I am an end user.