Skip to main content
Question

ArcGIS Portal Web Connection as Published Parameter

  • May 2, 2025
  • 1 reply
  • 40 views

koen
Contributor
Forum|alt.badge.img+10
  • Contributor

I am trying to read/write from ArcGIS Portal in FME Flow with a parameterized Web Connection, but am not able to select a connection in FME Flow.

 

I used these steps to set everything up succesfully: https://support.safe.com/hc/en-us/articles/25407772142733-How-to-Create-an-ArcGIS-Enterprise-Portal-Web-Connection-OAuth-2-0

 

✅ FME Form 

I created:

  • a webservice named 'Esri ArcGIS Portal MyCompany’
  • several web connecions: ‘user1 Esri ArcGIS Portal MyCompany’, ‘user2 Esri ArcGIS Portal MyCompany’

This works fine in FME Form and I can read from ArcGIS Portal.

 

✅ FME Flow

I published these service, connections and workspace to FME Flow as described, and this runs fine as well. As long as the connection is hardcoded in the workspace.

 

❌ FME Flow with Portal Connection Parameter

Now I want to create a parameter for this connection, so I can choose in FME Flow which connection to use, but that doesn't seem to work.

When creating the parameter the only supported service is 'Esri ArcGIS Portal (Template)’, not my own service 'Esri ArcGIS Portal MyCompany’

 

When I publish the workspace to FME Flow and try to run it I am not able to select any of my ArcGIS Portal connections:

 

How can I fix this?

 

Environment details:

  • FME 2024.2
  • ArcGIS Enterprise 11.4

1 reply

ebygomm
Influencer
Forum|alt.badge.img+39
  • Influencer
  • May 2, 2025

It might be an issue, I reported this in 2024.1

 

FME Flow Web Connection parameters not using Configuration | Community

 

I was told that this was fixed in 2024.2 however I then also got this message which I could be what you are seeing.

The supported service filter problem was solved in 2024.2. However, there's another bug related to the OAuth2 web connection in user parameters, like ArcGIS Online. This means the "supported service filter" feature in the user parameter is not fully fixed, and the development team plans to fix it in 2025.x. 


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