Question

FME bug causing failure in Workspace Runner, multiple datasets

  • 14 July 2021
  • 3 replies
  • 21 views
jacklonsdale

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 

 

3 replies

rahulsharma
Rank
Badge +8

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

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
Rank
Badge

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

Reply


Community Stats

28,724
Posts
109,518
Replies
36,564
Members
Terms & ConditionsCookie settings
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.