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.
Header | Column 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. |
endObjectLabel | Defines the endObjectLabel property value of the activity item (if present). |
endObjectUri | Defines the endObjectUri property value of the activity item (if present). |
eventId | Defines the eventId property value of the activity item (if present). |
id | Defines the ID property value of the activity item. |
method | Defines the method property value of the activity item. |
objectLabel | Defines the objectLabel property value of the activity item (if present). |
objectType | Defines the objectType property value of the activity item (if present). |
objectUri | Defines the objectUri property value of activity item (if present). |
startObjectLabel | Defines the startObjectLabel property value of the activity item (if present). |
startObjectUri | Defines the startObjectUri property value of the activity item (if present). |
timestamp | Defines the timestamp of an activity. |
url | Defines the URL property value of the activity item. |
user | Defines the user property value of an activity. |
Delta:
| Defines the values (if existing) of the corresponding properties that belongs to the delta property of an activity. |
data.entities /entityId | Defines the entities /entityId properties values of data property of an activity item (if present). |
Data
| Defines the corresponding properties values of the data property of an activity item (if present). |
Delta sources:
| 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.
Name | Details | Used as Default for | Example (an activity with 3 delta values) |
---|---|---|---|
activity | The 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:
Note: The attribute value indexing begins with 0 . | ACTIVITY_LOG | delta.attributeType
|
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
.
activityId | delta.attributeType | delta.type | delta1.attributeType | delta1.type | delta.newValue.id | delta.newValue.isComplex | delta.newValue.ov | delta.newValue.value | delta1.newValue.id | delta1.newValue.isComplex | delta1.newValue.ov | delta1.newValue.value | delta.newValue.source | delta1.newValue.source |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6464f74b-6d39-461b-b77a | configuration/entityTypes/HCA/attributes/TypeCode | ATTRIBUTE_ADDED | configuration/entityTypes/HCA/attributes/Name | ATTRIBUTE_ADDED | 2lBM43Rwq | false | true | COCL | 2lBM43Nga | false | true | qwer | Reltio | Reltio |
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.
activityId | ... | data.entities/id1a | data.entities/id1b | data.entities/id2 | data.entities/id3a | data.entities/id3b | data.entities/id4 | ... |
---|---|---|---|---|---|---|---|---|
1 | ... | John | Jonny | ... | ||||
2 | ... | David | ... | |||||
3 | … | Alexander | Alex | |||||
4 | … | John | Jonathan |
$.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.
activityId | data.Entity.URI | data.Entity.Label | data.Entity1.URI | data.Entity1.Label |
---|---|---|---|---|
1 | entities/id1a | John | entities/id1b | Jonny |
2 | entities/id2 | David | ||
3 | entities/id3a | Alexander | entities/id3b | Alex |
4 | entities/id1a | John | entities/id4 | Jonathan |
Examples
Example 1Consider 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.
activityDescription | activityId | activityLabel | clientType | id | method | timestamp | url | user |
---|---|---|---|---|---|---|---|---|
User logged in as user1 . | a499-eeff-7f394263 | USER_LOGIN | Reltio UI | 5Gx7j51K | POST | 1625022168540 | /reltio/api/myTenant/activities | user1 |
Example 2
Consider two activities (three activity items).
[
{
"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.
activityId | clientType | eventId | id | method | objectLabel | objectType | objectUri | timestamp | url | user | data.entities/18GdnGG8 | data.entities/qxxiuRk | data.matchGroups | data.mergeType | data.potentialMatches | data.type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
86d92622-2a4b-4ee1-b123-18b29a77392a | Reltio UI | 1625039617967_0ZIMeiR | 3MjJSuWa | POST | cBtCASwtAeEbTxe Agacati | configuration/entityTypes/HCP | qxxiuRk | 1625039617967 | /reltio/api/alenat/entities/qxxiuRk/_notMatch | user1 | configuration/entityTypes/HCP/matchGroups/HCPSameCountryCode | MANUAL | entities/18GdnGG8 | NOT_MATCHES_SET | ||
86d92622-2a4b-4ee1-b123-18b29a77392a | Reltio UI | 1625039617967_0ZOasl6 | 3MjJSymq | POST | configuration/entityTypes/HCP | 18GdnGG8 | 1625039617967 | /reltio/api/alenat/entities/qxxiuRk/_notMatch | user1 | cBtCASwtAeEbTxe Agacati | configuration/entityTypes/HCP/matchGroups/HCPSameCountryCode | MANUAL | entities/qxxiuRk | NOT_MATCHES_SET | ||
a26bb05f-e68e-450c-8468-0e6b7057b8b8 | UNKNOWN | 1625035403089_1XiTGpX | 2vHx0LcI | POST | cBtCASwtAeEbTxe Agacati | configuration/entityTypes/HCP | qxxiuRk | 1625035403089 | /reltio/api/alenat/entities/qxxiuRk/attributes/Commenters | collaboration-service | ENTITY_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.