How to change the name of a layer list item in HTML5?
Hello! I've read the article: How to change the folder/group layer visibility from a workflow in HTML5/Silverlight viewers. It works well in HTML5 for changing the visibility, but how to change the layer's name in the layers list? Nothing seems to be working in the DynamicExternal activity __SetLayerListItemInfo: name, DisplayName, Name... Can anyone help? Thanks a lot! - Vincent
0
-
Same here. None of the options seem to work ; the only one I can get to work is "SetLayerVisibility" and that doesn't even synchronize properly with the layer list on the left (as in : the layer group dissapears on my map, but it still ticked ON in the layer list , and you can never get it back on -- ever.)
This is very confusing. Have you worked out a solution to reliably turn on/off layers from within a workflow? f@poliart.com
0 -
Hi Frederic,
I'd recommend using the out of the box workflow activities SetLayerListItemInfo/GetLayerListItemInfo rather than DynamicExternal now that they have been made available that way. It's easier to configure than the DynamicExternal method, which was suggested specifically for a time period where the need for the activities was high, but they couldn't be released yet because the next Essentials version wasn't ready.
I don't believe there was an intent to use this activity to change a folder's name. The name input is used only to find the folder from the layer list. SetLayerProperty can't change the layer list names either, please read here (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&criteria=ALLQUESTIONS&id=90660000000TSSDAA4) for an explanation.
SetLayerListItemInfo and SetLayerVisibility should sync up with the layer list checkboxes when used to set visibility though. If that's not what you're seeing I would recommend contacting support. I have seen similar behaviour with layer theme and layer catalog bugs before, so it may be one of those or it could be an unreported bug.
Thanks,
-Amanda0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare