• State Not Answered
  • Replies 27 replies
  • Subscribers 7 subscribers
  • Views 5621 views
  • Users 0 members are here
Related Discussions
Home » Discussions » AI and Rules

Having trouble with a cascading dropdown. Basically, I have an editable grid tha

judym598
Certified Senior Developer
Having trouble with a cascading dropdown. Basically, I have an editable grid that has 3 dropdowns. The user selects a user from the first dropdown, assigns a role to the user with the second dropdown and assigns an area of expertise with the third dropdown. I got the rule to work with the first 2 dropdowns, but the choices presented with the third dropdown are dependent on the user selected in the first one. I have a query rule that brings back a list of expertises based on the userId. So I created a local!selectedUserId variable to use in my query rule that displays the dropdown list and added an a!save statement to update that local variable with the selected user id. But I get an error when I access this form because the query rule cannot find a userId. Here's the error I'm getting and I've attached my updated rule for the grid.
Expression evaluation error in rule 'ips_getexpertisebyuserid' (called by rules 'ips_assignuserrolesgr...

ips_assignUserRolesGrid_new.txt

OriginalPostID-170455

OriginalPostID-170455

  Discussion posts and replies are publicly visible

Parents
  • 0
    @judym I have just made one more change. Please find attached the code snippet. Do let me know if there are any issues again.

    Actually there is some confusion because of the todatasubset() conversions which were being done in the interface and they aren't actually needed as said by me earlier in the post. Let's remove these conversions when you get the interface up and working. Coming to if conditions, they are needed because your interface fails if null values aren't handled properly. But you could test the interface rigorously and remove them if needed at a later point.
Reply
  • 0
    @judym I have just made one more change. Please find attached the code snippet. Do let me know if there are any issues again.

    Actually there is some confusion because of the todatasubset() conversions which were being done in the interface and they aren't actually needed as said by me earlier in the post. Let's remove these conversions when you get the interface up and working. Coming to if conditions, they are needed because your interface fails if null values aren't handled properly. But you could test the interface rigorously and remove them if needed at a later point.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.