Accepted Solutions
When you first added the layer to the map, the map got the list of available fields in the layer and stored it in the map. Adding a new field later didn't alter the map's representation of the available fields. Removing the layer and adding it again caused the map to get all the available fields at that time, which included the new field.
The visible fields in the map are defined by the popup settings, which affects both the table and the popup. (See below for why this happens.) Alternatively, you could have configured the popup to show the new field (choose Configure Popup from the layer menu, then choose Configure Attributes to display the new field). Doing this will save it to the map. You can do the same thing from the layer's Visualize tab, which saves the popup configuration to the layer.
Why is field visibility in the table governed by the popup? This is a old "feature" that resulted from how ArcGIS Online developed over the years.
At first, AGOL only had a popup, no table. In defining the popup, you'd specify the visible fields you wanted to display in the popup. Then, we added the table to the map viewer. It made sense that the visible fields you displayed in the popup would also be the ones you want to display in the map viewer table, so we reused the field visibility defined in the popup for the table as well. Tables in the map viewer are somewhat transient and we thought it might be strange if the popup showed one set of fields and the table a different set. Then, we introduced the Data tab with its much more persistent table. Still, the popup governs field visibility in the Data tab table. Thus, even though you show a field from the table show/hide menu option, it will only persist while you're looking at the table. Refresh the page and it will revert back to the popup field visibility definition. We do want to decouple field visibility in the table from the popup, but just haven't done it yet. It's on the list.
Mike
When you first added the layer to the map, the map got the list of available fields in the layer and stored it in the map. Adding a new field later didn't alter the map's representation of the available fields. Removing the layer and adding it again caused the map to get all the available fields at that time, which included the new field.
The visible fields in the map are defined by the popup settings, which affects both the table and the popup. (See below for why this happens.) Alternatively, you could have configured the popup to show the new field (choose Configure Popup from the layer menu, then choose Configure Attributes to display the new field). Doing this will save it to the map. You can do the same thing from the layer's Visualize tab, which saves the popup configuration to the layer.
Why is field visibility in the table governed by the popup? This is a old "feature" that resulted from how ArcGIS Online developed over the years.
At first, AGOL only had a popup, no table. In defining the popup, you'd specify the visible fields you wanted to display in the popup. Then, we added the table to the map viewer. It made sense that the visible fields you displayed in the popup would also be the ones you want to display in the map viewer table, so we reused the field visibility defined in the popup for the table as well. Tables in the map viewer are somewhat transient and we thought it might be strange if the popup showed one set of fields and the table a different set. Then, we introduced the Data tab with its much more persistent table. Still, the popup governs field visibility in the Data tab table. Thus, even though you show a field from the table show/hide menu option, it will only persist while you're looking at the table. Refresh the page and it will revert back to the popup field visibility definition. We do want to decouple field visibility in the table from the popup, but just haven't done it yet. It's on the list.
Mike
