Unify and manage your data

CSV Output Format for Exported Activities

CSV Output Format for Activities Export describes the values displayed in the CSV columns for exported activities.

CSV Output Format

Use the header and column values listed in Table 1: Activities Export in a CSV Output Format which describes the headers and values that will be in the exported file.

Table 1. Activities Export in a CSV Output Format
HeaderColumn Value
activityDescription Defines the description property value of the activity (if present).
activityId Defines the Activity ID based on the activity URI property value.
activityLabel Defines the label property value of the activity (if present).
clientType Defines the clientType property value of the activity item.
endObjectLabelDefines the endObjectLabel property value of the activity item (if present).
endObjectUriDefines the endObjectUri property value of the activity item (if present).
eventIdDefines the eventId property value of the activity item (if present).
idDefines the ID property value of the activity item.
methodDefines the method property value of the activity item.
objectLabelDefines the objectLabel property value of the activity item (if present).
objectTypeDefines the objectType property value of the activity item (if present).
objectUriDefines the objectUri property value of activity item (if present).
startObjectLabelDefines the startObjectLabel property value of the activity item (if present).
startObjectUriDefines the startObjectUri property value of the activity item (if present).
timestampDefines the timestamp of an activity.
urlDefines the URL property value of the activity item.
userDefines the user property value of an activity.
Delta:

delta.attributeType

delta.type

delta.newValue.id

delta.newValue.isComplex

delta.newValue.ov

delta.newValue.value

delta.oldValue.id

delta.oldValue.isComplex

delta.oldValue.ov

delta.oldValue.value

Defines the values (if existing) of the corresponding properties that belongs to the delta property of an activity.
data.entities/entityIdDefines the entities/entityId properties values of data property of an activity item (if present).
Data

data.matchGroups

data.mergeReason

data.mergeType

data.objectUris

data.potentialMatches

data.state

data.taskId

data.type

Defines the corresponding properties values of the data property of an activity item (if present).
Delta sources:

delta.newValue.source

delta.oldValue.source

delta1.newValue.source

delta1.oldValue.source

Defines the values of sources property of newValue or oldValue for activity item (if present).

Header Format for Multiple Values

Header format specifies how the Export Service must name CSV header columns when multiple values are present.

See Table 2: Header Format for Multiple Values to find out how the Export Service must name the CSV header columns when multiple values are present.

Table 2. Header Format for Multiple Values
NameDetailsUsed as Default forExample (an activity with 3 delta values)
activityThe first header of attribute values will be named as the name of the attribute. All the following headers of the attribute values will fit into the pattern as follows:

<NameOfAttribute>N

Where N is an index of an attribute value.
Note: The attribute value indexing begins with 0
.
ACTIVITY_LOGdelta.attributeType

delta.newValue.source

delta.oldValue.source

delta1.attributeType

delta1.newValue.source

delta1.oldValue.source

delta2.attributeType

delta2.newValue.source

delta2.oldValue.source

Example: JSON

Consider the following JSON activity.

JSON: Activity JSON

 {
    "uri": "activities/6464f74b-6d39-461b-b77a",
    "user": "user1",
    "timestamp": 1624516093202,
    "items": [
        {
            "id": "3N9KdQqi",
            "user": "user1",
            "method": "POST",
            "url": "/reltio/api/myTenant/entities/16U21JfB/_update",
            "clientType": "Reltio UI",
            "timestamp": 1624516093202,
            "objectUri": "entities/16U21JfB",
            "objectType": "configuration/entityTypes/HCA",
            "objectLabel": "qwer",
            "data": {
                "type": "ENTITY_CHANGED"
            },
            "deltaCollection": {
                "ovChanged": true,
                "delta": [
                    {
                        "type": "ATTRIBUTE_ADDED",
                        "attributeType": "configuration/entityTypes/HCA/attributes/TypeCode",
                        "newValue": {
                            "value": "COCL",
                            "ov": true,
                            "id": "2lBM43Rwq",
                            "sources": [
                                "Reltio"
                            ]
                        }
                    },
                    {
                        "type": "ATTRIBUTE_ADDED",
                        "attributeType": "configuration/entityTypes/HCA/attributes/Name",
                        "newValue": {
                            "value": "qwer",
                            "ov": true,
                            "id": "2lBM43Nga",
                            "sources": [
                                "Reltio"
                            ]
                        }
                    }
                ]
            },
            "eventId": "1624516093202_01Ga6j3"
        }
    ],
    "itemsTotal": 1
}

CSV:

See Table 3: Examples to find the activityID and the corresponding delta.type.

Table 3. Examples
activityIddelta.attributeTypedelta.typedelta1.attributeTypedelta1.typedelta.newValue.iddelta.newValue.isComplexdelta.newValue.ovdelta.newValue.valuedelta1.newValue.iddelta1.newValue.isComplexdelta1.newValue.ovdelta1.newValue.valuedelta.newValue.sourcedelta1.newValue.source
6464f74b-6d39-461b-b77aconfiguration/entityTypes/HCA/attributes/TypeCodeATTRIBUTE_ADDEDconfiguration/entityTypes/HCA/attributes/NameATTRIBUTE_ADDED2lBM43RwqfalsetrueCOCL2lBM43NgafalsetrueqwerReltioReltio

Output format for entities' URIs

Some activity log events have attributes based on entities' URI. Entities URIs or labels from the activities data field can be presented in the CSV export output file depending on the tenant configuration. By default, entities' URIs are used in CSV headers, labels are cell values.

Output format for entities URIs and labels for data field of an activity in Activity Log Export are listed in Table 4: Output Format For Entities URIs and Labels.

Table 4. Output Format for Entities URIs and Labels
activityId...data.entities/id1adata.entities/id1bdata.entities/id2data.entities/id3adata.entities/id3bdata.entities/id4...
1...JohnJonny ...
2...David ...
3 AlexanderAlex
4John Jonathan
Note: To prevent the file from overblowing, you can have a maximum of 100 columns.

$.exportConfig.alDataMergeParticipantUseUriAsColumnName =false

Header Format

data.Entity.URI, data.Entity.Label, ..., data.Entity(N).URI, data.Entity(N).Label

The entities URIs and labels are values in the appropriate cells. You can switch to this format. For more information, contact https://support.reltio.com/hc/en-us.

Example:

Output formats for entities URIs and labels for data fields of an activity in Activity Log Export are listed in Table 5: Output format for entities URIs and labels.

Table 5. Output Format for Entities URIs and Labels
activityIddata.Entity.URIdata.Entity.Labeldata.Entity1.URIdata.Entity1.Label
1entities/id1aJohnentities/id1bJonny
2entities/id2David
3entities/id3aAlexanderentities/id3bAlex
4entities/id1aJohnentities/id4Jonathan

Examples

Example 1

Consider the following activity:

JSON: Activity JSON

{
    "uri": "activities/a499-eeff-7f394263",
    "user": "user1",
    "label": "USER_LOGIN",
    "description": "User user1 was logged in",
    "timestamp": 1625022168540,
    "items": [
        {
            "id": "35Wk1b9W",
            "user": "user1",
            "method": "POST",
            "url": "/reltio/api/myTenant/activities",
            "clientType": "Reltio UI",
            "timestamp": 1625022168540
        }
    ],
    "itemsTotal": 1
}    

CSV

See the activity details listed in Table 6: CSV Output file of the Activities Export.

Table 6. CSV Output file of the Activities Export
activityDescriptionactivityIdactivityLabelclientTypeidmethodtimestampurluser
User logged in as user1.a499-eeff-7f394263USER_LOGINReltio UI5Gx7j51KPOST1625022168540/reltio/api/myTenant/activitiesuser1

Example 2

Consider two activities (three activity items).

JSON: Activities JSON
[
    {
        "uri": "activities/86d92622-2a4b-4ee1-b123-18b29a77392a",
        "user": "user1",
        "timestamp": 1625039617967,
        "items": [
            {
                "id": "3MjJSuWa",
                "user": "user1",
                "method": "POST",
                "url": "/reltio/api/myTenant/entities/qxxiuRk/_notMatch",
                "clientType": "Reltio UI",
                "timestamp": 1625039617967,
                "objectUri": "entities/qxxiuRk",
                "objectType": "configuration/entityTypes/HCP",
                "objectLabel": "- cBtCASwtAeEbTxe Agacati",
                "data": {
                    "entities/18GdnGG8": "",
                    "mergeType": "MANUAL",
                    "potentialMatches": "entities/18GdnGG8",
                    "type": "NOT_MATCHES_SET",
                    "matchGroups": "configuration/entityTypes/HCP/matchGroups/HCPSameCountryCode"
                },
                "eventId": "1625039617967_0ZIMeiR"
            },
            {
                "id": "3MjJSymq",
                "user": "user1",
                "method": "POST",
                "url": "/reltio/api/myTenant/entities/qxxiuRk/_notMatch",
                "clientType": "Reltio UI",
                "timestamp": 1625039617967,
                "objectUri": "entities/18GdnGG8",
                "objectType": "configuration/entityTypes/HCP",
                "objectLabel": "",
                "data": {
                    "entities/qxxiuRk": "- cBtCASwtAeEbTxe Agacati",
                    "mergeType": "MANUAL",
                    "potentialMatches": "entities/qxxiuRk",
                    "type": "NOT_MATCHES_SET",
                    "matchGroups": "configuration/entityTypes/HCP/matchGroups/HCPSameCountryCode"
                },
                "eventId": "1625039617967_0ZOasl6"
            }
        ],
        "itemsTotal": 2
    },
    {
        "uri": "activities/a26bb05f-e68e-450c-8468-0e6b7057b8b8",
        "user": "collaboration-service",
        "timestamp": 1625035403089,
        "items": [
            {
                "id": "2vHx0LcI",
                "user": "collaboration-service",
                "method": "POST",
                "url": "/reltio/api/myTenant/entities/qxxiuRk/attributes/Commenters",
                "clientType": "UNKNOWN",
                "timestamp": 1625035403089,
                "objectUri": "entities/qxxiuRk",
                "objectType": "configuration/entityTypes/HCP",
                "objectLabel": "- cBtCASwtAeEbTxe Agacati",
                "data": {
                    "type": "ENTITY_CHANGED"
                },
                "deltaCollection": {
                    "ovChanged": false
                },
                "eventId": "1625035403089_1XiTGpX"
            }
        ],
        "itemsTotal": 1
    }
]

CSV

See Table 7: Listed Activities to find the list of the fields in the CSV file.

Table 7. Listed Activities
activityIdclientTypeeventIdidmethodobjectLabelobjectTypeobjectUritimestampurluserdata.entities/18GdnGG8data.entities/qxxiuRkdata.matchGroupsdata.mergeTypedata.potentialMatchesdata.type
86d92622-2a4b-4ee1-b123-18b29a77392aReltio UI1625039617967_0ZIMeiR3MjJSuWaPOSTcBtCASwtAeEbTxe Agacaticonfiguration/entityTypes/HCPqxxiuRk1625039617967/reltio/api/alenat/entities/qxxiuRk/_notMatchuser1configuration/entityTypes/HCP/matchGroups/HCPSameCountryCodeMANUALentities/18GdnGG8NOT_MATCHES_SET
86d92622-2a4b-4ee1-b123-18b29a77392aReltio UI1625039617967_0ZOasl63MjJSymqPOSTconfiguration/entityTypes/HCP18GdnGG81625039617967/reltio/api/alenat/entities/qxxiuRk/_notMatchuser1cBtCASwtAeEbTxe Agacaticonfiguration/entityTypes/HCP/matchGroups/HCPSameCountryCodeMANUALentities/qxxiuRkNOT_MATCHES_SET
a26bb05f-e68e-450c-8468-0e6b7057b8b8UNKNOWN1625035403089_1XiTGpX2vHx0LcIPOSTcBtCASwtAeEbTxe Agacaticonfiguration/entityTypes/HCPqxxiuRk1625035403089/reltio/api/alenat/entities/qxxiuRk/attributes/Commenterscollaboration-serviceENTITY_CHANGED

Important Points:

  • The CSV column separator is , and it is not configurable.
  • A column is present in the CSV output file only if there is at least one value that is not null. The value “” is an empty string value, but not a missing value.
  • The order of the columns is not guaranteed and cannot be configured.