Release notes for 4.1

September 2016

Support for MapImageLayer dynamic sublayers

We added support for dynamic sublayers in MapImageLayer. Developers can now create DynamicMapLayers and DynamicDataLayers as sublayers in the MapImageLayer. Users can create multiple DynamicMapLayers that point to a single map service sublayer and apply different rendering and labeling rules to each sublayer, though it points to the same service layer. You can also create DynamicDataLayers generated from data stored in registered workspaces, including service sublayers joined to non-spatial tables. Dynamic sublayers are created in the source property of the sublayer.

The image below links to a new sample demonstrating how multiple dynamic map sublayers may be created from a single service sublayer.


The new Sublayer class was added to provide a simple interface for creating these dynamic layer types. It can be used to directly make dynamic changes to certain properties of the service sublayer, including popupTemplates, renderers, labelingInfo, minScale, and maxScale. They may also be queried.

You can dynamically change the renderer of a sublayer, for example, by simply setting a new renderer object on the sublayer.

Use dark colors for code blocksCopy
var layer = new MapImageLayer({
  url: "",
  sublayers: [
      id: 0,
      renderer: new SimpleRenderer({
        symbol: new SimpleMarkerSymbol({
          color: "black",
          size: 8

Once set, the map service will send a new export request and display the updated image to the client. This sample demonstrates how to define dynamic labels on sublayers.

Sublayers are set on the sublayers property of the MapImageLayer. This property is now a Collection of the new Sublayer class. This is a breaking change from version 4.0. Other updates to MapImageLayer are listed below.

  • Sublayers now render in the same order that a map's layers are rendered in the view.
  • Since the sublayers property is a collection, sublayers may now be added, removed, or reordered from the MapImageLayer using the Collection API.
  • The createServiceSublayers() method was added to the MapImageLayer to allow developers to get all map service sublayers as defined by the service.

New dynamic layer samples


The IntegratedMeshLayer is designed for visualizing detailed 3D representations of both infrastructure and natural landscapes in a single layer. This creates a much more realistic scene, especially for landscapes with a lot of vertical drops such as canyons and buildings.


Integrated mesh data is typically captured by an automated process for constructing 3D objects from large sets of overlapping imagery. The result integrates the original input image as a textured mesh using a triangular interlaced structure. An integrated mesh can represent built and natural 3D features, such as building walls, trees, valleys, and cliffs, with realistic textures. Integrated mesh scene layers are generally created for citywide 3D mapping and can be created using Drone2Map for ArcGIS, which can then be shared to ArcGIS for Desktop or web apps.

Create custom popup actions per feature

Popups now have the ability to work with custom popup actions based on feature attributes. This can be useful if you wish to display information that is relevant for specific feature values. Please see the sample, Custom popup actions per feature to get a better idea how this works.

Default icon for popup action button

Popup action buttons now come with a default icon default icon if no image or classname is specified in the action object.

Default popup action icon

API updates and enhancements

Upgrade notes

Bug fixes and enhancements

  • BUG-000097752: Added support for map wraparound.
  • BUG-000097185: Extend the SceneView WebGL engine sample now works with IE11.
  • BUG-000097480: Added FeatureSet.fields property.
  • BUG-000097341: Added support for popups on webmaps using MapImageLayer layer types.
  • BUG-000097737: Fixed an issue where a feature layer's visibility could not be toggled if its initial visibility was set to false.
  • BUG-000096047: Graphic circles symbolized with simple fill symbols in SceneView now display properly when created counter-clockwise. Prior to this, it displayed hollow.
  • ENH-000096931: Fixed issue with Identity Manager's OK button displaying incorrectly in Japanese locale.
  • Fixed an issue where the BasemapToggle widget did not include a thumbnail for streets-navigation-vector

Additional packages

Version 4.1 of the ArcGIS Maps SDK for JavaScript uses Dojo 1.11.2 (updated from 1.10.4), dgrid version 1.1.0 (updated from 1.0.0), and dstore version 1.1.1.

How to access the SDK

  • The API library is available on both CDN and npm, Read more at Get started.
  • For supported versions, you can also download both the documentation and the API library. These downloads are typically available 3-4 weeks after release.

Previous releases

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.