Transfer/Update tool: Workflows and Production lines doubled

ONE DATA Core
1

Dear all,
we exported our project (without data) from our developing instance and tried to update a client’s instance. Unfortunately, all our production lines and workflows got doubled instead of updated. What did we do wrong?
That is the json (the default setting):

{
    "version": "v1",
    "filters": {
        "keysOnly": {
            "type": "resourceType",
            "resourceType": "KEY"
        },
        "connectionsOnly": {
            "type": "resourceType",
            "resourceType": "CONNECTION"
        },
        "dataOnly": {
            "type": "resourceType",
            "resourceType": "DATA"
        },
        "workflowsOnly": {
            "type": "resourceType",
            "resourceType": "WORKFLOW"
        },
        "productionLinesOnly": {
            "type": "resourceType",
            "resourceType": "PRODUCTION_LINE"
        },
        "functionsOnly": {
            "type": "resourceType",
            "resourceType": "FUNCTION"
        },
        "schedulesOnly": {
            "type": "resourceType",
            "resourceType": "SCHEDULE"
        },
        "appsOnly": {
            "type": "resourceType",
            "resourceType": "APP"
        }
    },
    "resourceTransformations": [
        {
            "condition": {
                "negate": true,
                "any": [
                    "keysOnly",
                    "connectionsOnly",
                    "dataOnly",
                    "workflowsOnly",
                    "productionLinesOnly",
                    "functionsOnly",
                    "schedulesOnly",
                    "appsOnly"
                ]
            },
            "action": {
                "type": "skip",
                "skip": true
            }
        },
        {
            "condition": "schedulesOnly",
            "action": {
                "type": "replace",
                "filePathRegex": "^scheduleMeta\\.json$",
                "jsonPath": "$.active",
                "searchRegex": "^.*$",
                "replace": "false"
            }
        },
        {
            "condition": "keysOnly",
            "action": {
                "type": "contextAdaption",
                "skipUpdateIfExists": true
            }
        },
        {
            "condition": "connectionsOnly",
            "action": {
                "type": "contextAdaption",
                "skipUpdateIfExists": true
            }
        },
        {
            "condition": "dataOnly",
            "action": {
                "type": "contextAdaption",
                "skipDataTableNameUpdate": true
            }
        }
    ]
}

@fmossner @mfriedl

2

As far as I know DPU do not matches the ressources by name but the ressource ID from the instance where they are exported.
So if the ressource IDs in the source instance has been changed (e.g. setting up new project), they won’t be recognized as same ressources and DPU will create new ressouces which I assume why the WFs are PLs are doubled.
You may need to setup a new project in the client’s instance.
If it is not possible, other thing that would work is making a huge list to match each ressource to other under resourceTransformations. It’s bascially making filter for each element, so it can be extremly time consuming

1 Like
3

thanks for the reply, do-hwan. that was exactly the problem here, since the original deployment came from a different source.