Graphics layer item limit /rendering problem in api version > 4.12

5384
12
Jump to solution
12-30-2019 07:36 AM
NettaBeninson
New Contributor III

Hi,

We are using graphics layers for many purposes.

When we checked v4.13, some layers appeared partially.

This happened only in big datasets.

My temp solution was to use featureLayer, and yet - it happened again in another part of our system.

I took the basic graphics example and managed to catch the point when the problem starts => more than 2205 graphic items.

I've created a simple codepen - https://codepen.io/nettaben/pen/QWwqbjy 

Change  `maxItemsV413` to 2204 to 'view' the markers ==> stops working when the number is greater.

If the api version is set to 4.12 - it is possible see more than 2205 points, while in v4.13 - it is not possible.

(change in the example).

UPDATE: not working with 4.14 as well.

Attached pic - our system partial view  

Codepen:#

12 Replies
NettaBeninson
New Contributor III

Thanks - It's not always easy to recreate such 'edgy' behaviors  

0 Kudos
UndralBatsukh
Esri Regular Contributor

Hi there, 

I want to give you a quick update on the status of this issue.  When the number of graphics is high (just short of 5K in this case), dojo promises are failing at 4.14.  The team exploring options to move away from the current approach to improve overall performance when working with large numbers of graphics in a graphics layer.

As a workaround for this issue at 4.14, you can use the native promises shown below or please check out the test app here

<script>
var dojoConfig = {
  async: true,
  isDebug: false,
  has: {
    "esri-native-promise": true
  }
};
</script>‍‍‍‍‍‍‍‍‍

Thank you,

-Undral

UndralBatsukh
Esri Regular Contributor

Hi there, 

I want to let you know that this issue is fixed at 4.15. You can test the fix for the issue with the next version. Please let me know if you run into problems. Please use this test app to check the fix.

Thanks,

-Undral