I am developing in Biztalk 2004 and have an Orchestration that receives an
xml message the have Customer, Order, and Order Details nodes.  I need to ma
p
each level to separate flat files (Customer, Order and order Details).  I
have this working with three separate maps in its own transform shape.  Afte
r
all three transform shapes, I have three send shapes sending each individual
file.

If one of the maps fail how do I stop the other two from writing out the
flat file?

In the Order loop, I change one of the dates to be invalid.  by debuging in
the orchestration, the map creates the xml destination message, but I get an
error on the send port.  If this occurs I do not want to write the other two
files.

[ Post a follow-up to this message ]

Let's try to divide an orch to three orchs.
Or you can write the C# method to check the event log. If in it you got an
event then don't do next mapping

--
Regards,

Leonid Ganeline,
BizTalk Developer
Vancouver
http://public.fotki.com/leogan/

"Curtis Vasbinder" <curtisv@newsgroup.nospam> wrote in message
news:4B52CB04-50BD-4620-AD8F-79BEC3D1869C@microsoft.com...
>I am developing in Biztalk 2004 and have an Orchestration that receives an
> xml message the have Customer, Order, and Order Details nodes.  I need to
> map
> each level to separate flat files (Customer, Order and order Details).  I
> have this working with three separate maps in its own transform shape.
> After
> all three transform shapes, I have three send shapes sending each
> individual
> file.
>
> If one of the maps fail how do I stop the other two from writing out the
> flat file?
>
> In the Order loop, I change one of the dates to be invalid.  by debuging
> in
> the orchestration, the map creates the xml destination message, but I get
> an
> error on the send port.  If this occurs I do not want to write the other
> two
> files.

[ Post a follow-up to this message ]

Hi,

You can add Scope shape and Catch Exception block in your orchestration to
catch the exception thrown from the mappings (e.g:
Microsoft.XLANGs.Core.XTransformationFailureException). If any of the
Transform shapes fails, you can do some exception handling like stopping
the current orchestration instance, deleting the other 2 generated files ,
etc.

Here are some references:

Catch Exception Block
http://msdn.microsoft.com/library/d...-us/sdk/htm/ebi
z_prog_orch_rouy.asp

Using BizTalk Orchestration Shapes - Error Handling
http://www.netologi.se/default.aspx...ionShape

s

Please update here if you have any further questions or meet any problems.

Have a nice week.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

Have a parallel shape place your map on each activity if all the transform
is done then it call the next step in the process otherwise its throws an
execption. that should take care.

Ren


""WenJun Zhang[msft]"" wrote:

> Hi,
>
> You can add Scope shape and Catch Exception block in your orchestration to
> catch the exception thrown from the mappings (e.g:
> Microsoft.XLANGs.Core.XTransformationFailureException). If any of the
> Transform shapes fails, you can do some exception handling like stopping
> the current orchestration instance, deleting the other 2 generated files ,
> etc.
>
> Here are some references:
>
> Catch Exception Block
> [url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sdk/htm/ebi[/ur
l]
> z_prog_orch_rouy.asp
>
> Using BizTalk Orchestration Shapes - Error Handling
> [url]http://www.netologi.se/default.aspx? Contents=BizTalk_UsingOrchestrationShape
[/ur
l]
> s
>
> Please update here if you have any further questions or meet any problems.
>
> Have a nice week.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>

[ Post a follow-up to this message ]

Hi,

Will it work for you if you combine all the 3 maps into a single map
having aggregate schema as the output.

[ Post a follow-up to this message ]