Notifications
Clear all

[Solved] Property Operations: Error "Plain text is not allowed in the value" when mapping Person to M-Files User list

0
Topic starter

We have a process with the property "Bearbeiter" (list of object type Person) and the property "Bearbeiter (Userliste)" (list of M-Files users).

image

In a Property Operation Rule, I want to write the value from the  property "Bearbeiter" in the property "Bearbeiter (Userliste)" (OnSourceObject).

To do this, I follow the property "Bearbeiter" and select the "M-Files user" -> Bearbeiter.M-Files-User as a dynamic value.

image

In my opinion, this should work without any problems, since the M-Files user is linked to the person.

image

However, I now get the following error message for the value: Plain text is not allowed in the value. Use placeholders only.

Is this a bug?

 

Thanks in advance.

Best regards,
Jeremias Zirngast
IMCT AG

2 Answers
0

Hi Jeremias,

if I understood correctly, you want to write all the M-Files Users inside the "Bearbeiter (Userliste)" property by adding it like "Bearbeiter.M-Files-User"

 

I have recreated it in Extension Kit Core version 25.5.1 like this:

Structure:

    • CL. Employee
      • PD.Name or title
      • PD.Login account - list of M-Files login accounts, each Employee has 1 login account
    • CL.Test
      • PD.Name or title
      • PD.Employees - list of object class CL.Employee
      • PD.EmployeesLoginAccount - list of M-Files login accounts

Rule is configured like this:

image

 

And I have successful results:

image

 

I hope I understood everything correctly and please let me know if I can help you with anything further. 

Jeremias Zirngast Jeremias Zirngast Topic starter 21/07/2025 1:14 pm

Hi @viktorzagajski 
Thanks for your quick response.
My rule seems to be the same.
The "M-Files Benutzer" property is a list of users (screenshot).
I can set another property that is a list of users without any errors.

image

image
0
Topic starter

Hi @viktorzagajski 
The alias for the property "M-Files Benutzer" was set with spaces and hyphens, which led to this error.
Looks like this was the problem.

Best regards,
Jeremias Zirngast
IMCT AG

Viktor Zagajski Viktor Zagajski 22/07/2025 5:15 am

Hi @jerry,

I am glad you resolved the issue, thank you for sharing the resolution!