Lowercasing keys breaks @odata.bind

[Majora320]

In all of the create/update functions in _odata.py, _lowercase_keys is called, but this breaks @odata.bind parameters as the keys are case sensitive to the table name. This is probably Microsoft's implementation of odata doing things wrong here, but there needs to be a way to create/update records with lookup columns.

[JoshuaDBruton]

Hey @Majora320 I have this issue as well.

So just bumping.
Seems like a major oversight, like nobody tested related columns in a DB service?

[MrPoopey]

PR opened: #86

[mkr-ac]

@tpellissier-msft @zhaodongwang-msft Any progress on this issue?

[saurabhrb]

Thanks for reporting this, @Majora320 — and to @JoshuaDBruton, @MrPoopey, and @mkr-ac for following up. Apologies for the delayed response on this.

This was a confirmed bug. _lowercase_keys() was unconditionally lowercasing all record payload keys, including @odata.bind annotation keys where the navigation property name is case-sensitive.

Fixed in PR #137 — _lowercase_keys() now preserves keys containing @odata.. We also appreciate @MrPoopey's PR #86 which identified the same approach.

The fix will ship in the next beta release.

[saurabhrb]

Closing — fixed in PR #137.