Hey @gilcrest, I know we were able to help sort this out via the Support chat but I thought it would be good to reiterate our response here for visibility 
We did ship a change to how the Select and Multiselect components handle data. This is a change from a very familiar pattern but ultimately we believe it improves the ease of use and the functionality of these components. Since these changes are still very fresh we haven't quite caught up with our docs, unfortunately.
For the updated Select Component using the Mapped field to dynamically enter data, you'll enter an array of items into the data field:
Each item can then be referenced for all its indexes in data with {{ item }} in the Mappers inputs:
This way if you entered an array of objects into the Data array, you could simply key into the values of each object for the values and labels in their respective input fields. Here's an example below that will set up the Select Component with an array of values [1, 2, 3] and an array of matching labels ['one', 'two', 'three'].
You can also use the variable i in these mapper inputs to reference each index of the input Data. For example, the below setup produces the same result as the above:
You can also reference each index of the data array with i and item to set other mapper fields (Caption, Tooltip, Hidden, and Disabled), giving you very granular control over how your data can be displayed and used in the Select Component.
OR if you want to enter data manually, you can select Manual from the Items toggle, enter all of the data into your select component fields manually, and drag and drop list items to reorder as needed:
For your specific case, I think if you change your
- Data input to be
{{jurisdictionDropdownQuery.data.data}}
- Value input to be
{{item.Codes}}
- Label input to be
{{item.Names}}
then your select component should work as expected. This is assuming that jurisdictionDropdownQuery.data.data is an array of objects.
As to why you're seeing these updates to the select component in some places but not others, we're rolling this change out slowly and it has only been set for a percentage of accounts. This shouldn't be any cause for concern, one of the accounts has the feature flag set and the other doesn't (at least not yet) 
I hope that helps clear things up for you and anyone else who might have ended up in a similar situation!
