I am working with FME Flow 2025.2.4
I have an automation with several Workspace Actions. Parameters are passed between the workspaces using JSON automation parameters.
One of the Workspace Actions needs to be dynamic, so I pass the workspace name through a string automation parameter and the remaining parameters through a JSON automation parameter.
Everything works correctly when I use only standard Workspace Actions. However, as soon as I replace one of them with a Dynamic Workspace Action, the JSON can no longer be parsed inside the workspace. It appears that FME Flow automatically deserializes the JSON parameter before it reaches the workspace.
As a result, the value is no longer a valid JSON string, and transformers such as JSONExtractor or JSONFlattener fail when trying to parse it.
For example, a parameter that arrives as:
JSON
{
"umgebung": "tst",
"parameters": {
"port": 54322
}
}
is transformed into something like:
Plain Text
{ umgebung : tst, parameters : { port: 54322 } }
which is no longer valid JSON.
Is this expected behavior or a bug in Dynamic Workspace Actions?
If it is expected behavior, what is the recommended way to access the values from a JSON automation parameter inside a Dynamic Workspace Action? Is there a way to prevent the automatic deserialization, or to work directly with the resulting object structure?
Thanks in advance
Vera