Zum Hauptinhalt gehen

SelectFeatures activity: Hoe to limit the columns visible in resultgrid

Kommentare

8 Kommentare

  • Nico Burgerhart
    You can exclude fields in the manager; edit layer > Fields tab.
    0
  • Permanently deleted user
    Hi Nico, Thanks for the reply.

     

    If I exclude fields in Fields tab, they will not be visible when I do any Query or Identify task too right. I am looking for a solution where the fields should be limited only when I run my workflow using Select Features activity like I said in my question. If I use any Viewer tool I need all the columns to be visible.
    0
  • Nico Burgerhart
    The Select Features takes the field visibility settings from the layer when you fill the MapServiceID and LayerID properties, this is by design.

     

    You can leave this properties empty. Then you will see only your defined fields in the query task. But I'm not sure it is possible to zoom/highlight a feature in the map.

     

    An alternative could also be multiple copies of the layer, with different visibility settings.

     

     
    0
  • Permanently deleted user
    I tried your suggestion too (Leaving the properties MapServiceID and LayerID empty). In that case I am getting only the columns which I wanted and Zoom to feature function is working too. But the problem is the label of the first tab is being overwritten by the last tab. I am using 'FeatureSet DisplayName' parameter of SelectFeatuers activity to set the label name. In the below Screen shot,

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000TUP6&feoid=Body&refid=0EM60000000LzwW" _/_img_

     

    the first tab label which is read 'Address' should actually read 'Point Assets'. The behaviour which I observed is if I dont give the ID properties, first tab label of every such result is being overwritten by label of last tab.
    0
  • Nico Burgerhart
    This seems a bug to me, did you report it to Latitude?
    0
  • Permanently deleted user
    Not yet.. I wanted to be sure from my side first. Hopefully if someone from latitude replies here it'd be more helpful. Anyway I'll report it now....Thankyou for helping :)
    0
  • Permanently deleted user
    I agree, it does sound like a bug. We've received the workflow and someone should be able to look at it shortly. I've asked that they follow up here once they've determined where the problem lies.
    0
  • Permanently deleted user
    Thankyou very much for the follow up Jordan :)
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.