CosmosDB patch operation changes datatype from numeric to string

Question

I'm performing a patch operation on a numeric field in CosmosDB using the CosmosDB connector in Logic Apps Standard.

The patch operation changes the field from numeric to string which is not what I want.

Inputs:

{
  "containerId": "SalesInvoices",
  "databaseId": "ODS",
  "itemId": "FAC000000427",
  "partitionKey": "FAC000000427",
  "patchOperations": [
    {
      "path": "/InvoiceTotals/InvoiceAmount",
      "type": "Replace",
      "value": 30.06
    },
    {
      "path": "/InvoiceTotals/PaidAmount",
      "type": "Replace",
      "value": 0
    },
    {
      "path": "/InvoiceTotals/OutstandingAmount",
      "type": "Replace",
      "value": 30.06
    }
  ]
}

Outputs:
{
  "Id": "FAC000000427",
  "ActivityId": "0ecba59b-ba6b-432c-8a8b-8cd9f69ece89",
  "RequestCharge": 14.22,
  "Content": {
    "InvoiceId": "FAC000000427",
    "InvoiceDate": "2024-07-10",
    "InvoiceTime": "12:00:00",
    "DueDate": "2024-08-09T12:00:00Z",
    "Currency": "EUR",
    "PaymentMethod": "Invoice",
    "PaymentCondition": "30DGN",
    "Relation": [
      {
        "Type": "Customer",
        "Id": "9999936"
      }
    ],
    "Status": "open",
    "InvoiceTotals": {
      "LineDiscountAmount": 10.08,
      "SubTotalAmount": 13.92,
      "InvoiceDiscountAmount": 0,
      "SurchargeAmount": 0,
      "VATAmount": 2.92,
      "InvoiceAmount": "30.06",
      "PaidAmount": 0,
      "OutstandingAmount": "30.06"
    },
...

Answer 1

Instead of passing the number directly in the value field, you can use the following format:

{
  "path": "/InvoiceTotals/InvoiceAmount",
  "type": "Replace",
  "value": "@float(30.06)"
}

As a workaround, after the patch operation, you can perform a validation step to check the types and convert them back if necessary. However, this would add additional complexity and might not be ideal.

Sometimes, the SDK or connector might have issues with data types. If you're using an older version of the CosmosDB SDK or the Logic App connector, consider updating to the latest version to see if this resolves the issue. Microsoft occasionally patches these types of issues in newer versions.