I would greatly appreciate the ability to use field values as symbology values, as is possible in ArcGIS Pro when checking the box for 'Allow symbol property connections.' In fact, I have a layer that uses this for color. It uses single symbol symbology, but each feature appears a different color since the hex code is stored in a table and set up to do so. When I go to publish online, though, not only does it not give any warning that this is not supported in AGO, but my features upload with a default gray appearance. The only workaround seems to be to manually set the color of each symbol class and to save that to the layer, which is still undesirable as it results in massive legends that aren't really necessary and manual labels for everything. Transparency by attribute is already an option, but there ought to be parity with Pro in this regard.
This is supported but we are seeing some unexpected outputs from Pro publishing side and are working with the team on getting this solved. You can log an issue with the Pro team on this for tracking.
Here is an example I made after making some manual edits to the web map using 3 fields with rgb values
https://jsapi.maps.arcgis.com/apps/mapviewer/index.html?webmap=bcda0069313e43e8a63800c250b8bd84
Sorry for the confusion- manually meant I did this one through ago-assistant and wrote out some web map JSON.
First published a web map from Pro with the option to use symbols compatible with all apps unchecked in the share web map dialog. Then I made the few changes to the primitive overrides that are written under the web map JSON to align with the CIM spec and what the JSAPI which handles the map view layer drawing expects.
@RussRoberts thank you very much for your contributions. I have the same problem, when publishing a service with ArcGIS Pro 3.0 in ArcGIS Enterprise 11.0 with this custom symbology, using an ARCADE expression for the color assignment, the service only respects this symbology with the map image, however, with the feature service it does not work, that is, the custom colors are not applied with the expression.
Is there any solution to this problem?
We did make a change in API that reads the output that Pro writes which was added in the last release of Online and I think will be part of 11.2. If you can share the Pro project I can take a look to see if some map JSON tweaks could get it to work in 11.0
@RussRoberts Does the "'Allow symbol property connections" work "out-of-the-box" when publishing a feature layer (or Web Map) from Pro to AGO? Meaning I don't have to go into AGO Assistant and fiddle around to make it work.
I've tried every which way but when I publish either the feature layer or map to AGO my field value symbology reverts to some default level.
Basically, just hoping for a simple yes or no answer...and if it's a Yes, what should I be looking for to make it work...ok, maybe not so simple of an answer 😁
Thanks!
Yup it should work. you want to make sure you are setting the expression with arcade for the symbol driven property is the main thing when authoring in Pro. Also this will only work in 4.x based apps like Map Viewer(not classic), Dashboards, Experience Builder and Instant apps. Also make sure you have "use compatible symbols" unchecked when sharing from Pro. If you can share the Pro project I can also take a look
@RussRoberts Thanks for the quick response. I'm not using Arcade to drive the symbology, I'm using the "Allow symbol property connections" feature which allows you to use a field to define the symbology...in this case the color. Everything else you mentioned I've followed. I'm fine with sharing the Pro project...how do I do that?
Thanks!
You can toss it into a group and invite russell_jsapi
@RussRoberts Done and hopefully I did it correctly 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.