• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Subscribers 4 subscribers
  • Views 5316 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Reports

Has anyone been able to implement multiple saves within a dynamicLink created by applyComponents?

Chris

Has anyone been able to implement multiple saves (list) within a dynamicLink created by applyComponents? My use case: I have a pie chart with links, which open a grid below for dta based on which section is clicked. Aside from saving the desired item, I also need to reset pagingInfo at the same time. Reason being, if the child grid is paged over to a startIndex greater than the next item's datasubset, an error is thrown. E.g., if pagingInfo startIndex is currenty 16 and you click another section of the grid which returns only 12 items, an error is generated - so, you need to reset paging when changing the filter. When I use the commented code below, the chart links will ALWAYS reference/populate local!filter with the first item in the value list. I also noted, if I simply add brackets {} around the local!filter variable within saveInto (second commented line below), the same issue is seen - clicking any section will populate local!filter with th...

OriginalPostID-177388

OriginalPostID-177388

  Discussion posts and replies are publicly visible

Parents
  • 0
    Actually we have paging grid with dynamic field on ID.
    when user clicks on ID we are storing entire row in a datasubset and try to store in other local variable using a!save in sveInto. In this case we faced two issues
    1.The data is not stored in second variable.
    2. When user clicks on other id the pv still showing old data which is selected previously(this is when we have multiple stores).

    so to avoid this in dynamic link we are storing in single pv and based on selection using some appian functions like displayvalue we are storing required data in second variable.

    Hope you got it !!
Reply
  • 0
    Actually we have paging grid with dynamic field on ID.
    when user clicks on ID we are storing entire row in a datasubset and try to store in other local variable using a!save in sveInto. In this case we faced two issues
    1.The data is not stored in second variable.
    2. When user clicks on other id the pv still showing old data which is selected previously(this is when we have multiple stores).

    so to avoid this in dynamic link we are storing in single pv and based on selection using some appian functions like displayvalue we are storing required data in second variable.

    Hope you got it !!
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.