Page Comparison

dt

UTC date and time when this transaction was written to the log.

The user who triggered the action in the first place. Null if change was triggered by the system.

NOTE: This field is only populated in some cases for the time being.

A globally unique identifier which permits to group related traces.

For example if an operation updates three different objects in the framework of an operation then all three traces share the same ts value.

An English description of the user interface or system operation attached to ts.

Examples: "Job status change", "Batch deletion of jobs", "Submission of order"...

NOTE: This field is only populated in some cases for the time being.

Uniquely identifies the type of object (primary keys in brackets)being traced.

For example:

• o: Order (oid)
• jc: Codyt Job (jid)
• js: Standard job (jid)
• ps: Person/User (uid)
• mc: Master Company (mid)
• c: Company (cid)
• p: Project (pid)
• d: Document (did)
• rs: RevisionSet (rsid)
• pl: Pricelist (plid)
• svc: Pricelist services (excluding inhouse person services) (svcid)
• ds: Resource (dsid)
• jsd: Standard job document (jid + did)
• ca: Company properties (caid)

User profiles

• uprof: User profiles (uprofid)
• uproff: User profile functionality (uprofid, ufunc)

• ...

See Traces for all objects.

The unique key of the changed object. This may be a composite key.

Example of a company change (object "c"):

key: { "cid": 1000 }

Example of a standard job document change (object "jsd"):

key: { "js": "s9928", "did": 88372 }

See list of objects and their keys

Change details

• "d": Deletion
• "i": Insertion
• "c": Change

The data fields. Each element contains a changed field.

Example:

[
	{ "f": "Reference", "v": "New reference 1", "p": "Old reference" },
	{ "f": "Status_", "v": 3, "p": 2 }
]

Notes:

• With deletions the fld property is always empty
• Fields with null-values are not listed