Hi Randini.

I haven’t worked with this functionality just yet but I found an entry in the documentation that maybe can help:

https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/100_conditional_lov/

Thank you much.
Best regards.
Gonzalo.

 

Hi Gonzalo,

Thank you very much for the link.

However this example is not for passing a dynamic value. I’m looking for that scenario. Anyway thanks again for your input.

Hi, Here, the value accepts an OData filter syntax. So I think we need to query core framwork team to see if we can have substitutions here. Further, good place to start is trying to do exact same thing in developer studio with marble and see what we have in page designer.

@Nils Wendelöv Is there a way to set a column value dynamically to an Odata filter? I have tried few ways through page designer but couldn’t get any to work. Maybe we are not supporting such functionality yet?

Thanks Chanaka. Yes I want to know whether we are supporting this functionality or not.

did you find the answer?

Not yet Franck

I'm looking to do the same thing ... with custom fields 

I’ll update the post if I get anything. Seems there is a high demand for this. Another person reached out to me asking whether I got a solution.

I don't know if the syntax of my fitre is correct 

Hi All,
 

This issue is not a bug in the application. It's important to understand that standard attributes and custom attributes have different capabilities. Custom attributes come with certain limitations as they are configuration-based.

The specific requirement mentioned here cannot be fulfilled using the page designer. There are several community links that demonstrate how to achieve this, but they are relevant to IFS Apps 10 and do not apply to the IFS Cloud track. The IFS product team recommends considering customization to achieve the desired outcome, and you can find detailed information in the IFS Documentation here:
Dynamically changing values.

You might wonder if this cannot be achieved using the page designer, then can we expect a fix in a future release?

The product development team has indicated that providing a definitive yes/no answer regarding whether this issue will be addressed in a future release is not feasible. Based on the existing design, it appears to be something that we are unable to achieve.
 

I hope this explanation clarifies the concern.

Thank you.
Kind regards,
Sandun Madola.

Thanks Sandun for the clarification

In another post the recommendation was to use Datasource Aggregate Ref parameters to filter Custom LOV field.

Is this information available for non-partners? The above link is restricted

Here is a Word document where I collected the answer from the other Community post. IFS employee Thisara was sharing a way to filter a custom field LOV.

I was stuck with the same problem as @Randini Jayasundara and this post saved me :)

The best part is that it’s possible to use dynamic values from the page in Datasource Aggregate Refs 

In my scenario I used a reference entity from another LOV field and it also worked!

LOV query looks like this

Customer env: 23R1

In another post the recommendation was to use Datasource Aggregate Ref parameters to filter Custom LOV field.

 

Is this information available for non-partners? The above link is restricted

Here is a Word document where I collected the answer from the other Community post. IFS employee Thisara was sharing a way to filter a custom field LOV.

 

I was stuck with the same problem as @Randini Jayasundara and this post saved me :)

The best part is that it’s possible to use dynamic values from the page in Datasource Aggregate Refs 

In my scenario I used a reference entity from another LOV field and it also worked!

 

LOV query looks like this

Customer env: 23R1

​@dsj , can you please elaborate more on how you use this other Lov reference here ?

I’m trying to do a similar thing but my filtration doesn't work at the moment.

in my case, in the functional object window,  I have added two custom fields 

1. to get the Object Level to Object Type entity (persistence reference field )
2. persistence reference using the FND Boolean (Yes No toggle)

I did the data source aggregate ref for the 2nd field and it works perfectly fine, Object Types can be filtered based on the Boolean field. but when I add the second filter to further filter the select fields based on the object level, it doesn't work and the Object type LOV become empty in the functional object window.

environment 24R2 SU 3

Below are some screen pictures

No data coming  :(

in the /payload it seems the filter parameters are passing correctly, but the values are not filtering. i tried to add this as a string directly to see whether it works or not, even when i pass as a string it comes empty. 

Any lead  would be helpful.

thank you so much.

Kind Regards!

Niyo.

​@dsj Found the issue :)

Thank you :)

Hi, This suggested solution is working for me as well. Thanks all.