Full versus condensed objects

Some methods in the Qlik Sense Repository Service (QRS) API return objects. The following object types may be returned:

  • Full object: The object includes all properties for the entity type.
  • Condensed object: The object includes the ID property and zero or more pre-selected properties, which may vary between different entity types. Condensed objects are used to reduce the amount of data to transfer.

Example: Fetching a server node configuration entity from the QRS

The full object for the server node configuration entity includes all properties:

{ "customProperties": [], "name": "MyServerNodeConfiguration", "hostName": "qlik.com", "isCentral": false, "engineEnabled": true, "proxyEnabled": false, "schedulerEnabled": true, "tags": [], "temporaryfilepath": "", "binaryfileRootpath": "", "privileges": null, "id": "6baa5c73-af76-48c8-a5e8-c185c86a885c", "createdDate": "2013-10-25T11:56:42.498Z", "modifiedDate": "2013-10-25T11:56:42.498Z", "modifiedByUserName": "INTERNAL\\sa_repository", "schemaPath": "ServerNodeConfiguration" }

The condensed object for the server node configuration entity includes a pre-defined sub-set of the properties:

{ "name": "MyServerNodeConfiguration", "hostName": "qlik.com", "temporaryfilepath": "", "binaryfileRootpath": "", "privileges": null, "id": "4bb7c8ea-da49-4b05-abeb-8a2d4334b995" }

Did this information help you?

Can you tell us why it did not help you and how we can improve it?