Map Tips & Details
Hello Everyone,
In the processing of updating to Essentials 3.15 and silverlight 1.10 some of my map tips have stopped working? I tried deleting the descriptions and adding them again, but they are still not displaying? Any ideas on how to make my map tips work?
Jacqueline
-
Hi Jacqueline 0 -
Ralph,
Thanks for getting back to me! Here is what I have in the feature discription:
<div style="text-align: center;"><span style="font-weight: bold;">TIN:</span> {TIN}<br/><span style="font-weight: bold;">PIN:</span> {PIN}<br/><span style="font-weight: bold;">Current Owner:</span> {Owner}<br/><span style="font-weight: bold;">Lot Number</span>: {Lot}<br/><span style="font-weight: bold;">Legal Acreage:</span> {Acreage}</div>
The information is being pulled directly off the feature class/service. I know you had mentioned you were having problem with a datalink breaking things.
On a sidenote... The same feature description is working perfetly in the HTML5 viewer?
Jacqueline
0 -
Hi Jacqueline
What happens if we make the toll tip really simple without any formatting:
<p>TIN: {TIN}</p><p>PIN: {PIN}</p><p>Current Owner: {Owner}</p><p>Lot Number {Lot}</p><p>Legal Acreage: {Acreage}</p>
I am trying to pin down whether it is something in the html formatting that it upsetting things.
In regards to your comment about my labels coming from datalinks it is just that most of the data is stored somewhere other than in the spatial data for most of my layers
Regards
Ralph
0 -
Hey Ralph,
Again thanks for helping me out with this issue. I have tried stripping out everything and the map tips seem to work property with only text entered. Once I enter a certin number of field tokens it breaks and nothing will display. I can enter some of the field tokens (for example TIN and PIN) and everything functions perfectly. But once I add additional tokens my map tips break. Also, it is not the same tokens that cause it to break each time... Adding more than 2 seems to cause problems.
I hope we can figure this out, because I really do not want to have to rebuild all my descriptions! Thanks again!!
Jacqueline
0 -
Hi Jacqueline
hopefully Ryan and Co are watching this thread
Regards
Ralph
0 -
Hey guys,
If you have an external site I could hit, I'd be happy to have a look at this for you. Feel free to email me a url - krintoul@latitudegeo.com
Cheers,
Kevin
0 -
This issue appears to be with SLV1.10. As mentioned, map tips work fine in the HTML5 viewer. I have the same configuration in SLV1.9 and it still works after upgrading to GXE3.15. I'm hoping latitude will offer a bug fix?
0 -
Hi Kevin 0 -
Our site is avaiable externally (GXE3.15 & SLV1.10):
http://maps.squamish.ca/PublicMaps/?Viewer=MapViewer
Map tip on t he P arcel lay er should appear as:
*Property 1
0 -
Hi Kevin
here is another site: http://geo.rdc.govt.nz/GSLV_EXT/Viewer.html?Viewer=GeyserView4&extent=19615950,-4590863,19615998,-4590832&layerTheme=Utlities and try an identify on the Water meter as indicated in the image below:
/customer/servlet/servlet.FileDownload?file=00P6000000e88VgEAI
Note that the additional details window is empty!
Here is the config for the Feature Description:
<p>COMPKEY: {Hansen8.COMPKEY}
And for the Feature Long Description:
<p>COMPKEY: {Hansen8.COMPKEY}
Note that the difference between the two is the last label field but which does show as seen in this image:
/customer/servlet/servlet.FileDownload?file=00P6000000e88VcEAI
Thanks
Ralph
0 -
Ralph and Dan,
Thank you for describing this issue fully! Hopefully, Latitudes will get back to us with a quick fix!
Jacqueline
0 -
Waiting to hear how this goes before upgrading.
0 -
I've rolled the viewer listed previously back to SLV1.9 until this is resolved. Any update from Latitude?
0 -
There is a bug in version 1.10 of the Silverlight Viewer where feature descriptions or feature long descriptions will not display if a field that is used has been configured to be NOT visible in the site.
Dan, it looks like this is true of the ROLL_COUNT field in your Parcel layer. Ralph, I'm not entirely sure in your case since all of the values are coming from the datalink, but I did notice that the regular Label field on your spatial layer is also set to be not visible, so maybe that is interfering?
Jaqueline, please check if this is true for your site as well.
I've added all of you to the list of affected users on this issue.
-Victoria
0 -
Thanks Victoria! Making ROLL_COUNT visible fixed the issue for me.
0 -
Something similar is happening with Feature Layers and attribute editing. I have a viewer (SL1.10) with in-place attribute editing enabled. The attributes are greyed out for editing, unless all the fields are made visible.
0 -
Victoria,
Thanks for getting back to us on this issue! Sorry its been a couple of days! So far this has sometimes fixed my issue. However, the fix is not consistant across site and the information in the map tips/details. Can you let me know if there is anything else I should try. I will keep looking into this in the morning!
Thanks again!
Jacqueline
0 -
Working with features and in-place attribute editing. I've tried turning off fields in ArcMap before publishing the service. The same issue occurs, where editable fields are greyed out.
0 -
Hi Victoria
just thought I would check to see if there was any progress on this or any suggestions from the dev team as to how we can help them resolve what is going on?
Thanks
Ralph
0 -
Hi Ralph,
My earlier suspician was correct. We've done some more testing and found that if you have a data link field with the same name as a field in your layer, and the field in your layer is not visible, the same issue will occur with the feature (long) description disappearing.
In your site, I suspect that making the Label field in your layer visible will cause your feature long description containing the {Hansen8.Label} datalink value to appear.
I've filed a separate bug for this issue.
-Victoria
0 -
Hi Victoria
yes that is indeed what is happening. It is a shame that the bug also prevents any of the other fields that do not have a visibility clash from showing as well.
At least the issue is clarified and a work around is available.
Looking forward to a bug fix
Thanks
Ralph
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
21 Kommentare