Result Mapping silently fails on keys containing square brackets

Bug reports
,
1

Ran into this today and wanted to flag it, because I’m fairly sure this used to work and the failure mode is concerning.

Setup

I’m pulling data from a Power BI / DAX query into a Web Request action. The response looks like this — standard Power BI shape, column names come back wrapped in square brackets:

{
  "results": [{
    "tables": [{
      "rows": [
        {
          "[DG_Prosent]": 0.149,
          "[Løpetid_Snitt]": 168.19,
          "[Antall_Prosjekt]": 52,
          "[employee]": "name@example.com"
        }
      ]
    }]
  }]
}

In the Result Mapping:

  • Root Path: results.0.tables.0.rows

  • Cardinality: Many

  • Property mappings: exact key names including brackets ([DG_Prosent], [employee], etc.)

Result

The Data Source ends up empty. No error, no warning in the logs — just zero rows mapped, even though the raw response in DevTools clearly contains the array.

Appfarm recognizes that there are X amount of rows, and creates them in the mapped table, just without any data.

The mapper appears to interpret [...] in the property path as array index notation rather than treating it as a literal part of the key. The lookup silently fails for every bracketed property.

Workaround

A Result Parser that strips the brackets fixes it:

return rawResponseData.results[0].tables[0].rows.map(row => {
  const cleaned = {};
  Object.keys(row).forEach(key => {
    cleaned[key.replace(/[\[\]]/g, '')] = row[key];
  });
  return cleaned;
});

After that, mapping with the clean names (DG_Prosent, employee, etc.) works fine.

This used to work. I have older flows that handled bracketed keys without any parser workaround, so something seems to have changed in how the result mapper resolves property paths.

If a mapped property path can’t be resolved, that really should produce a warning at minimum. As it stands, any other Power BI / DAX integrations could be silently dropping data and we´d have no way of knowing

Has anyone else hit this recently? And could someone from the Appfarm team confirm whether bracket handling in the result mapper changed in a recent release?