Symbolising date ranges capped at 100,000?

map16jamie

//areas which are surveyed 30 days ago or less belong in the first group
if (DateDiff(Now(), Date($feature.CreationDate), 'months') <= 😎 {
return "Surveyed within the last 8 months" }
//areas which are surveyed more than 30 days but less than 100 days ago belong in the second group
else if (DateDiff(Now(), Date($feature.CreationDate), 'months') > 8 &&
DateDiff(Now(), Date($feature.CreationDate), 'months') < 10) {
return "Surveyed between 8 to 10 months ago" }

else if (DateDiff(Now(), Date($feature.CreationDate), 'months') > 10 &&
DateDiff(Now(), Date($feature.CreationDate), 'months') < 12) {
return "Surveyed between 10 to 12 months ago" }
//areas which do not satisfy any of the given conditions belong in the fourth group
else {
return "None of these Date Ranges" }

 

I'm using the above expression to symbolise on inspections, however I am noticing this seems to cap at 100,000 inspections when in the layer there is around 300,000.

Has anyone else encountered this and if so is there a work around or is this just how it is?

 

Thank you for any contributions

Roquinn

I have ran into a similar issue before. I was using Dashboards to filter a list and it was limiting the returns. I used AGO Assistant to go into the JSON and modify the max return number. Not sure if you are trying to use in WebMap, App, Dashboards, etc., but here is what I modified: 

 (Which could be different on your Portal Item depending on your platform. Not sure if it will be the same or not.)

Disclaimer: I recommend saving a copy and modifying the JSON of the copy to prevent any errors in your production Portal Item. Also, something to keep in mind is the more items you load you could experience performance issues displaying the data. Food for thought...