Statistics Returns 0 for newly published referenced feature services

[hoelhaddouni]

Hello everyone, 

I am using Esri Dashboards to show some statistics, like the number of features in a layer (COUNT), and we use referenced feature services for that.

Recently, the COUNT returns 0 for referenced Feature Services published within the last few days, while it works correctly for older referenced services. The statistics also work correctly for hosted Feature Services.

The test :

I tested the same layers on Experience builder and still have the same issue. 

I also tested them on Map viwer by creating a chart, and it shows nothing.

On our REST, all services have the same configuration :

        - Supports addvanced query : True

        - Supports Statistics : True

The issue summary :

- We can't generate statistics on referenced Feature serviceces published in the last few days. 

- We can generate statistics on old referenced features services published last month.

- We can generate statistics with hosted feature services (new and old)

-We use Entreprise 11.3

Has anyone experienced a similar issue or have any suggestions on what could be causing this behavior?

Thank you for your help.

[GlenterpriseUK]

Hi @hoelhaddouni,

Is your Enterprise Geodatabase on SQL Server?

Regards,

Glen

[hoelhaddouni]

Hello, 

We use PostgreSQL 15.12.

Thank you

[GlenterpriseUK]

Hi @hoelhaddouni,

Have you applied any recent patch to your ArcGIS Enterprise deployment?

Regards,

Glen

[GlenterpriseUK]

Hi @hoelhaddouni,

I have not been able to reproduce the issue. I tried with all data types (polygon, line, point) in a Postgres 15.5 Enterprise Geodatabase.

Might be worth doing an investigation if you had any recent patching done.

Regards,

Glen

[hoelhaddouni · Accepted solution]

Hello @GlenterpriseUK   ,

It turned out that the problem was with some of the newly published referenced Feature Services.

We deleted the affected layers from the database and recreated them. Then republished the servecies. The statistics worked correctly. 

We don't know why those particular services were affected, as they appeared to have the same configuration as the others. However, recreating the services from the database resolved the issue.

Thank you very much for your suggestions 🙂