When reading a Utility Network feature service on ArcGIS Enterprise from FeatureReader using the Esri ArcGIS Feature Service format, only 2000 rows are returned. No errors are shown in the translation log (scrubbed and attached, using package version 3.25.4). There are no AGS Log entries to indicate an issue on our side.Β
This issue was not present with package versions 3.22.0 and 3.25.1Β
Upgrade within FME Form: You can update the package directly within FME Workbench via FME Options > FME Packages (or by adding the updated reader to your canvas).
This matches a known issue we're tracking (FMEENGINE-99411).
The line that shows it:
ArcGISFeatureServiceReader: Reading 2000 features in 2 batches of up to 1000 features
The reader works out the total first by asking the service for object IDs, then pages through them. In 3.25.3 it started sending resultRecordCount on that ID request. Some services cap the response at the layer's maxRecordCount and don't return exceededTransferLimit to flag that more exist. So the reader gets 2000 IDs and nothing telling it otherwise. It reads those 2000 and stops. That's why there's no error; it thinks it read the whole layer. 3.25.1 didn't send that parameter, so it worked.
Can you check maxRecordCount on the Pipeline Device layer and tell me whether it's 2000? That would confirm it.
Rolling back to 3.25.1 should get all your rows reading again in the meantime. Raising maxRecordCount above the layer's feature count may also work, though that's a server-side change your ArcGIS admin would need to make.
Our development team is aware of the problem and will investigate it further. We appreciate your patience in the meantime while they look into this. I'll update this thread as I hear more.
I can confirm my team is impacted by this issue too where the βMaximum Number of Records Returned by Serverβ parameter in ArcGIS server is returned.Β Β using arcgis feature serviceΒ 3.25.5 on enterprise services 11.3
Going to fme hub Rolling back to 3.20.1 resolved the issue.
Hey β@phil.l.avistaΒ Thanks for confirming - that does indeed confirm this aligns. And youβre correct; this issue hasnβt (yet!) been listed in our Known Issues. It seems, based on β@grahamwood_hwcΒ and othersβ experience encountering it, to be affecting numerous customers. Iβll discuss internally adding it.
Upgrade within FME Form: You can update the package directly within FME Workbench via FME Options > FME Packages (or by adding the updated reader to your canvas).
