I want to create a dropdown list that will store some filter criteria to filter records. Where's the best place to actually store the data table inside the app?
The filters datasets won't change, so Collections don't seem appropriate, and I don't want to have to add something like a Sharepoint List just to store this small amount of data....
Could you elaborate a little on the information that you're trying to store?
If the filter criteria doesn't change and can't be updated by the end user, why not just hard code the filter options in the drop down? For example, you could set the Items property to the dropdown to:
["criteria 1","criteria 2","criteria 3"]
Going off of timl, is there a reason not to hard code the filters?
I guess maybe I am misunderstanding how DropDowns works...
As an example, I want to have a Filter called "Active Leads" to allow users to sort their leads with the Status = Active.
The data source (a custom connector/API) accepts a string, which contains an array of arrays to apply the filters.
For example, if I pass into the API the paramter "[[""status"",""="",""active""]]" the API will return the leads with the Status of "Active".
So I'd like "Active Leads" to represent the string "[[""status"",""="",""active""]]" in the Dropdown.
I guess what I can't figure out is what the function/syntax is to represent the Item name to the string without using some kind of table as a datasource for the Dropdown...
In this example, you would set the items property of the dropdown to this:
Table(
{Desc:"Active leads", Expression:"[[""status"",""="",""active""]]"},
{Desc:"Inactive leads", Expression:"[[""status"",""="",""inactive""]]"}
)
You'd set the display field of the dropdown to 'Desc', and you can then retrieve the selected expression by referencing drpFilter.Selected.Expression
User | Count |
---|---|
122 | |
87 | |
87 | |
75 | |
66 |
User | Count |
---|---|
215 | |
180 | |
138 | |
96 | |
82 |