data connections on Map Tip
Hi, is there a way to get items from data connection SQL query to display directly within the map tip:
My data connection SQL query is this:
SELECT TaxAccountNumber,ProjectFileNumber,PermitType,PermitDescription,FolderDescription AS 'ProjectDescription',GroupType AS 'Type',Status,IssueDate,ExpiryDate AS 'ExpirationDate',ApplicantName,ApplicantOrganization,PDSContactName AS 'PDSProjectManager',PDSContactPhone AS 'PMphone',PDSContactEmail AS 'PMemail',SiteAddress AS 'SiteAddress',SiteCity AS 'City',SiteState AS 'State',SitePostal AS 'ZipCode'
FROM SCD_Amanda_TEST.dbo.SNOCO_QUERY_ALL
WHERE TaxAccountNumber = @ParcelID
Do i need to accomplish this through the creation of a workflow or can i workaround this in just HTML ? Any insight is appreciated.
0
-
You can include information from a one to one data link in your map tip. The syntax to call a data link field is {DataLinkID.FieldName}. 0 -
John, 0 -
You can put a link in your map tip to open the feature details window, which is where people can view one to many data link results. But it pretty much just does the same thing as the default view additional details map tip action. 0 -
John, 0 -
John, disregard the request for the count features option. I was able to get it work for my purposes(see below): 0 -
According to the API reference for the GVH, ShowFeatureDetails accepts either a feature or a feature set as a command parameter, not a data link ID. 0 -
John, 0 -
My guess is they're just opening the feature details and have their viewer set up to show the data links first. 0 -
John, 0 -
There are two things you need to do to mimic the behavior of the Kirkland viewer. { "moduleName": "FeatureDetails", "moduleType": "geocortex.essentialsHtmlViewer.mapping.modules.FeatureDetails.FeatureDetailsModule", "configuration": { "defaultViewMode": "expanded", "viewModes": { "compact": { "viewId": "FeatureDetailsCompactView", "defaultProviderTargetRegion": "FeatureDetailsCompactViewRegion" }, "expanded": { "viewId": "FeatureDetailsExpandedView", "defaultProviderTargetRegion": "FeatureDetailsBottomRegion" }
0 -
Nothing about the configuration about Provider location? I thought that was a part of this component in the past? I swore that is what you said before. 0 -
I didn't understand that last one, can you reword it? 0 -
I thought the work around i would need for my issue is very similar to the fix you brought up yourself back on June 18 2015, 0 -
For anyone else reading this thread, here the link to the post Raoul is talking about: "viewModels": [ { "id": "FeatureDetailsExpandedViewModel", "type": "geocortex.essentialsHtmlViewer.mapping.modules.FeatureDetails.FeatureDetailsViewModel", "configuration": { "defaultTabViewForLayer": { "FeatureDataLinksProviderView": "default" },
0 -
So I just copied this in and here is my version of how it looks in my viewer: "viewModels": [ { "id": "FeatureDetailsExpandedViewModel", "type": "geocortex.essentialsHtmlViewer.mapping.modules.FeatureDetails.FeatureDetailsViewModel", "configuration": { "defaultTabViewForLayer": { "FeatureDataLinksProviderView": "default" },
0 -
I tested and can confirm that these config changes do NOT work at version 4.4. I had tested these changes using 4.5 and 4.6, and they work there (100% sure on 4.6, 90% sure of 4.5). 0 -
John, 0 -
I don't remember how I found it, but usually when I'm looking to change something I just dive into the viewer config file (practice makes perfect). In that case I probably just did a Find for FeatureDetails and looked at the different lines until I found something that looked promising. 0 -
Unfortuantely RelatedFeaturesView, RelatedFeaturesProviderView, RelatedFeatureViewModel, RelatedFeaturesTableView, and FeaturesRelatedView did not work. Any further ideas? 0 -
I ended up setting up DataLinks and achieving this same thing. Is there any way to force the data links tab to show even if there are no related records? Or is there a way to configure the map tip to show the hyperlink if and only if there are related records? 0 -
For showing a hyperlink when there are no related records, you could try something similar to the method using LEFT OUTER JOIN in this post: 0 -
Using GE4.10.2 and GVH2.11.2 0
Please sign in to leave a comment.
Comments
22 comments