We are migrating to FME 2025.1 and I have a question about arcpy and the Emailer.
I have a workbench with a Creator and a PythonCaller. In the PythonCaller I added import arcpy. Python Compatibility is set to Esri ArcGIS Python 3.11. This works.
Now I want to add the Emailer transformer and I get the following screen:
If I Choose Cancel, I get no Emailer.
If I Choose Change Python Compatibility, I can add the Emailer. But now I the PythonCaller fails.
To solve that, I need to Change the Python Compatibility back to Esri ArcGIS Python 3.11. But if I do this, I get the following screen:
How can I configure my workbench to have both a working PythonCaller using arcpy and the Emailer transformer?
I need this on desktop (combined with ArcGIS Pro 3.5) and on server (combined with ArcGIS Enterprise 11.5).
The following transformers are problematic as well:
SharePointOnlineConnector
HTMLReportGenerator
AutodeskDocsConnector
Page 1 / 1
Here are some mentions about compatibility but I don’t understand why so many components seem to be build with 3.13 while esri still is at 3.11
@birgit created support ticket #56873 for this issue.
For info
I am able to run a workspace in 2025.1 with
Python Compatibility set to Esri ArcGIS Python 3.11
A pythoncaller using ArcPy
SharePointOnlineConnector
To get the python caller on the canvas I have to go through the steps you described yesterday, or copy and paste from 2024.1, the same with the SharePointOnlineConnector. I haven’t however, upgraded the package (latest is 1.4, I have 1.2.2 installed)
Possibly downgrading the emailer package would work?
Weird, I have the sharepoint online connector 1.1.7 and I have problems with that version too.
For info
I am able to run a workspace in 2025.1 with
Python Compatibility set to Esri ArcGIS Python 3.11
A pythoncaller using ArcPy
SharePointOnlineConnector
To get the python caller on the canvas I have to go through the steps you described yesterday, or copy and paste from 2024.1, the same with the SharePointOnlineConnector. I haven’t however, upgraded the package (latest is 1.4, I have 1.2.2 installed)
Possibly downgrading the emailer package would work?
Thanks for sharing! Tried downgrading to 1.2.2 but this did not work for me, same behaviour as described in the initial post. I tested on a VM with only FME desktop 2025.1 and ArcGIS Pro 3.5.0 installed. Did not have FME nor Pro installed prior to this.
Also, my concern is, as the HTMLReportGenerator is not an item from the FME hub, that Safe started upgrading the default transformers to 3.13 where Esri is limited to 3.11. So now I wonder which other default transformers won’t work anymore.
I was mistaken, I can’t add either an email or a sharepointconnector and then switch the python compatibility, but I can copy paste them into a workspace with the python compatibility already set without issue (and they appear to run with no warnings/errors)
I was mistaken, I can’t add either an email or a sharepointconnector and then switch the python compatibility, but I can copy paste them into a workspace with the python compatibility already set without issue (and they appear to run with no warnings/errors)
Copy pasting these transformers from an older version of fme desktop works for me. Thanks, this is a big relief!
I was mistaken, I can’t add either an email or a sharepointconnector and then switch the python compatibility, but I can copy paste them into a workspace with the python compatibility already set without issue (and they appear to run with no warnings/errors)
Copy pasting these transformers from an older version of fme desktop works for me. Thanks, this is a big relief!
Cheered too soon, when I try to save the workspace it still fails...
@birgit created support ticket #56873 for this issue.
The internal ticket for this is FMEENGINE-87331, which is scheduled to be fixed in 2025.1.1
Do we know the exact details of when this occurs?
I was able to save my workspace in 2025.1 without issue.
This is all we know. We continue to test / migrate our non arcpy workspaces and hope the version with the fix is released soon. In previous years xxxx.1.1 was released a month after the release of xxxx.1 which was 2025-07-08 so beginning of august would be nice.
Today unable to reproduce. Currently able to copy and paste transformers from 2021/2024 into the workbench and save.
But probably the workbench we tested on friday had something in it that switched it to 3.13 in the background on save.
I’m not able to add a PythonCaller (without copying from another workbench) without switching from Esri 3.11 to 3.13. And as soon as I switch to 3.13 unable to go back without removing the HTMLReportGenerator etc. Till now I added the pythoncaller first and then switch so I did not notice.
It seems that we need to write all workbenches in 2024 and run them in 2025 untill 2025.1.1 is released?
What i did not understand, but now do is that setting the workbench to 3.9+ will still run all python code with 3.13 because that is shipped with FME. And Esri 3.9+ will still run the code with 3.11 because that is installed with Esri. Guess it is only used to signal that the python code should be compatible with 3.9 and later. But nothing else.
So I hope the packages will all return to supporting 3.9+ as intended.
Watching closely as upgrade of flow environments to 2025.1 is imminent
I'm sorry for any inconvenience this may have caused! We have an internal ticket with development for this issue (FMEENGINE-87331), which is scheduled to be fixed in version 2025.1.1. I will update this thread once the issue has been fixed.
@crystalatsafe
Safe is aware the list of Transformers with this issue is longer than the current 3 identified?
You probably don’t need to know all the Transformers to fix the issue but at least these also have the problem:
Could you also add Python compatibility info to the Autodesk package?
In the past there was an issue when installing Autodesk package when a custom interpreter was set. It can only be installed with the default python interpreter.
Hi @jkr_wrk
Thanks for providing a list of the transformers impacted. I have let the development team know.
We previously included supported Python versions, especially when we still supported Python 2.7, as there were actual restrictions on the transformer/format. Now, packages are generally built to work on all Python versions supported by the minimum build of FME specified in requirements under the package details on FME hub.
If it's not documented on the FME hub, then as long as the transformer is being used on that minimum FME build or newer, there shouldn't be any issues with Python compatibility. If it is documented, it's either documentation from the past, or there is a reason to consider the Python version in the version of FME the package is being run on.
If you do see any issues when using a custom interpreter please let us know.
This issue has been fixed in version 2025.1.1 (Build 25615), released yesterday. You can download the latest version at: https://fme.safe.com/downloads/
