For example, using the Create Record (v3) connector and passing a value to shortcutDimension1Code (using v2.0/salesOrders or v2.0/purchaseOrders) gives this result:

{

"error": {

"code": "Internal_RecordNotFound",

"message": "The Sales Header does not exist. Identification fields and values: Document Type='Order',No.=''  CorrelationId:  569f08a5-61d0-44a9-8f8f-5207ab162c35."

}

workaround is to POST and then PATCH.

But even with that workaround, how do you use PowerApp connectors for Dimensions 3+?

with a full-featured REST call, you can specify as many dimensions as you want using the dimensionSetLines array:

{

"customerNumber": "C100002",

"dimensionSetLines": [

{

"code": "REGION",

"valueCode": "CENTRAL"

},

{ ... more code/valueCode pairs ... }

]

}

but such a construct is not available using the PowerApp Connectors. Even trying to do a Create Record (v3) using the dimensionSetLines API passing the following does not work (the intent would be to add a single dimension to the salesOrder, which you could then iterate through as many dimensions as you need):

{

"parentId": "ecef10bc-6eeb-ed11-8848-6045bd03b6ff", // this is the SalesHeader

"code": "REGION",

"valueCode": "CENTRAL"

}

yields this:

{

"error": {

"code": "Application_DialogException",

"message": "You must get to the parent first to create a dimension set line.  CorrelationId:  4cc9c75c-3789-4235-a484-ece2da45b819."

}

}

Even adding "parentType": "Sales Order" to define the parent id, gives this:

{

"error": {

"code": "BadRequest",

"message": "Control 'parentType' is read-only.  CorrelationId:  e382cb89-a089-41e0-b63a-587bb3816be4."

}

}

SUMMARY:

We need a way to use these connectors to easily manage dimensions. Clients expect at a minimum that a POST to shortcutDimension1Code should not produce an error. Then second, they want availability to influence more than just dimensions 1 and 2 using these connectors.