Data / Partial update projects

Task in alpha phase

This Data Factory task is in phase. You can contact the Product-Live team at contact@product-live.com if you want more details and get an early access.

This task allows to partially update projects. Unlike data-project-update, this task only updates the fields you provide, leaving other fields unchanged.

Task name:

Examples

JSON input - Update name

{
    "name": "data-project-patch",
    "taskReferenceName": "patch_project",
    "description": "Update project name",
    "type": "SUB_WORKFLOW",
    "optional": false,
    "inputParameters": {
        "request": {
            "method": "INLINE",
            "contentType": "application/json",
            "model": "default",
            "json": {
                "operations": [
                    {
                        "key": "a",
                        "context": {
                            "projectId": "633ec1f0829f993dedc288eb"
                        },
                        "element": {
                            "name": "New Project Name"
                        }
                    }
                ]
            }
        }
    }
}

JSON input - Update status

{
    "name": "data-project-patch",
    "taskReferenceName": "patch_project",
    "description": "Deactivate project",
    "type": "SUB_WORKFLOW",
    "optional": false,
    "inputParameters": {
        "request": {
            "method": "INLINE",
            "contentType": "application/json",
            "model": "default",
            "json": {
                "operations": [
                    {
                        "key": "a",
                        "context": {
                            "projectId": "633ec1f0829f993dedc288eb"
                        },
                        "element": {
                            "status": "INACTIVE"
                        }
                    }
                ]
            }
        }
    }
}

Definition

Property	Type	Required	Description
			The name (or type) of the task
			The unique name of the task in your job. It is used to reference this task in the workflow.
			The functional description of this task in your job.
			The type of the task. It must be SUB_WORKFLOW.
	:		true: the job continues if there is an error on this task. false: the job fails.
			Input parameters of the task. See below

Inputs Parameters

Property	Type	Required	Description
			The Product-Live API key. If not provided, an automaticaly generated API key will be used to perform the request on behalf of the current user. If provided, the given API key will be used to perform the request.
			See below
			To day, application/json and application/xml are supported.
			INLINE: The request body is provided inline in the request object. ATTACHMENT: The request body is provided as an attachment in the request object.
			The request body as a JSON object.
			See below
			A unique key to identify the element in the batch. This key will be associated to the element in the output.
			The element to create or update. See examples below
			Some element may require additional context to be created or updated.
			The request body as a file.
			The outputs of the request. Default: [{"mediaType": "application/json", "outputMode": "INLINE", "outputKey": "json"}].
			The media type of the output. To day, application/json and application/xml are supported.
			INLINE: The output is provided inline in the output object. ATTACHMENT: The output is provided as an attachment in the output object. INLINE is only supported for mediaType=application/json
			The key of the output. Either json or xml
			Default: DEFAULT. The model/format used in the output. To day, only 'DEFAULT' is supported.

contentType=application/json

• The expected elements are the entities described in the Product-Live API.
• See examples below for more details.

One element

{
    "operations": [
        {
            "key": "a",
            "element": {
                "...": "..."
            }
        }
    ]
}

Multiple elements

{
    "operations": [
        {
            "key": "a",
            "element": {
                  "...": "..."
            }
        }, {
            "key": "b",
            "element": {
              "...": "..."
            }
        }
    ]
}

Context requirements

Property	Type	Required	Description
			The ID of the project to update

Project patch element properties

Property	Type	Required	Description
			The new name of the project
			The new description of the project
			The new status. Possible values: ACTIVE, INACTIVE

contentType=application/xml

• This XML representation follow the one used by the JSON query language of the Product-Live API.
• The expected elements are the entities described in the Product-Live API.
• See examples below for more details.

One element

<?xml version="1.0" encoding="UTF-8"?>
<map xmlns="http://www.w3.org/2005/xpath-functions">
  <array key="operations">
    <map>
      <string key="key">a</string>
      <map key="context"></map>
      <map key="element">
        <string key="...">...</string>
      </map>
    </map>
  </array>
</map>

Outputs

Property	Type	Description
		An object containing the outputs of the task. Each output key is the key of the output defined in the outputs[][outputKey] input parameter.

Example

If your input parameters is as follows:

{
    "...": "...",
    "outputs": [
        {
            "mediaType": "application/json", 
            "outputMode": "INLINE", 
            "outputKey": "json_inline"
        },        
        {
            "mediaType": "application/xml", 
            "outputMode": "ATTACHMENT", 
            "outputKey": "xml_attachment"
        }
    ]
}

The output will be as follows:

{
    "outputs": {
        "json_inline": {
            "...": "...",
            "...": "..."
        },
        "xml_attachment": {
            "url": "..."
        }
    }
}

Json output - outputs[].outputMode=INLINE and outputs[].mediaType=application/json

• output.json is an array of objects as defined in the projects API.
• json is the default output key but may be changed by setting the outputKey property.

Example output:

[
    {
        "key": "a",
        "response": {
            "object": "project",
            "id": "633ec1f0829f993dedc288eb",
            "createdAt": "2023-10-06T09:00:00.000Z",
            "updatedAt": "2024-05-17T10:30:00.000Z",
            "name": "New Project Name",
            "description": "Original description",
            "status": "ACTIVE",
            "accountId": "2492"
        }
    }
]

Limits and additional notes

• When the outputMode=INLINE is selected, the maximum number of elements returned by this task is limited to 1000. If more elements are to be returned, the task ends with an error. To export up to the maximum of elements, use the limit input parameter to limit the number of elements return.

Additional examples

Patch project with XML input

job.json

{
    "name": "data-project-patch",
    "taskReferenceName": "patch_project",
    "description": "Patch project with XML",
    "type": "SUB_WORKFLOW",
    "optional": false,
    "inputParameters": {
        "request": {
            "method": "ATTACHMENT",
            "contentType": "application/xml",
            "model": "default",
            "file": "@my-request.xml"
        }
    }
}

my-request.xml

<?xml version="1.1" encoding="UTF-8"?>
<map xmlns="http://www.w3.org/2005/xpath-functions">
    <array key="operations">
        <map>
            <string key="key">a</string>
            <map key="context">
                <string key="projectId">633ec1f0829f993dedc288eb</string>
            </map>
            <map key="element">
                <string key="name">New Project Name</string>
            </map>
        </map>
    </array>
</map>

Patch project with dynamic values

job.json

{
    "name": "data-project-patch",
    "taskReferenceName": "patch_project",
    "description": "Patch project with dynamic values",
    "type": "SUB_WORKFLOW",
    "optional": false,
    "inputParameters": {
        "failOnError": true,
        "request": {
            "method": "INLINE",
            "contentType": "application/json",
            "model": "default",
            "json": {
                "operations": [
                    {
                        "key": "a",
                        "context": {
                            "projectId": "${find_project.output.json[0].id}"
                        },
                        "element": {
                            "description": "${workflow.input.newDescription}"
                        }
                    }
                ]
            }
        }
    }
}