Skip to main content
Question

WORKSPACE_NAME dereferenced?

  • November 11, 2024
  • 3 replies
  • 320 views

tb09114
Supporter
Forum|alt.badge.img+22

We just installed FME Flow 2024.1.2.1 on a Windows machine and I published a workspace. Running the workspace immediately ends in:

Undefined macro `WORKSPACE_NAME' dereferenced in file `flow_testing\sqlserver_test_delete\sqlserver_test_delete.fmw'

 

The workspace was published from an ArcGIS Interoperability Workbench [FME(R) 2024.0.1.0 (20240328 - Build 24202 - WIN64)], but I tried the same from FME Form 2024.2. The result is the same.

 

The workspace is as simple as it gets. Just a reader and a writer, and the error appears independent if there is a name for the workspace set or not.

 

Can somebody please point me the right direction to solve the issue?
 

3 replies

kate-safe
Safer
Forum|alt.badge.img+6
  • Safer
  • November 13, 2024

Thank you for your post!

There are a couple of things here:

  • First, it’s important to publish between the same version of FME Form and Flow - so publishing from 2024.2 Form to 2024.1 Flow is not going to work.  As well, publishing from an older Form (2024.0.1) to a newer Flow (2024.1) can also cause problems. 
  • Are you able to try publishing from the same version of Form to Flow and do you see the same issue?
  • Are you able to share the workspace with us that you are creating in ArcGIS Interop?

Thank you,

 

Kate


tb09114
Supporter
Forum|alt.badge.img+22
  • Author
  • Supporter
  • November 13, 2024

Hi, yes I realized today that it is possible to publish from the Data Interop Workbench and the workspace run is successful.

The compatibility check of Form and Flow (which I checked to late) clearly states that Form 2024.2 will not work with Flow 2024.1. I downgraded Form…

So, all good. 😊 


kate-safe
Safer
Forum|alt.badge.img+6
  • Safer
  • November 13, 2024

Wonderful!  Glad to hear things are working now!

 

 


Reply


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