" /> ListLookupCfg vs ListGetDataCfg - Genesys CTI User Forum

Author Topic: ListLookupCfg vs ListGetDataCfg  (Read 964 times)

Offline rolf_b

  • Newbie
  • *
  • Posts: 20
  • Karma: 0
ListLookupCfg vs ListGetDataCfg
« on: September 13, 2023, 03:48:25 PM »
Advertisement
Hello,

I am still stuck with IRD and URS.

With ListGetDataCfg I can specify a list, in this list I can specify an item (the annex section) and in this item I can read the value of a key. The value I get may be ''. But since '' is a valid entry, I still don't know if that key exists, or if its value is just empty.

With ListLookupCfg, I can address a list, in this list I can address an item. So, I can check if a section exists. Nice, but what about keys? Is that impossible?

I tried ListLookupCfg('List', 'Item/Key') and ListLookupCfg('List', 'Item.Key'), with no success. Am I missing something? How can I reliably check if a key exists in a Configuration List-Object?

Thanks
Rolf

Offline Campfire

  • Jr. Member
  • **
  • Posts: 73
  • Karma: 0
  • If you must blink, do it now.
Re: ListLookupCfg vs ListGetDataCfg
« Reply #1 on: October 04, 2023, 09:53:04 AM »
What's the aim here?

If we want to check if a key exists in a list, use ListLookupCfg.

Now that we know the key exists and if we want to check the key has empty string as value, check its value (using ListGetDataCfg maybe) against an empty string. say x == ''.

Ofcourse the functions can be nested.
« Last Edit: October 06, 2023, 01:12:48 PM by Campfire »

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: ListLookupCfg vs ListGetDataCfg
« Reply #2 on: October 05, 2023, 01:11:36 PM »
You can receive entire list by not specifying the item or by using * instead of real value (do not remember it well). Based on that you can check whether the specified key does exist in the list or not