This is a functionality that looks like it’s been degraded in cloud and that is the ability to select multiple items from the list of values.
For example, on NCR’s we have a “Source ID” list. In IEE we could select multiple items in the list by hitting CTRL and clicking the item we wanted to select and IFS would then separate those values with a semi-colon. Now in lists in cloud, when you select an item, it closes the LOV and you are then forced to manually enter the remaining items from memory.
Is there anywhere in page designer that I can change this functionality?
IEE, selecting multiple by holding CTRL and clicking, then IFS separates each value with a ; and does a search for source ID = INTERNALERROR OR source ID = MRB NCR OR etc.In cloud, hitting the down carrot to see the LOV, it only allows me to select one of the values from the list but I need to be able to select multiple efficiently.
Page 1 / 1
Hi @Anna ,
Checked in 24R2 as well, and the behavior remains the same.
As far as I know, LOV Multi-Select is not yet available in the Aurena client, and the Framework Team is considering it as a potential future enhancement.
Hi,
Just to clarify. IFS Cloud do have support for Multi-LOV. Entity attributes is set to support multiselect. In this case, the client field will indicate multi selection with a different icon.
If the field is a multiselect the search field will also act as multiselect. The lookup picker is exchanged for a search button that takes you to the LOV detail dialog, where you select the items you want.
This, however, should not be confused with the search field syntax, where you can specify an OR list using the format “ITEMA; ITEMB; ITEMC.” This syntax can be used for any field, regardless of whether the fields are lookups or multiselects.
It seems that Anna wants to search for all records that match any of the lookup values A, B, or C, even though the underlying attribute is a single-select reference (lookup). In other words, the expectation is that the search field dropdown should support multiselect, even if the field attribute itself does not. I think it would be a reasonable enhancement request for a search field lookup to support multiselect functionality, simplifying the use of the A; B; C syntax.
Answers:
While there is multiselect (multi-LOV) support, you cannot convert a normal lookup reference to a multiselect in Page Designer. For this functionality to work, the attribute must support multiselect on the server side.
There is no way to control the behavior of the search field independently of the actual field behavior in Page Designer. The search field will function according to how the field is configured.
