Esri feature service writer: every integer is written as 1 when inserting into an existing AGOL layer

Hi ​@bekir,

Please check the existing feature layer to see if there are any data ranges set on the integer attributes: https://doc.arcgis.com/en/arcgis-online/manage-data/define-attribute-lists-and-ranges.htm

Hi,

We experience the same issue here:

• Problem seems to occur since v3.25.1
• There are no data ranges set on the integer attributes

This is a very serious problem. Especially if you read data from a feature layer and write the data back to the same feature layer, you loose some of you own data.

thanks ​@daveatsafe didn't look at that one, but it's also empty.

the definition is:

    {
      "name" : "equipmentNr", 
      "type" : "esriFieldTypeInteger", 
      "alias" : "EquipmentNr", 
      "sqlType" : "sqlTypeOther", 
      "nullable" : true, 
      "editable" : true, 
      "domain" : null, 
      "defaultValue" : null
    }, 

Hi ​@bekir,

I have tried to reproduce the problem with my own layers, but with no success. Are you able to create a shareable layer that I can write to, or a detailed explanation on how to create a layer that will reproduce the problem?

Hi ​@daveatsafe,

I am creating an debug environment. Do you have an ArcGIS Online user I can share the feature layer with you. 

I will add an ffs and an fmw to here, after I’m done.

Here’s the ffs and fmw.

Hi ​@bekir ,

Thank you for that info! 

I was able to reproduce the problem by forcing the values to strings, and will create a problem report for our development team.

Thanks ​@daveatsafe - will start implementing this workaround to production now :)

The workaround is nice if you only have a few workbenches to change. But we have a lot of workbenches with this problem, so I want to try to revert to an older version of the package on FME Flow.

I followed the manual for removing the 3.25.1 package by manually removing the package from the Engine resource and sub resources as described in https://support.safe.com/hc/en-us/articles/25407389067021-FME-Flow-Troubleshooting-Packages

But when I try to upload a 3.22 version from FME Form to FME Flow I get the following error:
Upload 'safe.esri-agol-3.22.0.fpkg'...
Package access failed - FME Flow encountered an error and reported the following message.
Package safe.esri-agol may not be downgraded from 3.25.1 to 3.22.0.
Request to https://<our_server_url>/fmeapiv4/packages returned status code 422.
 

Also a restart of all the FME Flow services on the server does not help.

The manual upload of packages is not supported in FME Flow 2023.0 and above (that is why I did that via FME Form). But it seems that removing a package manually is also not supported anymore (or at least for this esri-agol package).

Does anybody know how to solve this issue?
How can I revert to an older version of the package on FME Flow?

There should be a manual to downgrade the package, but I cannot seem to find it quickly. However you could replace the package on the Engine folder on FME flow. That’s where the package lives.
If I encounter the manual tomorrow morning I will post it here too.

I entered a ticket at FME Support and got the following answer:

Are you able to access your Flow backend database (using something like pgAdmin 4)? If you connect to the database using your connection details located in the fmeDatabaseConfig.txt (<FlowFileShare>\FMEFlow\Server) for connection details) And go to Databases > fmeflow > Schemas >public > Tables >, and view the fme_package table. Do you see an esri-agol package in the table? If you can, try deleting that table, restarting FME Flow, and reuploading the older version of the package.

So the steps I followed are:

1. Remove the package file from the Engine resource
2. Remove the package files from the Engine sub resources
3. Remove the row for the package from the fme_package table in the FME Flow database
4. Restart the FME Flow services
5. Remove the package from FME Form via Utilities | FME Options | FME Packages
6. Install an older version of the package in FME Form by dragging the package file in FME Workbench.
7. Create a workbench using the package, and upload it to FME Flow.
8. Run the workbench on FME Flow, so the package gets extracted on FME Flow

I have no information yet on whether this can cause strange side effects and workbenches that are already referencing to a newer version, not working on FME Flow...