DataIteratorUtil createTableMap support for matching on encoded fieldKey for insert/update/save rows

[cnathe]

Rationale

One of the recent special characters issues that we fixed had to do with the app using fieldKeys instead of column names when posting the data from a Details form to the updateRows API. For those rows without any encoded special characters, this wasn't an issue but for those with the encoded special characters, the columns were not being resolved for the target table. In the data iterator code that handles this "column matching" we already support matching the column on name, label, uri, alias, among other things. This PR adds in the encoded fieldKey to the table column map that is used for this matching.

Related Pull Requests

• Issue 52038: Fix problems for fields whose names and fieldKeys are different labkey-ui-components#1697

Changes

• DataIteratorUtil createTableMap support for matching on column encoded fieldKey

[labkey-susanh]

Probably we should add unit tests somewhere. I'm not sure what coverage we have for this server-side code already, but at the moment our applications are likely not going to hit this code path.

[cnathe]

Probably we should add unit tests somewhere. I'm not sure what coverage we have for this server-side code already, but at the moment our applications are likely not going to hit this code path.

Yes for sure. I was opening this as a Draft PR to get review on the overall approach before I started on adding any tests for the change. I will for surely do so before we merge this PR. Thanks.