You are viewing limited content. For full access, please sign in.

Question

Question

Help with search syntax for multi value field.

asked on July 23, 2020

Hello, caveat--non-IT literate person here needs help. 

I am having workflow issues that I think are related to a field on our template being a multi-value field. To test this theory, I tried to edit the value in admin console to be a single value field but it won't let me. I tried to use this syntax to search for the documents using the multi value field: {[]:[First Name](2)=“*”} 

I came up with an error message of:  

Does anyone see anything obvious that I should fix?

0 0

Replies

replied on July 23, 2020

Your screenshot shows that you forgot the "[]:" before the field name in your search syntax. ( {[First Name](2)=“*”}   instead of {[]:[First Name](2)=“*”} . It's also using Word smart quotes instead of regular quotes. 

Your search also looks for a value in a specific position in the field (the second value), is that intended?

1 0
replied on July 23, 2020

Thank you, I will try that out. I was trying to search for the second value in the name field, even if it was blank. This syntax was sent to me from our VAR so I just did a copy paste. 

0 0
replied on July 23, 2020 Show version history

The system won't allow you to change the Multi-Token field to a Single line Token as it would delete metadata field data from the database related to documents in the repository.

The search syntax against a Single-value field and a Multi-value token looks the same, but the Multi-line can return more than one result in the token that you may have to step through. 

What is the challenge in the workflow?

0 0
replied on July 23, 2020

The field is for first names. It then looks up the middle initial and last name from a SQL database. This works great most the time, but if you hit enter after selecting the first name from the dropdown, it causes a second empty field to be added to the template. This seems to be affecting the population of the rest of the data and causing some middle initials to incorrectly populate, etc. The SQL table looks fine, it all seems related to the fact that the field has a second (empty) name value when you hit enter. It's hard to explain what I'm seeing, but I am wondering if the only way to correct is to manually remove the second empty name field from all documents then try to delete. 

0 0
replied on July 24, 2020

That sounds like expected behavior for multi-value fields. When you pick a value for the first name, a second text is added to that field to make it easier for the user to add multiple values. The empty value is not saved in the repository.

0 0
replied on August 3, 2020

Okay, thank you/ If anyone knows how to change this field to a single value now, I would appreciate any guidance. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.