Skip to main content
Question

FME bug causing failure in Workspace Runner, multiple datasets


jacklonsdale
Contributor
Forum|alt.badge.img+4

Hi all,

 

Since upgrading to FME 2021, I have found previous workspaces that were working in 2020 are now not working. This appears to be when multiple datasets are referenced in a WorkspaceRunner and through a user parameter. It concatenates the filepaths together and loses the double quotes and separation, causing the reader to fail.

 

Any help would be appreciated.

 

Kind regards,

JackFME Problem 2FME Problem 1 

 

4 replies

rahulsharma
Safer
Forum|alt.badge.img+10

Hi @jacklonsdale​ 

There is one minor thing that I noticed in the WorkspaceRunner dialog, the Source Dataset is missing double quotes around the Filegeodatabase "$(FME_MF_DIR)Folder1\\Folder2\\Technical (T) - General\\Test\\*.gdb"

Can you try adding the quotes to see if that fixes the issue?


jacklonsdale
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • July 15, 2021

I've tried adding double quotes in the dialog and in text editor, but when I come out of the transformer settings, it removes them from the dialog! This is the weird thing...


cyril-fr
Participant
Forum|alt.badge.img
  • Participant
  • April 23, 2024

I have the same probleme with fme 2023.2.
I use WorkspaceRunner to call multiple postgis tables :

  • when I call the second workspace with fixed list of tables, it works
  • when the list of tables is written trough the editor or stored in an attribute, it fails

The log file reveals that fme try to read the entire string as a single table

I would appreciate some help


crystalatsafe
Safer
Forum|alt.badge.img+19

Hi @cyril-fr 

 

If you are able to share both workspaces (one where it works and one where it doesn’t work) with us we can take a closer look. 

 

Crystal 


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