Environment:
- ArcGIS Pro 3.5.4
- Windows 11 Enterprise 23H2
- ArcGIS Enterprise 11.5
- Data Source: File Geodatabase
Issue Description:
We are experiencing inconsistent query results when publishing a layer from ArcGIS Pro to our Enterprise Portal as a hosted feature layer.
In ArcGIS Pro, we apply the following Query Definition to a layer stored in a file geodatabase:
(code1 IS NULL OR code1 = '' OR code1 = 'Y') AND date >= timestamp '2023-01-01 00:00:00.000'
This returns approximately 37,000 features as expected.
However, after publishing this layer to the Enterprise Portal as a hosted feature layer, we observe the following issues:
- The hosted feature layer returns only 290 features.
- Applying the same filter manually (without using Query Definitions) on the hosted feature layer in the Portal also returns only 290 features.
- Creating a View Layer from the hosted feature layer and applying the same filter again results in 290 features.
- Using an Arcade expression in a Dashboard referencing this layer also returns 290 features.
- If we filter only by code1 = 'Y', the result is correct.
- If we filter only by date >= timestamp '2023-01-01 00:00:00.000', the result is also correct.
This leads us to believe that the issue lies in how code1 IS NULL OR code1 = '' is being interpreted or handled when the layer is published to the Enterprise Portal.
It seems that null or empty string filters are not being correctly transferred or respected in the hosted feature layer environment. Unfortunately, even when we try to apply these filters directly in the Portal (outside of ArcGIS Pro), the results are still incorrect.
Additionally, hosted feature layer published with 8000 or 32000 maximum return count, and it didn't change anything.
Has anyone else encountered this issue?
Is there a known limitation or workaround for handling NULL or empty string values in hosted feature layers or view layers in ArcGIS Enterprise?
Any insights or suggestions would be greatly appreciated.
Thanks in advance!
