Skip to main content
Question

ArcGIS portal feature writer fails to fill certain fields when run on FME Flow

  • October 15, 2024
  • 3 replies
  • 57 views

mgrupp
Participant
Forum|alt.badge.img+4

Hi everyone,

I have a problem that I can't seem to solve. I have a workspace that writes data from a PostGIS database to a feature layer on our portal using the ArcGIS portal writer. When this workspace is run locally on FME form, it works perfectly fine. When it is uploaded to portal and run there, it seems to work fine (the amount of features written is identical to the amount when run locally), but some important fields are not filled. Flow and Form both use the same web connection with the same authorization parameters. Why is it that a identical workspace that runs locally can fill all fields fine, but when run on portal it seems to not be able to fill these fields??? I have put testfilters and loggers in between to check if the fields actually have values and they do, so it must be a writer quirk. Field names between the features and writer are identical as well (all lowercase) so I am at a loss...

 

I am using fme form/flow 2023.2.2 and ArcGIS portal 11.1

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+54

Hard to say without data. No wornings in the logs? I never use this writer but I often read that it is very sensitive for schema differences. Maybe specific field types? Dates?


mgrupp
Participant
Forum|alt.badge.img+4
  • Author
  • Participant
  • October 15, 2024

 

nielsgerrits wrote:

Hard to say without data. No wornings in the logs? I never use this writer but I often read that it is very sensitive for schema differences. Maybe specific field types? Dates?

 

Thanks for your response! The logs give no warnings suggesting something might be wrong. I thought about the vartypes too, but vartypes for the problem variables are identical as well (varchar(20) in fme, string(20) in the portal writer).

 


artw
Participant
Forum|alt.badge.img+1
  • Participant
  • May 2, 2025

Just came across the same, hope you found the problem!
Try adding a BulkAttributeRenamer, and change all fieldnames to lowercase before writing to Portal


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings