Agentry CT drop down doesn't populate record if there is only one matching record with cascade index

[Sudhir_Lenka]

Hello Team,

We have an Agentry transaction screen where the Complex table drop-down field does not show the right record if there is only one matching record as per cascade parent index. 

Details :-

• There is an UI element(Template Equipment) of type Complex table drop-down in a transaction screen.
• The selection method in the UI element is "Always Open Dialog with Search".
• Data filtered/shown matching with two level index (By class and by Category) - Class is another drop-down in the same screen and category is always "A". 
• The functionality is - when class is selected in the first drop-down then only matching(by class and by category) template equipment will be populated/shown in the second drop-down (Template Equipment).
• It works fine except one scenario as mentioned below. 
• Agentry Client :- WPF (72.x)

Failure scenario :- When there is only one matching template equipment as per selected class then it does not show the right equipment, it shows the previously selected equipment.

Observation :- 

• This works fine with Agentry client 71.x but does not work in version 72.x and 73.x.  
• It also works fine in client version 72.x and 73.x when we change the selection method to "Drop-Down menu".
• It only fails if the matching record count is 1, if it is more than then it works perfectly alright.

Is this a known issue with Agentry client version 72.x and 73.x ?  

Your response would be much appreciated.

Thanks,

Sudhir.

[Randall_Roman]

Sudhir - Have you used the Test Environment to debug your cascade rule Z_ReferenceEquipmentParent? Can you see that it is returning the expected value when you have multiple matches and singles?