07-28-04 11:09 PM
Hi Yossi, thanks for your reply.
Yes, the element was defined as a promoted property in the schema, so it loo
ks like this was the issue. It makes sense in having this limitation in or
der not to degrade performance.
Thanks again.
Cheers.
"Yossi Dahan" wrote:
> Did you define this element as promoted property in the schema? I'm not su
re
> but this might be the case as there is a 255 characters limitation on
> promoted properties
>
> Yossi
>
>
> "TokBoy" <TokBoy@discussions.microsoft.com> wrote in message
> news:C15B098E-07B1-4B9A-BFF9-AA276FCCA021@microsoft.com...
> orchestration when trying to assing a large string value (greater than 256
> characters in length) to an element within my xml message which is defined
> within the schema as being xs:string type.
> to hold large strings? Or is it something to do with the way I am assigni
ng
> the value?
>
>
>
[ Post a follow-up to this message ]
|