Latest Contributions by RhettZufelt

@SupriyaK wrote: If you look at the screenshots above the aliases/display names are set at the data level. That is the whole issue, they aren't being honored in the visualization. Actually, in the case I submitted above, I see just the opposite.  Setting it in the Visualization is honored in the data table, popups, etc. but is NOT honored in the Data/Fields tab of the item details.  Even though the alias's are changed in the visualization, which seems to be honored in the Data/Table, and in any popups/tables when added to a new webmap, it still shows them as the same in the Data/Fields tab. However, as you say, if you load the link above into a new webmap, it (tables, popups) honors the alias's set in the service.  But, if I create an AGOL item from it, will only display by the field name, even though the alias shows in the Display Name in Data/Fields. But, if I go into the visualization tab of the new item (that loads this service), I can change the Display name to what I want, and it is now honored in everything EXCEPT the Data/Fields tab. So, testing with these two feature services, it appears that changing things in the visualization tab of the item does seem to work in most places, the Display name in the Data/Fields tab in the item details is very misleading and seems to have nothing to do with what is actually displayed elsewhere so probably best to ignore what it says. So, if I add the REST endpoint you provided into a new AGOL item and look at the Data/Table, it shows how, as you noted, they have reverted to the Field name and not the alias set in the service: But, if you look at the Fields Tab, it shows as if the alias are preserved from the REST service: If I go to Visualization tab of the item details and change the Display name there (I only changed the first 3 to make them obvious) and remember to Press the Save link:   then the Data/Table will show the updated Display names that were set in the Visualization tab: BUT, if you look at the Data/Fields tab, nothing has changed: Then, load that new AGOl item into a new webmap, and the table and popups honor the changes I made in the visualization tab: So best to completely ignore the Data/Fields tab when testing as it seems to have nothing to do with anything. You might consider a tech support case on this, as there definatly seems to be a bug in the system.  It appears that the Data/Fields tab in the item details is honoring the field name/alias's set in the REST service, BUT, everything else is not. R_ ... View more

I use python to do this for my street names.  First, I create a dictionary, then I use arcpy.da.SearchCursor to populate it with my street Code:Value pairs: (I don't have a street called "Pathway" in the source table, so below is how I 'add' it to the list) import arcpy update_dict = {"fields": [ { "name": fieldname, "domain" :{"type" : "codedValue", "name" : domainname, "codedValues" :[ {"name" : "Pathway", "code" : "Pathway"} ]}}]} with arcpy.da.SearchCursor('streetsFC', ["Code","Street"]) as cursor: for row in cursor: update_dict['fields'][0]['domain']['codedValues'] += [{"name" : row[0] , "code" : row[1]}] dictionary format is as follows: update_dict = {"fields": [ { "name": "StreetName", "domain" :{"type" : "codedValue", "name" : "Streetnames", "codedValues" :[ {"name" : "10th Ave", "code" : "10th Ave"}, {"name" : "10th St", "code" : "10th St"}, {"name" : "First St", "code" : "First St"} ]}}]} Then I use the python API to update the domain list on the HFL in AGOL: from arcgis.gis import GIS my_agol = GIS(url='https://yourorg.maps.arcgis.com', username='adminuser', password='adminpass') lyr = my_agol.content.get('ItemIdNumber').layers[0] update = lyr.manager.update_definition(update_dict)  Not sure how responsive Field Maps would be with that many values in a dropdown, but my streets with 5100 values works fine. Also, whatever order the domains are in the update_dict is the order they appear in the dropdown. R_ ... View more

Did you try the Feature to Line tool? Don't have your data to test, but my testing splits all the lines exactly at the polygon boundary so that the one to many spatial join has a single match for each line segment.  It also retains all the attributes as well. R_ ... View more

That is weird.  The snapshot I provided last is what i see in the Visualization tab in AGOL, but I see the same as yours in Portal 10.9.1.  Perhaps an org setting or something?  Afraid I won't be able to help with that one. R_ ... View more

After seeing this screenshot, it appears that you are in Portal, not AGOL? I don't know if this option existed when Visualization tab was still opening in Classic like your screenshot.  I don't see it in Portal 10.9.1.... In AGOL, Visualization tab has access to the Layers, and then the table:   R_ ... View more

I've had similar need, but in my case, most of my lines crossed the polygon instead of following it. I used the Feature To Line tool with my line layer and the polygon layer as inputs with Preserve Attributes selected. This creates a fc with all the lines, both polygon outlines and the input line fc data, split at the intersections, with attributes from each. I then select all features in the output that have a null value for the copied over ID field from the lines.  This way, I'm selecting only the polygon boundaries (as they don't have that particular ID field) and then I delete them.  Then I delete the un-needed polygon attributes that were carried over to the lines. This leaves me with an attributed copy of my line input data that is split at each of the polygon boundaries that I can use for my spatial join(s).  Have not run into it myself, but the Feature To Line tool has 'some' flagging/handling of coincident lines/boundaries as well. Different scenario, but thought I'd put it up here as don't think that is what that tool was originally intended for. R_ ... View more

you can try the Check Geometry or Repair Geomtetry GP (which has a Delete Features with Null Geometry setting) tools to see if it has issues.  Always safest with tools such as Repair Geometry GP tool which modify the existing featureclass to test on a copy first.  At least if it will allow you to copy it. R_ ... View more

To set it at the data source level, you will need to open your contents page and navigate to the folder where the FERM engagement v1 251002 hosted feature service is located, click on the three dots to the right, and select View details. In there you will see the Visualization and Data tabs in the upper right. R_ ... View more

I am not seeing a difference. I have also not always had good luck with just clearing cache. You might load the webmap in Edge, press the F12 button to enter developer mode, then right-click on the reload button and choose "Empty cache and hard refresh" and see if that makes a difference. You can close developer mode once it starts reloading. R_ Edit:  To add, I am still on Windows 10 ... View more

Glad it worked. ... View more

If you don't see the blue plus sign, first place I check is the editing capabilities in the Settings tab of the item details page:   R_       ... View more

Agree, that can be tedious. If you want that set at the data level, then you would need to do the same tedious steps, just in the Visualization tab.  That will update the data source so that when you add it to a web map it will reflect the modified values.  However, since this can be overridden in the web map, any that already have it saved will show as it 'used' to be.  You would have to remove and re-add that service to the map to see the new values. In the Visualization tab, select the layers you want to modify, select the layer, click the fields button and modify as desired (be sure to click the Save button: You will see the new alias when you switch to the Data tab and look at the table.    However, it appears as if there is a Bug or 'known limitation' that the Fields tab in the Data tab does not reflect it but is reflected when added to new maps. R_     ... View more