Displaying the identified results in GE 4.7\GVH 2.8 without grouping (as in GE 4.6\GVH 2.7.2)
Displaying the identified results in GE 4.7\GVH 2.8 without grouping (as in GE 4.6\GVH 2.7.2)
Showing values is much more important than showing the name of the layers. Grouped fashion requires you to expand each result individually to view the result information which is time consuming.
So, we are interested in displaying the identify results in GE 4.7\GVH 2.8 as it was in GE 4.6\GVH 2.7.2.
Is there a way to change this style, and have the same style as GE 4.6\GVH2.7.2? Why this option is noy optional?
_img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90660000000GtxD&feoid=Body&refid=0EM60000000UjVI" _/_img_
Thank You in advance
Beest,
Majdoleen
0
-
We finally found a solution for this by replacing these coded as shown in the screenshots:
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.ResultsListView",
"markup": "Mapping/infrastructure/results/ResultsListView.html",
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FlatResultsViewModel",
It works fine with me.
Best,
Majdoleen0 -
One more step is needed,
Replace “ FeatureSetCollectionResultsActions” by “ResultsListActions” as shown in ordet to keep the drop menu:
Thanks0 -
Here is a quick summary. You can change the values for the types and markup without having to delete parts of the group view. Thanks for sharing this Majdoleen Awadallah.
Step 1
Search for"id": "ResultsListView"
Change
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FeatureSetCollectionResultsView",
"markup": "Mapping/infrastructure/results/FeatureSetCollectionResultsView.html",
To
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.ResultsListView",
"markup": "Mapping/infrastructure/results/ResultsListView.html",
Step 2
Search for"id": "ResultsListViewModel"
Change
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FeatureSetCollectionResultsViewModel",
To
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FlatResultsViewModel",
Step 3
Search for"id": "FeatureSetCollectionResultsActions",
Change
"id": "FeatureSetCollectionResultsActions",
To
"id": "ResultsListActions",
0 -
i hope that this will be managed in the future releases at the level of manager without the need to play with the code 0 -
I have been waiting for a solution to this grouping that was introduced as it is definitely more time consuming and less efficient.
Thank you so much Majdoleen Awadallah for taking the time to provide a solution!
I really hope that LG will add this ability to group or ungroup results directly from the manager soon.0 -
Dear Brian,
I am very happy to hear that your issue has been resolved.
Best,
Majdoleen0 -
This doesn't work in 4.10 - is there another solution? Help! 0 -
Hi Cassandra,
I would double check your changes and carefully follow Tyson's steps. I just tried it in 4.10 / 2.11 and it worked as expected, after correcting an initial mistake I made.
Regards,
Wayne0 -
Based on information from the following help topic, setting the automaticDrillInDelay in the ResultsListView to 0 should make the results not be put into a summary panel - but it doesn't appear to be working. I also tried setting it to 10000 and same results.
https://docs.geocortex.com/essentials/gvh/latest/admin-help/Default.htm#gvh/admin/modules/results-module.htm
Is this a bug or just not work the way I think I'm understanding the description in the help?
- Cassandra0 -
I believe that setting is unrelated to the changes detailed in the post. The setting is applicable to a results list of only 1 feature set while this post details how to avoid grouping of multiple feature set results. What was your desired outcome?
Regards,
Wayne0 -
Hi, it is just a note as I am wondering if i am alone having trouble as these changes worked for GE 4.9 and HTML5 2.9 and prior releases, however they cause issues at GE 4.10 and HTML5 2.11.2 viewer. I have confirmed it with the support team that these changes cause duplicate results into the results pane through global search, which disappear upon clicking and moving back. I hope it helps for those planning an upgrade to 4.10.3 and viewer 2.11.2. 0 -
Hi, I would also very much like a solution for ungrouped results which works in 4.10.2. If I implement it, I get duplicate results after a global search. Has anyone a solution? Thanks in advance.
Regards,
Annet0 -
Hi All,
I also get duplicate results after a global search! I will try to find a solution fot this, and hope that one of Latitude Geographics support can confirm if this is a bug or not? In GE 4.7\GVH 2.8 this issue was not appeared.
Best
Majdoleen0 -
Hi All,
I got duplciate resuls as well. It was caused by the Step 2.
"type": "geocortex.essentialsHtmlViewer.mapping.infrastructure.results.FlatResultsViewModel",
don't know if this is a bug yet.0 -
Hi All,
We are disappointed that “ungrouping results” is not included as an option at the level of manager in the last release 4.12
Is there any chance to have this option included in the future release?0 -
Hi Majdoleen,
We are struggling with two issues when it comes to 4.12 release regarding the “ungrouping” code:- The result of the globally searched values is displayed twice
- The relate keeps the values of the first searched word (you need to refresh each time in order to get the correct relate for the searched values)
Best
Jamal0 -
Hi Eng.Jamal,
Kindly notes that the first issue (The result of the globally searched values is displayed twice_ is resolved using GE4.12 and GVH 4.12, I tried it from scratch on a local machine and it worked fine.
Regarding the second issue(The relate keeps the values of the first searched word (you need to refresh each time in order to get the correct relate for the searched values), this issue is not related to ungrouping, it is related to the code which expanded the result details by default, I think we need to edit the code which is written in my last comment here (https://support.geocortex.com/essentialsGSCForum?id=90660000000CjydAAC),
Any Idea regarding this?
Best
Majdoleen0 -
Hi again,
I actually ended up finding a quick work-around for the second issue with the expanded view, set the command to be the following and it works as expected.
"commands": [
"ShowFeatureDetailsExpanded",
"ShowFeatureDetails",
"ZoomToFeature"]
Best
Majdoleen0
Please sign in to leave a comment.
Comments
18 comments