Hi @philipwhitten​, FME should automatically read in the GlobalIDs without brackets or changes in letter case. I'd suggest taking a look at this article from Esri regarding preserving Global IDs, and you can also try using the ArcGIS Portal Feature Service Writer at the end which will preserve the GlobalIDs in lowercase and without curly brackets when you write back up to Portal. You'll have to enable this in the writer parameters under Advanced >Use Global IDs. I hope this helps!

Hello @saraatsafe​. I am using FME Workbench 2023.0. From my testing, FME changes the case and adds curly brackets to Global IDs that are lower case and do not have curly brackets. When I use a a where filter in the ArcGIS Portal Fortal Service Reader to only read features with Global ID's that don't have curly brackets I can then use RegEx to remove the curly brackets added by FME and change the case to lower case and at the end of the workspace the ArcGIS Portal Feature Service Writer works as it is intended. I could try creating a public Portal Rest Service if you would like to test this behaviour - but - I don't think FME is automatically GlobailIDs without adding brackets and changing case of the letters.

Hi @philipwhitten​, yes if you could provide us with a Portal Rest Service for us to test, that would be great. We'd like to try and reproduce the issue you're seeing and confirm whether or not it's an issue on the FME side or elsewhere.

Hello @saraatsafe​ , could you try using this Feature Service https://portal.data.nsw.gov.au/arcgis/rest/services/Hosted/fme_gobalid_test_public/FeatureServer/ combined with the Esri ArcGIS Server Feature Service Reader? You should hopefully see the same issue.

Also, you can use the following query to inspect the different GlobalID formats: https://portal.data.nsw.gov.au/arcgis/rest/services/Hosted/fme_gobalid_test_public/FeatureServer/0/query?where=1%3D1&objectIds=&time=&geometry=&geometryType=esriGeometryEnvelope&inSR=&spatialRel=esriSpatialRelIntersects&distance=&units=esriSRUnit_Foot&relationParam=&outFields=*&returnGeometry=true&maxAllowableOffset=&geometryPrecision=&outSR=&havingClause=&gdbVersion=&historicMoment=&returnDistinctValues=false&returnIdsOnly=false&returnCountOnly=false&returnExtentOnly=false&orderByFields=&groupByFieldsForStatistics=&outStatistics=&returnZ=false&returnM=false&multipatchOption=xyFootprint&resultOffset=&resultRecordCount=&returnTrueCurves=false&returnCentroid=false&sqlFormat=none&resultType=&datumTransformation=&f=html

Hi @philipwhitten​, apologies for the late reply here. I've had a chance to speak with other experts and devs, and since globalID formatting is inconsistent across Esri's products, we had configured the reader to try and correct for it, hence the upper-case and curly brackets... apologies for any confusion on this previously. When you use the ArcGIS Portal Feature Service Writer at the end, do you have any issues with the globalID then? If so, then that's a bug and I can file a ticket for it. Let me know if you have any questions!

Hello @saraatsafe​ , I can confirm that if you use the ArcGIS Portal Feature Service Writer and an ArcGIS Protal Feature Server Reader in the same workspace with no other action than an UPDATE using the Global ID then you do get an error. These errors were the reason we became aware of the different Globail ID formatting. So I think it is a bug from your description.

I haven't worked out why FME with the ArcGIS Portal Feater Service Writer sometimes writes Global ID's with different formatting when doing INSERT but that is another challenge, and probably the root problem that triggered this problem.

Hi @philipwhitten​, can you clarify what error you get? I ran into this error when I tried to UPDATE the feature service on Portal:

ArcGIS Portal Feature Service Writer: Cannot create or overwrite Feature Service 'PointLayer' because feature type 'Layer1' is set to 'UPDATE' mode. All feature types must be in INSERT mode and not set to Truncate

However, when I have the writer set to INSERT and remove the ObjectID from the writer's User Attributes tab, it works and new data is written up.

Would you be able to clarify and perhaps share your workspace? I can take a look at your transformers and parameters to see if anything's off.

Hello @saraatsafe​ . The error that I get is:

ArcGIS Portal Feature Service Writer: 'updateResults' error for a feature in 'Layer Name'. The error code from the server was '10512' and the message was: 'Update for the object was not attempted. Object may not exist.'

Hello @saraatsafe​ . I have attached a workspace that has a bookmark with contents for giving the error or preventing the error. Please let me know if this is sufficient?

Hi @philipwhitten​, thank you for sending your workspace over! It does raise a few more questions and in the interest of efficiency, I'll be transitioning this over to a case. I've created it (C693609) and you should have received a notification in your email. I'll work with you there to coordinate a call so we can find out more.

Hello,

To prevent the Esri ArcGIS Portal Feature Service Reader from changing the case and adding curly brackets to GlobalID values, try adjusting reader parameters related to formatting. If unsuccessful, use FME transformers to correct the format post-reading. Check Esri support and Portal settings, inspect data sources, and explore alternative workflows. Review Esri documentation for specific recommendations. Test changes in a controlled environment to avoid unintended consequences.

I hope this will help you.

Regards

Riya Singh(Devops training)

Hello riy02, Which reader parameters relate to formatting? Could you be explicit please? I am unable to identify any relevant reader paramenters and am not sure whether your answer actually addresses my question?