- This topic has 2 replies, 1 voice, and was last updated 8 years, 4 months ago by
.
-
Posts
-
-
In BizTalk 2009 Enterprise 64-bit, running on Windows Server 2008 Standard 64-bit, and connecting to CRM 4.0 we are getting an error while trying to update two datetime fields in CRM.
<ReturnCode>0</ReturnCode>
<ErrorCode>0x80040203</ErrorCode>
<ErrorString>serializedForm :: Server was unable to process request.</ErrorString>
<Retryable>0</Retryable>We have tried a number of different functoids in the mapping, including IsNill->Logical Not, Logical Date, Logical String, Logical Existence, all of which went into a Value Mapping functoid which then went to the values in the CRM update schema. I have also tried a scripting functoid that would return an empty string (both return “”; and return String.Empty;) and none of them have worked. The only way we’ve gotten this to work so far is to put in a default value, or not include them in the update.
We are updating the account entity, and since these two fields need to be updated, we can’t just exclude them from the update. Not every account has to have a value for these either. In CRM they are not required, and have no default value. We have an existing Scribe job that handles these updates right now, and it doesn’t have any issues updating using null values.
An example of what we are doing, and how it pans out is…
The account entities are actually dealers for our company, so one of the datetime fields is when they started as a dealer with us. An account does not have to be a dealer to exist in CRM, they can still be a prospective dealer. If an account is a prospect, then there is obviously no date for when they started as a dealer with us, so the value would be null. The other datetime that we are trying to update is along similar lines.
Any help on this issue is greatly appreciated.
-
Hi,
Check out the following MSDN blog that gives a walkthrough on how to update data in the CRM system from BizTalk using the CRM adapter:
The example showcases version 3.0 of the adapter but I think it’s still applicable to version 4.0.
Daniel
-
The solution turned out to be relatively simple (yet I never found it anywhere online for some reason…)
I set up some functoids in the map that used the logical date
functoid, and if it was a logical date, then a Value Mapping functoid
sent the value to the datetime field. The logical date functoid also
went to a logical NOT functoid which then went
to two Value Mapping functoids. the first value mapping functoid
returns the date of 1901-01-01 to the datetime field, and the second one
simply returns the constant true and goes to the IsNull attribute in
the datetime field in the destination schema.Summed up, I never found anywhere that said the datetime field needed
to have a valid date in it in order to set IsNull = “true” for it to
work…
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.