I don't know why I felt the desire to write this much, maybe just because I've had to explain this to a lot of people over the years who are first learning the software, and I just hope it helps someone. I apologize if what I write sounds obvious to you!
Best,
Katherine
======================
TL;DR - It's important to understand the "hierarchy" of layer settings between hosted feature layers, web maps, and web applications. The actual data values don't have a hierarchy, so edits are reflected everywhere regardless of the interface.
======================
Answer to your specific question - I would recommend one of two options for having pop-up configurations reflect in the web application:
- Use custom settings for the Edit Widget in the web application and make changes to field visibility and aliases (I assume you mean alias when you said "field names", as field names cannot be changed).
- Use "Honor settings in the web map" as the setting for the Edit Widget in the web application, and make changes to layer pop-ups etc. in the web map. These changes should then be reflected in the web application.
As for editing the values in the table, you have many options for this and which one you choose will depend on your preference of the interface and the complexity of the calculations that you need to make. You can edit through the "Data" tab of the Item Details page, you could navigate to the feature directly in the web application and edit values through the Edit Widget, you could change specific values through the attribute table in the web map, or you could edit the data by pulling the hosted feature layer into ArcGIS Pro (use the Catalog pane, then search your organizations contents). Note that you can perform field calculations only through the Item Details page (limited to using Arcade or SQL) or in ArcGIS Pro (where you can use other languages, like Python). Changes to the data will be reflected everywhere, regardless of which interface you use to make the edits.
======================
A much more long-winded explanation...
So, to answer this question it's important to understand how everything is "layered/stacked" in AGOL (I think of it like a Matryoshka doll, but a more accurate comparison would be like Specificity Rules in CSS).
At the "base level", you have the hosted feature layer. You can configure default setting for symbology, pop-up, visibility range, etc. from the "Visualization" tab of the Item Details page. Whatever settings are saved at this level will be the settings of the layer when it is initially pulled into the web map.
That brings us to our "second level", the web map. You can change settings for the layer in the web map in case you want it to differ from the defaults (useful if the layer is used in multiple web maps that have different requirements). However, keep in mind that changes made at this level override the defaults. So even if you go back to the Item Details page and change something from the visualization tab, the change won't be reflected in the layer that is already part of the web map. This can work in reverse though. Because the settings in the web map are higher than the default settings, you can save the settings of the layer and they will be applied at that HFL Item Detail level.
At an even higher level, there's the web application. These applications "consume" the web map and build on top of it by adding additional functionalities and widgets. In the Edit Widget, you have the option of using custom settings, or you can "Honor settings in the web map". If you choose custom settings, you can dictate which layers are editable and even further customize those editable fields my modifying the aliases of field names. These setting changes would be a status unique to the web application, so if you made changes to the field names the pop-ups would display differently in the web application when compared to the web map.
While layer settings will vary based on the hierarchy, remember that the data itself is "universal" and a change to an attribute in one interface will reflect wherever you view the data.
Best,
Katie
“The goal is not simply to ‘work hard, play hard.’ The goal is to make our work and our play indistinguishable.”
- Simon Sinek