Skip to main content

Hi.

I built a workspace in 2024.1, that fetches a number of files from a customer Sharepoint site. It works (in 2024.1) without problems.

I just installed 2024.2, and ran the workspace (with no changes).

Now it issues an error with a SyntaxWarning from the package “safe.microsoft-sharepoint”:

C:\Users\xxx\AppData\Roaming\Safe Software\FME\Packages\24783-win64\python\safe.microsoft-sharepoint\stringcase.py:247: SyntaxWarning: invalid escape sequence '\W'
return re.sub("\W+", "", string)

Is this something that I should worry about ?

SharepointOnlineConnector is not listed as an upgradable transformer in 2024.2

Cheers.

Have you tried uninstalling and reinstalling the package?

If this does not resolve your issue I would submit a ticket.


Have you tried uninstalling and reinstalling the package?

If this does not resolve your issue I would submit a ticket.

I don’t want to do that right now, since another virtual machine is running the same workspace with 2024.1 as a scheduled task.

I just upgraded FME 2024 locally to see if there were any issues, before upgrading on the VM.

I guess I found one, so I’m not upgrading FME 2024 on the VM at this time.


I wonder if it is a python version issue. do you have the same python versions installed on each machine and the same version compatibility set?

Asking chatgpt, it suggests that after 3.6 python would begin raising syntax errors when strings with escape characters (“\”) weren’t declared as raw strings.
https://chatgpt.com/share/673e31ac-fd98-800f-b74e-0aecdf38ae84

If changing the python versions doesn’t work (or isn’t possible in your setup) then yes, its definitely something for Safe to investigate!


I wonder if it is a python version issue. do you have the same python versions installed on each machine and the same version compatibility set?

As far as I can tell, FME 2024.1 and 2024.2 embeds the same Python version: 3.12.

I assume the transformer (SharepointOnlineConnector) uses the embedded Python, so unless 2024.1/3.12 != 2024.2/3.12, I don’t see an issue here.

I have submitted a ticket. It’s probably an easy fix in the code, and may be just a friendly warning, but I would like to be sure before upgrading our production version.


Reply