Unique Value Renderer, Many Fields support

4470
5
Jump to solution
10-21-2015 12:59 AM
ZdeněkJankovský
Esri Contributor

Hi,

I would like to ask about support of Unique Value Renderer with Many Fileds setting.

I am testing App Studio (Beta 4) with local offline *.geodatabase file. Our customer uses Unique Value Renderer with Many Fields (3 fields) in his MXDs quite often.

These layers are marked as Error during the Analyses in ArcMap 10.3.1 with File > Share As > ArcGIS Runtime Content... function, neither Create Runtime Content geoprocessing tool is not able to process it. Both say that it is unsupported content.

But I’ve found out that UniqueValueRenderer (https://developers.arcgis.com/qt/qml/api-reference/class_unique_value_renderer.html) is able to use three fields of Graphic to renderer a symbol.

From this point of view it seems Many Fields renderer is not supported by *.geodatabase package, but it is supported by Qt Runtime itself. Is that right? Is there any plan for supporting this renderer in next versions?

0 Kudos
1 Solution

Accepted Solutions
LucasDanzinger
Esri Frequent Contributor

This is something we are looking into for a future release, but is not currently available. When you create a mobile geodatabase with the create runtime content, it is using the same JSON spec as the feature service, which I believe also does not support publishing a service with multiple field renderer. You should see the same behavior between the mobile geodatabase and the feature service (an analyzer error stating that this renderer is not supported), and that is where the limitation currently is.

Hope this helps.

-Luke

View solution in original post

0 Kudos
5 Replies
LucasDanzinger
Esri Frequent Contributor

This is something we are looking into for a future release, but is not currently available. When you create a mobile geodatabase with the create runtime content, it is using the same JSON spec as the feature service, which I believe also does not support publishing a service with multiple field renderer. You should see the same behavior between the mobile geodatabase and the feature service (an analyzer error stating that this renderer is not supported), and that is where the limitation currently is.

Hope this helps.

-Luke

View solution in original post

0 Kudos
ZdeněkJankovský
Esri Contributor

Thank you for the info, as you said, Feature service does not support Many Fields as well.

Thank you,

Zdenek J.

0 Kudos
PaulHaakma
Regular Contributor

To add to the conversation.....

We had a similar requirement, to symbolize on multiple fields and encountered the same issue of not being to to achieve that in a published feature service or within the QML environment. Our workaround was to create a field just called "Symbology", and code our app so that on submitting a feature it created a string joining the values of the fields we needed.

We then set up the feature service to symbolize on the 'Symbology' field using the expected joined values. Of course, you end up with a LOT of potential value combinations very quickly! You also rely on interaction with the data being through the app only, e.g. if someone say, edits the data directly in Arcmap they need to remember to manually update all the fields correctly.

The point simply being, a) that it isn't currently possible, b) there is a workaround, but it's a lot of hassle.

Hopefully at some point they just update the capability of feature services.

RandallClark2
Occasional Contributor II

>Hopefully at some point they just update the capability of feature services.

Yes.

0 Kudos
ZdeněkJankovský
Esri Contributor

Yes,

that is the workaround we are going to use.

Our situation is a bit simpler, because data for offline use will be exported from main geodatabase - in that point we can calculate the field and use it.

0 Kudos