v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
Normal
0
false
false
false
false
EN-AU
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,”sans-serif”;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:”Times New Roman”;
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
system 1, sends me an update of some information, from time to time, about a
user, this information needs to be instantly replicated into SharePoint.
near real time, so
that consumes a WCF Service.
the schema s are useful, the orchestration you can choose to use it or not, it
contains a bunch of multi-part message types,
and a massive port for every single method.
it contains the operations, you will need to use when you create the port, so
one port can have many operations to the same web service, they give you the
binding for this port, which is very nice, I suggest you use it.
stuff begins. If you use this, it does not work.
<soap:Envelope
xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xmlns:xsd=”http://www.w3.org/2001/XMLSchema”><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Server
was unable to process request. —> Invalid String Value: Input must
match string data type.</faultstring><detail
/></soap:Fault></soap:Body></soap:Envelope>
a string..
in here, which is correct, I want to, a string, a datetime, a int. So the
schema is flexible
name=”ValueData”>
minOccurs=”0″ maxOccurs=”1″ name=”Value” />
does not specify a type BizTalk interprets this, bad sharepoint.
let down when you have gotten past the authentication issue to find this. See
my other post to fix this.
find out why it works, you look at the xml that this call generates:
xsi:type=“xsd:dateTime“>2012-06-25T10:01:17.486123+10:00</Value> </ValueData>
uppercase V, BizTalk puts is with a lower case V. so that’s the first fix.
schema, it’s not going to happen.
however it’s coming up as:
because it cannot interpret the type.
BizTalk pipelines I can touch up the message before I send it to SharePoint.
!!
the user profiles.