Virtual entity update of a boolean value failing using the SQL Server Connector

(5) Share

Report

Posted on by CU17021610-0

We have multiple virtual entities connected to SQL Server tables via the SQL Server Connector, and we have been successfully updating records for a number of months.

Following a recent solution update from Microsoft to the Microsoft.Xrm.DataProvider.Connector.Plugin, we can't update a record if we reference a boolean field in the JSON (using Xrm.WebApi.updateRecord from javascript) - the MS plugin throws an error:

"Object of type 'System.String' cannot be converted to type 'System.Nullable`1[System.Boolean]'"

If we update without the boolean field, it works correctly.

Sample code:

        var record = {};
        var newRecordId = "<GUID HERE>";
        record.exampleBoolean = true;
        record.exampleText = "Test Text";
        var updateResult = await Xrm.WebApi.updateRecord("new_virtualentity", newRecordId, record);

Anybody else experiencing this or know of a workaround? (Ticket has been raised with MS)

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

Holly Huffman 6,538 Super User 2025 Season 2 on at

Like (1)

Report
hi there! apologies if youve already done these:

Check Data Types: Ensure that the boolean field in your SQL Server table is correctly defined as a bit data type. Verify that the field in the virtual entity is mapped correctly to the boolean field in the SQL Server table.

Update JSON Payload: Sometimes, the issue can be related to how the boolean value is being passed in the JSON payload. Ensure that the boolean value is being passed as true or false and not as a string.

Example:

javascript

var record = {}; var newRecordId = "<GUID HERE>"; record.exampleBoolean = true; // Ensure this is a boolean, not a string record.exampleText = "Test Text"; var updateResult = await Xrm.WebApi.updateRecord("new_virtualentity", newRecordId, record);

Use Alternate Methods: If the issue persists, consider using alternate methods to update the boolean field. For example, you can use a custom API or a Power Automate flow to update the field

Was this reply helpful? Yes No
Verified answer

CU17021610-0 24 on at

Like (1)

Report

Just had the issue resolved by Microsoft on our environments, and a general fix will be released "in the next few weeks". Unable to clarify the nature of the fix (it was a "known issue") but as nothing was done to our SQL boxes it seems it was a backend fix to the connector or power platform.

Was this reply helpful? Yes No