Revision Summary Date Revision History Revision Class Comments 5/10/2016 1.0 New Initial Availability 7/14/2016 2.0 Major Significantly changed the technical content. 8/16/2017 3.0 Major Significantly changed the technical content. 3/16/2018 4.0 Significantly changed the technical content.
"items": { ... } }, "extendedProperties": { "type": "array", { ... } } }, "additionalProperties": false } The JSON-based partition data type is expressed differently than the Partition data structure, in which all properties of the Partition data type are flattened into the Partition object. For more details about Partition, see section . In the JSON representation, source is an object of type partitionSource and is equivalent to Partition. Additionally, like the types of Partition, the types of partitionSource are query, calculated, none, m, and entity. A source object of type query has a dataSource reference and a query property. The query property corresponds to the QueryDefinition property (see section 2.2.5.6). A source object of type calculated has an expression property, corresponds to the QueryDefinition property. If no source object is provided, the default of the partition has a source of type none. The source object of type m has an expression property, which corresponds to QueryDefinition property. The source object of type entity has a dataSource reference, and it has an entityName property that corresponds to the QueryDefinition property. In addition, the JSON-based partition object can include collections of child and objects. measure The schema for the measure object is as follows. { "description": "Measure object of Tabular Object Model (TOM)", "type": "object", "properties": { "name": { "type": "string" }, "description": { [ { "type": "string" }, { "type": "array", "items": { "type": "string" } } ] }, "expression": { "anyOf": [
"description": "Restore command of Analysis Services JSON API", "properties": { "restore": { "description": "Parameters of Restore command of Analysis Services JSON API", "properties": ... "additionalProperties": false } }, "additionalProperties": }, { "type": "object", "description": "Attach command of Analysis Services JSON API", "properties": { "attach": { "description": "Parameters of Attach command of Analysis Services JSON API", "properties": ... "additionalProperties": false } }, "additionalProperties": }, { "type": "object", "description": "Detach command of Analysis Services JSON API", "properties": { "detach": { "description": "Parameters of Detach command of Analysis Services JSON API", "properties": ... "additionalProperties": false } }, "additionalProperties": false } ] } } } } }, "additionalProperties": false } The following commands can be specified inside the sequence command:
RoleMembership Object Clarified that MemberID is a generated property. Major Create Columns Added SourceProviderType to the schema and the table of elements. Major Alter Annotations Added a product behavior note clarifying that the ID property is required. Major Delete Kpis Clarified that ID.KPI is not a required element. Major Delete LinguisticMetadata Clarified the use of the ID.LinguisticMetadata element. Delete PerspectiveTables Clarified the use of the ID.PerspectiveTable element. Major table Clarified that a table requires at least one column and a partition. Major translations translatedCaption to roles in the schema. Major relationship Added new section. Major Request Removed the database property and its description from the Major
A 17 C 271 18 E Examples 265 264 255 102 F 17 G 11 I 267 267 13 11 M Messages 18 N 18 12 O 16 13 P 267 17 17 268 Protocol examples 265 264 255 R References 13 12 16 S Security 267 267 Server 62 62 62 254 254 62 17 T 254 271 18 18 18 V 17