I just tested with create request Web API in Postman. Turns out setting null to a lookup field we need to use the Schema Name instead of the Logical Name. It's quite inconvenient when they are different, usually upper case vs lower case like this:

Display Name: Lookup Field
Schema name: new_LookupField
Logical name: new_lookupfield

so the payload should look like this:

{
  logicalName: "new_entityname",
  new_name: "some name",
  new_LookupField: null
}

Can we have some logic to check for this scenario and construct the payload correctly?

Proposed a fix in a PR

Hi @khoait - I completely missed this PR - sorry it's take me over a year to get to it! I merged in and the nullvalues integration test started to fail:

Perhaps this issue is specific to batch requests?

Thanks @scottdurow ! It happens to a single create request as well. I'll review the tests.

@scottdurow I added unit tests and passed all tests. please have a look.

Ah - ha! So it's the case sensitivity of the lookup field. Awesome job in spotting and fixing this!

yeah! it was very tricky when I first encountered the error.

I came up with a convention within the team to always modify the logical name to lowercase whenever we create a new field to keep it consistent for sdk and odata.

I hope the fix will be available soon! Cheers!

I'll get this merged and published asap!
I want to move v2 out of beta by the end of the year. Do you have anything that you could share to improve the documentation for dataverse-ify?

That's great to hear! Thanks @scottdurow !
First thing comes to mind is adding quick installation in the Readme. I'll create another issue/discussion with more details.