EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB47830: "queryTask error:TypeError:undefined" when executing a DHTML document set to display esriGeometryPoint areas in an ESRI Map in an on-premise configuration in MicroStrategy Web 9.4.1 HF5.


Community Admin

• Strategy


MicroStrategy Web 9.4.1 HF5 users can configure their ESRI Map on-premise deployment to display areas based on an attribute geo-maped in the esriConfig.xml. To view more details on this procedure refer to the GIS Integration Help that corresponds to the MicroStrategy version used. In this process, attributes can be mapped to different map layers that contain geometry information to display areas. The most commonly used geometry is esriGeometryPolygons. MicroStrategy Administrators might configure a layer with a different type of geometries and will see the following error when executing an ESRI Map configured to display areas of type esriGeometryPoint in a DHTML document: "queryTask error:TypeError:undefined"

SYMPTOM:
Strategy Web 9.4.1 HF5 users can configure their ESRI Map on-premise deployment to display areas based on an attribute geo-maped in the esriConfig.xml. To view more details on this procedure refer to the GIS Integration Help that corresponds to the Strategy version used.
 
In this process, attributes can be mapped to different map layers that contain geometry information to display areas. The most commonly used geometry is esriGeometryPolygons. Strategy Administrators might configure a layer with a different type of geometries and will see the following error when executing an ESRI Map configured to display areas of type esriGeometryPoint in a DHTML document:


"queryTask error:TypeError:undefined"

 
 

ka04W000000OaSjQAK_0EM440000002639.png

 
In some cases the Document in Flash Mode will show the correct markers as shown below:
 

ka04W000000OaSjQAK_0EM440000002635.png

 
 
Note: Since this type of geometry is not supported, as it will be explained below, it is not guaranteed that it will work in Flash Mode.
 
CAUSE:
This is working as designed, Strategy Web 9.4.1 HF5 does not support geometries of type esriGeometryPoint. The only certified geometry type is esriGeometryPolygon. Some other types of geometries may work with the existing version of Strategy, however, these will not be supported and may not work in the future. An enhancement request has been logged to support  geometries of type esriGeometryPoint.
 
To find the geometry type of the map layer used, access the map layer through a browser. Clicking on the link below will show an example:
http://services.arcgis.com/P3ePLMYs2RVChkJx/ArcGIS/rest/services/Customer_Information/FeatureServer/2
A field called Geometry type will contain the geometry information as shown below:
 

ka04W000000OaSjQAK_0EM440000002637.png

 
In this example, the geometry type shown above will not be supported in Strategy Web 9.4.1 HF5.
 
ACTION:
Contact Strategy Technical Support for an update on this enhancement request.
 
WORKAROUND:
Strategy Web administrators can do the following to display markers in an ESRI on-premise configuration:

  1. Use the latitude and longitude information available in the ESRI on-premise database and add it to the table schema of the existing Strategy Warehouse.
  2. Import the tables to the Strategy Project.
  3. Create an attribute with two attribute forms one for latitude and longitude.
  4. Update the schema and modify the esriConfig.xml accordingly as described in KB45324 "What are the prerequisites to use the ESRI Map Widget with the ESRI sample server in MicroStrategy Web 9.4.0 or earlier versions"
  5. Modify the document to display markers using the information added above. The map will now display the markers correctly.


KB47830


Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

November 23, 2018