Skip to main content
zacharyg0001
February 20, 2024
Question

Using a!urlForSite() to pass data to gridField user filter

  • February 20, 2024
  • 6 replies
  • 0 views

Hello,

I am trying to make use of the new function: a!urlForSite()

It seems like a great use case for a!urlForSite() is to pass data to a site page that shows a record list, so that the user can be directed a filtered set of data. As far as I can tell, this can only be done using custom components to create filters, and cannot be used to pass data directly to ootb user filters. I usually try to avoid using custom components as filters because these cannot be saved as user filters and they don't appear in-line with the search field. Am I missing something? Or is passing data to user filters still not supported? 

Thanks!

6 replies

venkatrea696188
February 20, 2024
pass data to a site page that shows a record list

Hi Zach, 

We use urlforsite() for passing values to a interface (Site page type) 

https://docs.appian.com/suite/help/23.4/fnc_scripting_urlforsite.html

pass data directly to ootb user filters

For this i suggest you to  configure record level Security....

zacharyg0001
February 20, 2024

Hi Venky,

Thank you for the reply. Please let me clarify my object setup...

Appian Site -> Interface Rule -> gridField()

venkatrea696188
February 20, 2024

Can't pass to record filters directly...

stefanhelzle0001
Brainy
February 20, 2024

You are right. The OOTB user filters cannot be configured in such a way.

zacharyg0001
February 20, 2024

Hi Stefan - thank you for the response. 

It seems like if Appian recommended best practice is to use user filters, they need to be more functional. Having to create custom filters to support advanced functionality seems to add additional complexity and maintenance. 

stefanhelzle0001
Brainy
February 20, 2024

That's the tradeoff we need to make to gain developer efficiency.

But, I would not consider custom built filters to be any complex or difficult.