Not sure if you are open to issues being reported here but trying out the group by example (ultimately I want to use this for a join), I can't view the results when querying a non-hosted feature layer, that is one in a Postgres enterprise geodatabase. The same expression against a hosted layer works fine.
I looked into the responses from the feature services and they are almost identical, but the hosted service returns a few more properties in the json response;
exceededTransferLimit,
globalIdFieldName,
objectIdFieldName.
Is there a limitation on using these arcade data expressions against non-hosted layers? Or is there a workaround/function I can enable on my services to support them?
Hi arcade team,
Not sure if you are open to issues being reported here but trying out the group by example (ultimately I want to use this for a join), I can't view the results when querying a non-hosted feature layer, that is one in a Postgres enterprise geodatabase. The same expression against a hosted layer works fine.
I looked into the responses from the feature services and they are almost identical, but the hosted service returns a few more properties in the json response;
exceededTransferLimit
,globalIdFieldName
,objectIdFieldName
.Is there a limitation on using these arcade data expressions against non-hosted layers? Or is there a workaround/function I can enable on my services to support them?
The expression based on the example;
The response from the non-hosted feature layer;
But this is rendered/returned to the dashboard without the statistics;