Skip to main content
Solved

installing a python module (fieldcloud-sdk) on fme-flow 2025.2.4

  • March 10, 2026
  • 4 replies
  • 87 views
vki
Contributor
Forum|alt.badge.img+8

Hello

We have just updated FME Flow to 2025.2.4. As we also need the qfieldcloud-sdk module, I installed it with pip-install 

"C:\Program Files\FMEFlow\Server\fme\fmepython313\python.exe" -m pip install qfieldcloud-sdk

Somehow this installation got mixed up and the module was installed in python 3.12

"C:\Program Files\FMEFlow\Server\fme\fmepython313\python.exe" -m pip show qfieldcloud-sdk

Name: qfieldcloud-sdk
Version: 0.13.0
Summary: The official QFieldCloud SDK and CLI.
Home-page: https://github.com/opengisch/qfieldcloud-sdk-python
Author:
Author-email: Ivan Ivanov <ivan@opengis.ch>
License:
Location: C:\Program Files\FMEFlow\Server\fme\fmepython312\Lib\site-packages
Requires: certifi, charset-normalizer, click, idna, pathvalidate, requests, requests-toolbelt, tqdm, urllib3
Required-by:

(» Location: C:\Program Files\FMEFlow\Server\fme\fmepython312\Lib\site-packages)


Previously, we used FME Flow 2024.1.2.1, which used python 3.12, FME Flow now uses python 3.13 and as the module is installed in python 3.12 the module isn’t used and I get errors in my workspaces.

How can I fix this and install the module in python 3.13.?

 

Thanks in advance

Vera

Best answer by hkingsbury

As this tool is available as a python package, i’d suggest using the Python API/SDK instead of the CLI interface.

This would mean you use the PythonCaller instead of the SystemCaller

https://opengisch.github.io/qfieldcloud-sdk-python/

    4 replies

    hkingsbury
    Celebrity
    Forum|alt.badge.img+70
    • hkingsburyCelebrity
    • Celebrity
    • March 12, 2026

    You need to upload the module to FME Flow under resources\engine\plugins\python

    https://docs.safe.com/fme/html/FME-Flow/AdminGuide/Using-Python-with-FME-Flow.htm

    https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/Importing_Custom_Python_Modules_FMEServer.htm

    vki
    Contributor
    Forum|alt.badge.img+8
    • vkiContributor
    • Author
    • Contributor
    • March 13, 2026

    We completely uninstalled FME Flow again and deleted everything from the server host that was left over from previous installations (there were apparently still some old folders there). After that, we reinstalled FME Flow and then reloaded the qfieldcloud-sdk module (following the official instructions that @hkingsbury also referred to). Python is now working properly and there is no fmepython312 directory anymore.
    However, the module is now installed differently than in FME Flow 2024. In the workspaces that use the module qfieldcloud-sdk, it is accessed within a SystemCaller as a CLI tool (qfieldcloud-cli.exe).

    The path that was used in 2024 was:
    C:\Program Files\FMEFlow\Server\fme\fmepython312\Scripts\qfieldcloud-cli.exe

    In 2025, the module is now in 
    C:\ProgramData\Safe Software\FMEFlow\resources\engine\Plugins\Python\python313\
      - qfieldcloud_sdk
      - qfieldcloud_sdk-0.13.0.dist-info

    There is no file qfieldcloud-cli.exe anymore. But in the directory qfieldcloud_sdk-0.13.0.dist-info I found a file called

    entry_point.txt:
    [console_scripts]
    qfieldcloud-cli = qfieldcloud_sdk.cli:cli

    I guess, I have to use this somehow. But can I do this in the SystemCaller as before? I looked for a way with AI, but with no success...

    My goal is, to use the workspaces as they are and just adapt the path to qfieldcloud-cli.

    Thanks for any help!

     

    hkingsbury
    Celebrity
    Forum|alt.badge.img+70
    • hkingsburyCelebrity
    • Celebrity
    • Best Answer
    • March 15, 2026

    As this tool is available as a python package, i’d suggest using the Python API/SDK instead of the CLI interface.

    This would mean you use the PythonCaller instead of the SystemCaller

    https://opengisch.github.io/qfieldcloud-sdk-python/

    vki
    Contributor
    Forum|alt.badge.img+8
    • vkiContributor
    • Author
    • Contributor
    • March 16, 2026

    I got it working now with python. I had to install the module to the right directories. And as the qfieldcloud-module obviously uses another module, that is deprecated, I had to install a legacy version of it as well.

    So these were my installation-commands

    FME Form:

    "C:\Program Files\FME2025\fme.exe" python -m pip install qfieldcloud-sdk --target "C:\Program Files\FME2025\python\python313"

    "C:\Program Files\FME2025\fme.exe" python -m pip install legacy_cgi --target "C:\Program Files\FME2025\python\python313"

    FME Flow:

    "C:\Program Files\FMEFlow\Server\fme\fme.exe" python -m pip install qfieldcloud-sdk --target  "C:\Program Files\FMEFlow\Server\fme\python\python313"

    "C:\Program Files\FMEFlow\Server\fme\fme.exe" python -m pip install legacy_cgi --target  "C:\Program Files\FMEFlow\Server\fme\python\python313"

    In the workspaces I then changed from SystemCallers to PythonCallers. I had AI generate the code for the PythonCallers.

      Community Stats

      32,414
      Posts
      123,199
      Replies
      40,531
      Members
      Terms & ConditionsCookie settingsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.