Hierarchical custom LoVs in IFS Cloud

​@Alexander Heinze I’m afraid what you’re asking for is not possible through config.

See the below post that goes in the same direction.

Hi, 

The issue here is that you cannot add a filter when defining a custom attribute of the reference type. However, the client configuration concepts that have been introduced might be of interest.

Conditional LOV Filter
For more information, refer to the Conditional LOV Filter documentation.

Conditional Enumeration Filters
For further details, see the Conditional Enumeration Filters documentation.

Kind regards

Tobias Furberg

That’s exactly what I’m playing with at the moment! 😁

As I got the question from the side I just want to clarify. When I wrote 

“you cannot add a filter when defining a custom attribute of the reference type”

What I meant is that when you define your custom attribute as a reference. You select the view that you want to reference and then what attributes to display to the user. Here, you can not specify that you want to filter the list of values. I’m not saying that a custom reference attribute can not be filtered in the client. 

Conditional LOV filters can be applied to any reference (LOV) attribute, standard or custom, in the client. 

With help from ​@tofuse I managed to achieve exactly what I was looking for. Solely using Page Designer! 😁

​@Marcel.Ausan , ​@Rukmal Fernando fyi.

Looks like I’m late for the party 😎

Nice job ​@Alexander Heinze

I’m curious to know how you managed to solve it. As I last checked in 23R1 , conditional enumeration filters doesn’t accept dynamic values as filter conditions. has this been changed in 24R1?

However I managed to solve it using Datasource Aggregate Refs as described in this topic.

Adding a dynamic filter to LOV Custom Field in 23R1 | IFS Community

Cheers!

Damith

This one uses a filter on a reference field, not an enumeration. Cannot remember though when this kind of filter was introduced.

​@Alexander Heinze
Thanks for sharing ACP. Very useful! 

​@Alexander Heinze you only uploaded the word doc, without the ACP.

I can see ACP inside word doc :)

 

If you wonder how LOV2 gets emptied when you select a new value in LOV1…

The entity that I pick from has a field NULL_VALUE.

When you pick into LOV1, LOV2..5 get updated with NULL.

​@rkescoupland FYI.

thank you for that insight on clearing! 

Alexander Heinze wrote:

If you wonder how LOV2 gets emptied when you select a new value in LOV1…

The entity that I pick from has a field NULL_VALUE.

When you pick into LOV1, LOV2..5 get updated with NULL.

 

​@rkescoupland FYI.

That’s really cool ​@Alexander Heinze thanks for sharing.

unfortunately - it did not work in my case - i assume because my lov are separate - but i can see it is a neat way to solve this issue in many scenarios. thanks for sharing😀