Skip to main content

Scenario:

I’d like to maintain a list of “Trade Shows” basic data with a status of active/inactive, and have a LOV only show the active records to pick from. Similar functionality to hiding/blocking coordinators, etc in other areas of IFS Cloud. 

 
I have a custom entity with two columns:

Column 1: Trade show (String)

Column 2: Status (CustomEnum: Active/Hidden)

 

On the Sales Lead entity (Business Lead), i have created a custom attribute that references the custom table. 

In my page designer, i’d like to add this field as a LOV, and have the LOV filter to show only the records where status = Active. 

I have found this page: https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/200_filter_enumeration_values/

But it doesn’t cover my exact scenario. Is this functionality possible to do without a customization? If not, is it possible to just Hard Code the values that i want to see manually?

For reference, I am on 23R1.8

​@mdezzi you got incredibly close! I believe Conditional LOV Filter is what you need.

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

best regards,

Rukmal

​@Rukmal Fernando Correct! I had LOV/Enum confused. Thanks for pointing me in the right direction. Thanks for the help!

For anyone looking to do the same, here’s how my Filter case looks:

And results in only showing the “Active” trade show from the “basic data” entity that i created.

 

​@mdezzi Hi there, 

I have a similar challenge here and I have an issue with the fields available from the advancedview. In my case, it only displays the field Cf_Display_Text and nothing else. Is your entity list auto generated from creating the custom attribute in Sales Lead entity? Did you have to modify or add any other list with page designer? 

I am on 23R1 as well.

Let me know if you need more details.

 

Hi ​@anguyen 

I think the selector and the advanced view just grab whatever Display Text you set up when you created the reference field in entity configuration (thats the part where you can add fields and separators and it concatenates them to build the cf_display_text). I discovered that you’re not actually forced to use that field. I found that you can delete the Cf_Display_Text field from the selector/advanceview and add whatever real attributes you want instead. I am on 24R2 now, but i believe this worked in 23R1 too. 

​@anguyen Following up on this, because I am working on another one of these and couldnt figure out which step i forgot. I was also seeing ONLY the Cf_displaytext to pick and couldnt figure out why. Then i remembered when you create the attributes in your “basic data” entity (the one you are referencing), you have to make sure you check the “List of Values” option. If you do that, when the Selector and AdvancedView lists get created, they will include Cf_displaytext along with any attributes that you checked LOV for. And you can remove Cf_displaytext and use the real attributes in your Search, Selector and Advancedview. Hope this helps!

​Hi @mdezzi

Yes, this was the part that I missed when I was trying to implement the filter. Checking the “List of Values” option did the trick. Thank you so much for getting back to me!

Reply


Terms & ConditionsCookie settings