Zum Hauptinhalt gehen

Datalink token display changes in GE3.15

Kommentare

2 Kommentare

  • Permanently deleted user

    Hi to all

    time has moved on but still not much wiser.

    /customer/servlet/servlet.FileDownload?file=00P6000000eltsjEAA

    Note that the additional details window is empty!

    Here is the config for the Feature Description:

    <p>COMPKEY: {Hansen8.COMPKEY}

     

    </p><p>Type Description: {Hansen8.TypeDescript}

     

    </p><p>Another attrib that doesn't exist: {Hansen8.Blah}

     

    </p><p>SerialNo: {Hansen8.SerialNo}

     

    </p>

     

    And for the Feature Long Description:

    <p>COMPKEY: {Hansen8.COMPKEY}

     

    </p><p>Type Description: {Hansen8.TypeDescript}

     

    </p><p>Another attrib that doesn't exist: {Hansen8.Blah}

     

    </p><p>SerialNo: {Hansen8.SerialNo}

     

    </p><p>The label field = {Hansen8.Label}</p>

     

    And here is the Attributes tab where these Datalink items are showing due to the Datalink being configured as a 1:1 link.

    /customer/servlet/servlet.FileDownload?file=00P6000000e88VWEAY

    If if export that Feature to  CSV I get a zip file with two csv files, one for the features (WSMeter)  and one for the Hansen8 Datalink:

    Here is the contents of the WSMeter.csv:

    Component Key,Component Type,Unit ID,Unit Type,DateStart,DateEnd

     

    200161,42,WM157321,INLINE,,

     

    And the contents of the Hansen8.csv:

    COMPKEY,Supply,PressZone,MapNumber,AsBuilt,Status,InstallYear,AddInfo,Address,Owner,METERSZ,Manufacturer,MODELNO,SerialNo,Comments,UNITID,UNITTYPE,TypeDescript,ACCTNO,SL_UNITID,Label,LDZone,LEGACYAPPLICATION,APPLICATION

     

    200161,EA,,U16-1000/56.08,,IN,2008,VINTAGE CAR CLUB AT NEIL HUNT PARK,"  TE NGAE RD LYNMORE, ROTORUA",ROTORUA DISTRICT COUNCIL,20,KENT,PSM,07A140344,,WM157321,INLINE,IN LINE METER,,WL020140,20mm KENT PSM INLINE,,E1928,

    If I check the site REST endpoint for the datalink using http://serverName/Geocortex/Essentials/REST/sites/DataLinkTesting/map/mapservices/1/layers/2/datalinks/Hansen8/link?maxRecords=&pff_COMPKEY=200161&f=pjson

    I get this result:

    { "results" : [ { "index" : 0, "featureFieldParameters" : { "names" : [ "COMPKEY" ], "values" : [ "200161" ] }, "linkedData" : { "columns" : [ "COMPKEY", "Supply", "PressZone", "MapNumber", "AsBuilt", "Status", "InstallYear", "AddInfo", "Address", "Owner", "METERSZ", "Manufacturer", "MODELNO", "SerialNo", "Comments", "UNITID", "UNITTYPE", "TypeDescript", "ACCTNO", "SL_UNITID", "Label", "LDZone", "LEGACYAPPLICATION", "APPLICATION" ], "rows" : [ { "row" : [ 200161, "EA", null, "U16-1000/56.08", null, "IN", 2008, "VINTAGE CAR CLUB AT NEIL HUNT PARK", " TE NGAE RD LYNMORE, ROTORUA", "ROTORUA DISTRICT COUNCIL", 20, "KENT", "PSM", "07A140344", null, "WM157321", "INLINE", "IN LINE METER", null, "WL020140", "20mm KENT PSM INLINE", null, "E1928", null ] } ] } } ] }

     

    If I add {Hansen8.Label} to the Feature Description definition as follows:

    <p>COMPKEY: {Hansen8.COMPKEY}

     

    </p><p>Type Description: {Hansen8.TypeDescript}

     

    </p><p>Another attrib that doesn't exist: {Hansen8.Blah}

     

    </p><p>SerialNo: {Hansen8.SerialNo}

     

    </p><p>The label field: {Hansen8.Label}</p>

    Then that causes the Feature Desciption to be blank in the SL Viewer

    There are other anomalies occuring when creating hyperlink in the descriptions as well that may be related. To save confusion I won't attempt to describe those as yet.

    Looking forward to hearing any suggestions

    Thanks

    Ralph

     

     

    0
  • Cattyann Campbell

    Hi had some weird funky stuff happen with map tips

     

    that used to work before the upgrade...

    it seemsed to center around hyperlinks and formatting (bold, colors...)

    Somehow I got the thing to work after trying every combo I could think of.

    It worked just fine Html viewer but not SL viewer.

    0

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