# Result Mapping silently fails on keys containing square brackets

**URL:** <https://community.appfarm.io/t/result-mapping-silently-fails-on-keys-containing-square-brackets/2359>\
**Category:** Bug reports\
**Tags:** service, web-request\
**Created:** [May 20, 2026, 7:44am UTC](https://community.appfarm.io/t/result-mapping-silently-fails-on-keys-containing-square-brackets/2359 "2026-05-20T07:44:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/michael/32/2883_2.png) [@michael](https://community.appfarm.io/u/michael)\
**Post date:** [May 20, 2026, 7:44am UTC](https://community.appfarm.io/t/result-mapping-silently-fails-on-keys-containing-square-brackets/2359/1 "2026-05-20T07:44:22Z")

</div>

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:

```json
{
  "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:

```javascript
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?

---

<div class="post-metadata">

**Author:** ![Olav](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/olav/32/63_2.png) [@Olav](https://community.appfarm.io/u/Olav)\
**Post date:** [May 20, 2026, 2:06pm UTC](https://community.appfarm.io/t/result-mapping-silently-fails-on-keys-containing-square-brackets/2359/2 "2026-05-20T14:06:06Z")

</div>

This was resolved as a support case, and a fix will be rolled out tonight to restore the original result mapping behaviour.