Zum Hauptinhalt gehen

Linked data visibility (GE3.10 / SL1.6)

Permanently deleted user

Hi to all

there appears to be an issue where a DataLink against a Layer is configured to be NOT Visible (unchecked) with the data no longer being available via the Viewer syntax of {DatalinkName.FieldName}

I would like the Tab to be hidden/invisible but still have the data available via the above syntax. I have not tested with a workflow as to whether it is still available.

This would appear to be an issue with the 1.6 Viewer. (SL1.5.2 ignored that setting)

Thanks

Ralph Price

0

Kommentare

5 Kommentare

Datum Stimmen
  • Permanently deleted user

    Hi to all

    just a bump to this to see if I can get any reaction prior to logging a bug in the SL1.6 release.

    Anyone who would like to tidy up their linked data tabs would like the Visible checkbox to working correctly ie hide the tab but still make the data available.

    Regards

    Ralph Price

    0
  • Ryan Cooney

    Hi Ralph,

    The Visible property of a DataLink to governs whether that DataLink's data should be displayed anywhere to the end user. This means it applies to more than just the specific Tab in the Feature Details view. It also includes/excludes the data from FeatureLabel, FeatureDescription, FeatureLongDescription and FeatureHyperlinks.

    The use case we were intending to address with the Visible property was to support DataLinks that are only used for server-side reports, workflows or custom modules. In these cases the data is not for display in the UI so we don't need to query for it. This gives us better performance and hides irrelevant stuff from the various results views.

    Relationships, Reports and Print Templates have Visible properties that work the same way. The objects exist, but the viewer doesn't exercise them.

    --Ryan

    0
  • Permanently deleted user

    Hi Ryan

    thanks for the clarification.

    An example of where I would apply it is where:

    The end user doesn't really need the frontageLink to be visible as a tab but they do need to have the data coming from that datalink for the above link to Google Street View to work.

    Note that I have also used this technique for address points that have got the Parcel-Id as an attribute as well.

    Have you got any idea as to how I would achieve these aims?

    Thanks

    Ralph Price

    0
  • Permanently deleted user

    Hi Ralph,

    While you can't easily hide the frontage from the user, you can make it a lot less intrusive by configuring your data link to be a 1-1 relationship rather than a 1-many.  This is just an option in the configuration page for the data link itself.  In this case you'll get a couple of extra attributes for the parcel in the Attributes tab (one for Lat, one for Long, plus one for any others you're pulling from the data source) but there will be no tab dedicated to the frontage link itself.  I expect from your use case that the relationship is indeed 1-1 so this may work for you.

    John

    0
  • Permanently deleted user

    Hi John

    that works well enough for the case in point. I assume that where there is more that one matched result ie the property is a corner property and has frontages onto two road then it would be the first of the results that would get added to the feature attributes tab.

    Thanks

    Ralph

    0

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

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post