« Return to Thread: Error Assign activity: selectionFailure; Fault Data is null

Re: Error Assign activity: selectionFailure; Fault Data is null

by Wouter van Reeven :: Rate this Message:

Reply to Author | View in Thread

Hi Romano,

On Mon, Jun 02, 2008 at 03:47:55AM -0700, Romano Londt wrote:

> While looking at the messages I noticed that the <record> tag was not used
> inside the messages.
> When rewriting the xsd from
>
>
>      <xsd:element name="TEST1" type="TEST1"></xsd:element>
>      <xsd:complexType name="TEST1">
>        <xsd:sequence>
>          <xsd:element maxOccurs="unbounded" ref="record"></xsd:element>
>        </xsd:sequence>
>      </xsd:complexType>
>      <xsd:element name="record">
>        <xsd:complexType>
>          <xsd:sequence>
>          </xsd:sequence>
>        </xsd:complexType>
>      </xsd:element>
>
> To:
>
>     <xsd:element name="TEST1" type="TEST1"></xsd:element>
>     <xsd:complexType name="TEST1">
>         <xsd:sequence>
>         </xsd:sequence>
>     </xsd:complexType>
>
> I got data in my assign activity.
>
> Can anyone verify if my action is "legal" and does not have any negative
> sideeffects?

AFAIK rewriting the xsd as you did above (with the lines I deleted for clarity
included again) you now only expect ONE element inside your TEST1 element
instead of 0, 1 or more. Not sure why the first xsd doesn't return any data...


HTH, Wouter van Reeven

--

People: "If she weighs the same as a Duck, she's made of wood!"
Sir Bedevere: "And therefore...?"

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: Error Assign activity: selectionFailure; Fault Data is null