Saving production-line failed when setting variables

Hi Community,
I have a productionline with several workflows. Now for one specific workflow I am changing the variable-assignment for a bunch of variables (up to 10) in the production-line variable overview from “Workflow definition” to one of “Fixed Value” or a predefined production-line-variable.

Sometimes I get the following error when trying to save the production-line. When I then reload the page and set only 3 or 4 variables at a time and save it, I can change all the needed variables, but I always need to save in between. Ideally I want to change all variables and save it once.

Does anyone have an idea, what this error could tell me? Am I doing something wrong?
Thanks in advance!

`Could not save the production line

{ “data”: { “errors”: [ “JSON parse error: Unrecognized field “existsInWorkflow” (class$VariableReferenceWFVarAssignmentDTO), not marked as ignorable; nested exception is com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field “existsInWorkflow” (class$VariableReferenceWFVarAssignmentDTO), not marked as ignorable (2 known properties: “variableValue”, “variableName”]) at [Source: (PushbackInputStream); line: 1, column: 102118] (through reference chain:[“workflowSequence”]->java.util.ArrayList[1]->[“workflowVariableAssignments”]->java.util.ArrayList[0]->$VariableReferenceWFVarAssignmentDTO[“existsInWorkflow”])” ] }, “status”: 400, “config”: { “method”: “PUT”, “transformRequest”: [ null ], “transformResponse”: [ null ], “jsonpCallbackParam”: “callback”, “url”: “DELETED-DUE-TO-CUSTOMER-URL”, “data”: { “owner”: “4d7d9611-cb4f-44a3-8142-bf48db20e8d7”, “id”: “f26d8f95-2fd7-4150-b119-5b3e44440505”, “name”: “DELETED-DUE-TO-CUSTOMER-NAME”, “description”: “Model training and serving only!”, “notes”: "`

I’ve checked the ProductionLineWFVarAssignmentDTO class server side and there is no field existsInWorkflow in the most recent version of the class.

This (together with the HTTP status code) indicates a malformed request. If you’re using the ONE DATA Core Client, please file a Bug Report for this incident, including the error message posted above (please add version information for both Core Client and Server).

If you’re using another Client or directly use the REST API of the Core backend, please check your request data and make sure, it only contains the fields applicable to the request data type.

Hi, thanks for your quick help!
Yes indeed, I am using the ONE DATA core client. Then I create a bug ticket for that :slight_smile: