Safe recommend using the same Form and Flow version. Try the same from Form 2025.0.1 and take note of the Python compatibility setting under the Navigator > Workspace Parameters

If the problem persists, you may wish to lodge this to their support page, sign in https://support.safe.com/hc/en-us/requests/new referring to https://support.safe.com/s/article/How-to-Create-a-Great-FME-Desktop-Support-Case

Cheers,

I’ve aligned the versions between form and flow, but the same issue as in the original post persists.

Does anyone have any ideas?

Hello, ​@ecx.

Thanks for posting your question to the community! Sorry your running into issues with the SharePointOnlineConnector transformer.

Just to get up to speed and first suggestions, have you tried taking take note of the Python compatibility setting under the Navigator > Workspace Parameters > Scripting > Python Compatibility as ​@j.botterill suggested? Also have you verified your interpreter is within range via Tools > FME Options > Translation > Python Interpreter?

Furthermore, this may give some insight depending on your use-case: Troubleshooting SharePoint Web Connections and Services.

Would also be able to give a quick run down of what you are doing with the SharePointOnlineConnector transformer if you can? It’ll provide some additional context.

Thanks!

issue has been resolved.

solution: deleted the sharepoint web connection on fme flow, republished it with the same azure sharepoint info and now it works.


Python issues were a red herring.
But I did also realise that fme form was using 3.XX ESRI version, switching this to 3.10+ (not esri version) solved other python issues I was having. so it may also be part of this solution. unsure.



fme ticket response from Technical Support Specialist I, FME Flow, after I informed him of my solution:

I'm glad to hear that the Sharepoint connection is back online! 2025.x introduced some rather major changes with how FME handles connections and authentication, and this extends to the SharepointOnlineConnector transformer. I suspect what happened is that your SharepointOnline package was updated automatically to version 1.2.2 with the installation of 2025.x, and had to then be republished to Flow to properly reestablish the connection.