Latest Contributions by JonathanMcDougall

@JoseBarrios1  I've republished for you, it's still rough but should work as an example. Elements are as follows; Map - shows nothing more than the selection from the list, I've not set any actions at all. This dataset is just a dataset of states, nothing more. List - set to allow multiple selections of "states". It's got one action to select records of species to show in the table. Table - the data is a table of "species" that was published with the "state" feature layer, so two datasets with the state as a common id. The table is set to show selected records. Filter - speaks for itself. Happy to give further info and screenshot to develop further. ... View more

@JoseBarrios1  Hi You may not have a list of species in the map, however, the common field in map, or list, and table is State, I assume. This being the case, when you add the trigger, it will ask for this common field from the two datasets. If you look at the link above, you will see I've put "states" into a list, from that list you can select multiple which will then populate the table from selected records. I've left the map there, but no map interaction is needed. I'll add more records to make it a bit more obvious what's going on. ... View more

Sorry for this being rough - buy may give you ideas. Lists, filters, table, map and extents. Re-published ExpB ... View more

There's perhaps a couple of ways, some smoother than others. @JoseBarrios1  One approach; allow the user to select the state(s) through a filter with multiple clauses then have a card related to the ethnic group information. I could put a quick example of what I mean together for you ... View more

@RyanBohan  You're welcome. ... View more

@garmendariz  I really should check first before replying, however, changing the colour palette may change the indicator colour. (Now off to check) ... View more

We'll perhaps differ on the value of the "View for Empty" - if I were to use it, as I've suggested elsewhere, I'd create a "99999" feature that has attributes that give the user some level of detail, just not the detail of the dataset. I think sometimes it could cause confusion to the user if handed record one (or whatever) as they land - I'd want to manage the make a selection process to see the data. You don't online shop and start with a basket that already has one item in it. ... View more

@Song_Li  Interested in this too, would help define capacity or hot & cold. ... View more

@ShengdiZhang  Hi, thanks for the response. Have tried your suggestion, however, same result with the filter "switching off" as soon as I close the window. All filters remain active, using the other arrangements too, right to the point of clicking off window. Looking forward  to the bug-fix. ... View more

@Anonymous User  So, the user interaction is to select an item on the map within your app and see the selected info? If so, then all you have to do is ensure, within the card you've created, you don't use "Selected Features" but "Default" within the dynamic fields, but you do make sure the data action from the map is to "on select change framework" I've thrown a field into this screenshot for an example. Card on the left has fields set to "Selected", the little box on the right is set to "Default" for dynamic fields - Default just brings through a first record, regardless of any selection.   if I make a selection then you'll see both details change accordingly. This means, as long as the user knows to select data and  isn't put off by always getting a record given to them on open, then all is good. Me, you'll see on the first grab, I've got the dynamic field asking the user to "Select a Feature". You could think about the way that first experience is shown, and change the wording of the dynamic field. (hope this makes sense?) ... View more