Latest Contributions by RhettZufelt

In Mapviewer, below the popup config button, there is a Fields button. If you go into the Fields settings, click on the field that you want to change, you can change the display name. Which will then show the Display name in the popup as well as the table: R_   ... View more

My Testing: In the Data tab of item details, this example has NormallyOpen as the first field: If we open that in New mapviewer and open the table for the System Valve layer we see that is the case: In Visualization tab of Item details, select Layers, then open the table of the FC you want to re-order, re-order them and be sure to click Save in upper left (I moved motorized to be the first field): Now if we look at the Data Tab, you will see the new order of fields: And if we add the data to a new MapViewer and open the table, you will see the new order: So, it 'should' maintain the order set in the Visualization tab unless overridden in a web map. R_ ... View more

Making the changes in MapViewer will only change it for that map. If you want it to change 'permanently' (which can be overridden within a web map), you need to change/save it in the visualization tab.  This will re-order them in the DATA mode as well.  At least if you are referring to the Data tab in the item details. Testing was done with layer made for 123 Connect, created from existing features service if that helps. R_ ... View more

In AGOL, you should be able to go into the Visualization tab of the feature service, open the table, re-order and save.   This seems to change the order in tables when opened in web map. R_ ... View more

that is weird, something different in the data I guess. This is what I used: import arcpy geodatabase_path = r"Database Connections\PublicWorks.sde" output_file_path = r"C:\Temp\Output.txt" with open(output_file_path, "w") as f: arcpy.env.workspace = geodatabase_path datasets = arcpy.ListDatasets("*Storm_Features*", "Feature") f.write(f"Feature Dataset: {datasets}\n") for ds in datasets: for fc_fd in arcpy.ListFeatureClasses(feature_type='Polygon', feature_dataset=ds): print (fc_fd) f.write(f"Feature Class: {fc_fd}\n") fields_fc_fd = arcpy.ListFields(fc_fd) for field in fields_fc_fd: f.write(f"{field.name}, {field.type}\n") f.write("\n") And this is what came out (I removed all but the two sdStructure FC's in the output.txt file, one with and one without relationship class: Thought maybe it was because of "FeatureDataset" in the ListDatasets call, but seems to work the same with that or "Feature". R_       ... View more

Puedes usar la herramienta de escala para esto. R_ ... View more

Your script is working as expected for me. I tested on machine with Pro 3.2.1 and one with Pro 3.1.3, both connecting to SQL server sde 10.9.1.2.9 database. Not all the featureclasses in my feature dataset have relationship classes, but many do and they get reported just the same. R_ ... View more

With ArcMap you can use Catalog to enable feature access in the Service Properties:   R_ ... View more

This should work for definition query, use your fields: created_date IN (SELECT TOP 1 created_date FROM FeatureclassName ORDER BY created_date DESC) R_ ... View more

I have had very similar issue before.  I had to add Expects($feature, '*') to get it to work. Take a look at this post and see if it helps. R_ ... View more

what if you set aNL = '\n' var aNL = '\n' var popupString = '' popupString += 'test' + aNL popupString += 'test2' + aNL popupString += 'test3' + aNL popupString += 'LastString' return popupString R_ ... View more

Looking into this more, still no word on the Center map and add point, BUT, for the Manual location options (Allow, Warn, Block) to work, you need to have the GPS metadata fields in your feature service.  Then the Warn/Block options will work. However, with the Block setting and snapping off, (and the metadata fields) the ONLY point that can be added is at the GPS coordinates. BUG-000159708 R_ ... View more

See my post above, then you can right click on the 'new' style and 'Share as Web Style' to share with AGOL.   R_ ... View more

I think you want to create a new style with only the symbols you want to export. So, in catalog, double click on a style and it will open the style manager.  Right click and add a new Style: Then, you can open the style that you used for the map, expand Point symbol, hold shift to select the symbols you want, right click, copy, go back to syle manager, right click on the newly created style, and select paste. This will add the point symbols to new style that can now be shared and only contains the intended symbols. If you are using custom symbols (changed size/color/etc. from the original style), with just a few like that, it might be easier to just save them to the newly created style file. So, for this method, follow the above to create new stylx file, then go to the symbology tab for that layer. Click on a symbol and in the upper right waffle, select Save symbol to style: Give the style a name and select the new stylx file: Repeat for the other 4 symbols and you now have a style file that can now be shared. R_ ... View more

It's been a while since I did this as I'm now on portal and use dynamic services mostly.  But, in Pro 3.2.1 I would create the map I want to make into a tile layer, then choose Publish Web Layer from the Share menu: Then in the configuration tab, I choose the tile scheme and adjust the slider to include the LOD's that you want: and I always checked the cache locally button, otherwise I would often get timeout errors: This will build the tile package in folder specified (C:\temp) and when done, will upload to the organization you are signed into, and build the tiles for you. R_     ... View more