Hello All, Does anyone have any experience with the a!pickerFieldCustom com

Jin Pheh

Certified Associate Developer

over 9 years ago

Hello All,
Does anyone have any experience with the a!pickerFieldCustom component? I'm using an expression that wraps an a!queryRecord call however using this as the suggestFunction returns all records regardless of input. However testing my query expression directly returns the filtered results as expected.

I'm only encountering this problem when using an expression as the suggestFunction - using a query rule for the suggestFunction works as expected.

Even more perplexing is that when I supply a fixed argument to the suggest function (eg: suggestFunction: rule!myQuery("test") returns no results at all when, again, testing the query function directly returns results as expected.

Discussion posts and replies are publicly visible

0 Robert Shankin
Appian Employee
over 9 years ago

Are you using a SAIL recipe as the basis for your design?
If so, make sure you're following the recipe documented for the same Appian version you're currently using. This recipe varies slightly from version to version.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jin Pheh
Certified Associate Developer
over 9 years ago

Hey Rob,
I'm not using a recipe as a basis for the design since the recipes all use a static array as their data source and I'm trying to hit a database.

My problem has to do with the returned dataset from the suggestion function as I can successfully use the component using a query rule but not a queryEntity expression despite individual testing on each being successful.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tyler Criste
Appian Employee
over 9 years ago

Note that the suggest function needs to return a datasubset. So if you're using a query rule that returns just the array of data, you'll need to wrap that in an expression that returns a datasubset. So the rule in your suggest function would be soemthing like this:

with(local!data: rule!myQuery(ri!input), a!datasubset(data: local!data, identifiers: index(local!data, "id", {})))
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Conor Cahill
Certified Lead Developer
over 9 years ago

a!queryEntity()'s .data field is a list of Variant, not a list of the desired CDT / type. You can try casting the .data field to a text array and remaking the datasubset with the text array.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jin Pheh
Certified Associate Developer
over 9 years ago

Thanks Tyler and Conor however I already checked that and I am explicitly casting my result set to a datasubset before I return it to the picker component.

In addition, the picker is showing all records regardless of what I type which indicates that the query is working and providing results in the proper format - just ignoring the filtering I am trying to reply. IE: No matter what I type the expression isn't receiving the value to search by - even when I hard code it as per my initial post.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tyler Criste
Appian Employee
over 9 years ago

I've attached an example that we used on one of my projects. Maybe it will help.
Custom Picker Field Example.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jin Pheh
Certified Associate Developer
over 9 years ago

Thanks - for future people searching and finding this post with the same problem the issue was that my query expression was using a load() instead of a with(). The a!picker element doesn't initialize a new context for the suggestFunction with every call and thus the first query, with all the results, was being carried over for all subsequent queries and never being executed again.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel