Set ISN not working anymore.

[Gosse-N]

Hello,
As of yesterday ( 2025/01/21) I noticed that the Set ISN features doesn't work anymore.
It worked fine last week.
I'm using version 1.2024.10.1 of the tool. I tried reinstalling it and deleting every metadata and cache related to BDU but same result.

Can someone test on their side? To confirm that it's not just a local issue then I will open an Issue

Thanks

[rappen]

I tested it here, and it works fine.
Can you provide the actual error?
Can you also find the version of the Dataverse (found in the PP Admin Center, in the environment) - mine has version 9.2.24122.178 where it works.

[Gosse-N]

Dataverse version: 9.2.24123.230

I don't have any error, that's what I don't understand. No custom logic on this field neither.
I did a test again this morning and same result. For that record we can see that a previous update with BDU did update the ISN.

Here the update done in BDU:

The actual ISN after the update:

The audit log of the record. The mobile phone update is the one made with BDU. We can see the previous update on the 16th of january made with BDU that correctly set the ISN:

The log of BDU for that update:

<?xml version="1.0" encoding="utf-8"?> <BDULogRun xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <TimeStamp>2025-01-21T16:22:30.0689635+01:00</TimeStamp> <Action>Update</Action> <EntityLogicalName>contact</EntityLogicalName> <EntityDisplayName>Contact</EntityDisplayName> <DurationMS>1422.0677</DurationMS> <Records>1</Records> <Errors>0</Errors> <Requests> <BDULogRequest> <TimeStamp>2025-01-21T16:22:30.3104389+01:00</TimeStamp> <No>1</No> <Request>Update</Request> <Id>daba374e-72e6-43b1-86f8-7b91c09911a7</Id> <DurationMS>1176.0834</DurationMS> <Success>true</Success> <Records> <BDULogRecord> <Id>ce91c58d-6de5-eb11-bacb-000d3ab1153a</Id> <Name /> <Attributes> <BDULogAttribute> <LogicalName>birthdate</LogicalName> <DisplayName>Date of Birth</DisplayName> <Action>Touch</Action> <OldValueKnown>false</OldValueKnown> </BDULogAttribute> <BDULogAttribute> <LogicalName>bd_language</LogicalName> <DisplayName>Langue</DisplayName> <Action>Set</Action> <NewValue xsi:type="OptionSetValue"> <Value>899240000</Value> </NewValue> <NewValueString>FR</NewValueString> <OldValueKnown>false</OldValueKnown> </BDULogAttribute> <BDULogAttribute> <LogicalName>importsequencenumber</LogicalName> <DisplayName>zzzImport Sequence Number</DisplayName> <Action>Set</Action> <NewValue xsi:type="xsd:int">250121675</NewValue> <NewValueString>250121675</NewValueString> <OldValue xsi:type="xsd:int">250116466</OldValue> <OldValueString>250116466</OldValueString> <OldValueKnown>true</OldValueKnown> </BDULogAttribute> </Attributes> </BDULogRecord> </Records> </BDULogRequest> </Requests> </BDULogRun>

BDU_Update_contact_20250129_114504 - PrivacyEdited.log

At time of my post I had someone else test it on the same environment and he had the same issue.

Sorry, it took me a while to get back to you.

Thanks for your help!

[rappen]

Weird it is... I now have the same problem.
And now my environment is up to your version.
It might that MS has finally blocked it, only 15 years later since that fiels was introduced (CRM 2011 - and probably was there in CRM 4.0 and earlier).
We see that the metadata says it can't be updated, but it has worked forever.

I will contact folks at MS to see if they understand it and can explain to us.

[Gosse-N]

Thanks for the quick feedback.
I guess we will need to rely on a custom field if they don't change it back.
I just got unlucky and the update happened during a bulk update so I was puzzled as to why some records were not processed by BDU (Was only doing a touch so ISN was the only trace I had).

Curious to hear their reasoning for finally blocking it.