xrmquery.update operation will be used to update the CRM ID binding to null

Question

xrmquery.update operation will be used to update the CRM ID binding to null

I am encountering an issue with using XrmQuery to update an id-binding field with a value of "null".

Below is the code snippet that I'm working with:

XrmQuery.update(x => x.contacts,
                recordId,
                {
                    address2_line1: null,
                    address2_postalcode: null,
                    address2_city: null,
                    cgk_origindate: null,
                    cgk_countrypostaladdressid_bind$cgk_countries: null,
                    cgk_originaddress: null
                }).execute(id => {
                });

The issue arises specifically when trying to set

cgk_countrypostaladdressid_bind$cgk_countries

to null.

Interestingly, removing this line results in the update functioning correctly. Is there a workaround or best practice for setting an id-binding field to "null" using XrmQuery?

typescript dynamics-crm crm xrmquery

Answer 1

Answer №1

If you're looking to clear lookup fields through an update-request made via the Web API, that won't work. You'll actually need to utilize a disassociate request instead. Unfortunately, at this time, the XrmQuery library does not have built-in support for associate/disassociate requests (XrmQuery documentation).

While we work on adding this functionality directly into XrmQuery (refer to issue 31), you can manually compose the request like so: As outlined in the MSDN documentation, you will need to use an HTTP DELETE request in a specific format. For nullifying lookups (referred to as single-valued navigation properties), you can set their value to null in the following manner:

XrmQuery.sendRequest("DELETE",
  "contacts(" + recordId + ")/cgk_countrypostaladdressid/$ref",
  null,
  () => { alert("success"); },
  () => { alert("error"); }
);

Answer 2

If you're looking to clear lookup fields through an update-request made via the Web API, that won't work. You'll actually need to utilize a disassociate request instead. Unfortunately, at this time, the XrmQuery library does not have built-in support for associate/disassociate requests (XrmQuery documentation).

While we work on adding this functionality directly into XrmQuery (refer to issue 31), you can manually compose the request like so: As outlined in the MSDN documentation, you will need to use an HTTP DELETE request in a specific format. For nullifying lookups (referred to as single-valued navigation properties), you can set their value to null in the following manner:

XrmQuery.sendRequest("DELETE",
  "contacts(" + recordId + ")/cgk_countrypostaladdressid/$ref",
  null,
  () => { alert("success"); },
  () => { alert("error"); }
);

xrmquery.update operation will be used to update the CRM ID binding to null

Answer №1

Similar questions

Tips for transferring information between different components through a collaborative service

find all the possible combinations of elements from multiple arrays

Enabling logging for the Mapnik SQL query while generating the map

Deploying Angular to a shared drive can be done in a

Error: Unable to dispatch a Redux-thunk action with additional arguments in React

show additional worth on the console

Material Angular table fails to sort columns with object values

Encountering a Problem with Angular 2 RC HTTP_PROVIDERS

Can we confidently disregard React's caution regarding using the useState hook conditionally if only the parameter changes based on a condition?

Incorporating Close, Minimize, and Maximize functionalities into a React-powered Electron Application

Shifting Angular Component Declarations to a New Location

How can I eliminate the white bar elements from my dropdown menu? Also, seeking guidance on replacing an empty <div> tag in a boolean query

How can one define a getter within an interface?

Executing service calls in a for loop in Angular 2 using the Http module

TypeScript failing to infer a particular data type

Encountered a specific issue with Angular 8's mat-autocomplete: "matAutocomplete" is not being recognized as a valid property of the "input" element

Issue arises when employing Higher Order Components in TypeScript

The page has been updated following a refresh

Angular 14.2.9: "Trouble with Form Data Binding - Seeking Assistance with Proper Data Population"

How can you effectively handle ngxs state changes in your component to respond to loading or error events?