Skip to main content
  • EN

We have multiple workspaces that write to ArcGIS Online with multipart geometries. The old ARCGISONLINEFEATURES writer works and correctly writes the geometries. The new (2025) Esri ArcGIS Feature Service Writer returns an error rejecting the features and the following warning:
ArcGISFeatureServiceWriter: INSERT error for a feature in Project Stats by State. The error code from the server was '1000' and the message was 'Adding/updating geometries that result in SQL GeometryCollections is currently not supported (SQL Server performance).'
 

Using a Deaggregator seems to fix this in most cases. However, we want to retain the multipart geometries. In other cases, I see a similar warning and the following error after using a Deaggregator:
ArcGISFeatureServiceWriter: INSERT error for a feature in Terracon Offices Closest Areas. The error code from the server was '1000' and the message was 'Data is Null. This method or property cannot be called on Null values.'
 

I’ve tried a NullAttributeMapper and only writing a single column that I know has 0 NULLs and see the same error and warning. Has anyone ran into these issues with the new writer? If so, have you found a workaround?

Hi ​@paul_m,

 

This sounds similar to an issue we’re tracking internally as FMEENGINE-88156. If you can please submit a ticket so that our Support team can look into this further, that would be great!

We’ll be able to better assist you with more information. When submitting your ticket, please provide the following (if available/possible):

  • Details about the environment used (e.g. platform and OS version, FME Form version, any other dependencies, etc.)
  • Please provide a sample of the source data used in your workspace
  • The workspace (or sample workspace) that you are encountering issues with. Please be sure to include any required data or custom transformers needed. If, possible please send this as a template (.fmwt).

In the meantime, could you try changing the following parameter in the writer and seeing if that fixes the errors?

  • Use True Curves > No

Hi ​@paul_m,

 

This sounds similar to an issue we’re tracking internally as FMEENGINE-88156. If you can please submit a ticket so that our Support team can look into this further, that would be great!

We’ll be able to better assist you with more information. When submitting your ticket, please provide the following (if available/possible):

  • Details about the environment used (e.g. platform and OS version, FME Form version, any other dependencies, etc.)
  • Please provide a sample of the source data used in your workspace
  • The workspace (or sample workspace) that you are encountering issues with. Please be sure to include any required data or custom transformers needed. If, possible please send this as a template (.fmwt).

In the meantime, could you try changing the following parameter in the writer and seeing if that fixes the errors?

  • Use True Curves > No

Thanks for all the info! I’ll submit a ticket. I did set True Curves to No, and the data wrote without errors, but the result is very wrong (see below). When writing the same exact data with the old ArcGIS Online writer, everything shows up in the right place with no errors.

 

Community Stats

31,922
Posts
121,242
Replies
39,545
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.