Hello all,

I have set up a flow receiving messages from Navision, sending them to
a trading partner in X12 format.  As we are currently testing out this
setup, I need to be able to specify the testing flag at the end of the
ISA header segment.  (*T*>, instead of *P*> )

Currently I have not found a flag, promoted property, or a field in the
database that I can set to define this indicator.  As a temporary
solution, I created a custom pipeline component, but I am pretty sure
this should be possible out of the box.  (allthough, this EDI adapter
really is not a piece of artwork...)

Anyone has a good idea on this?

Best regards

[ Post a follow-up to this message ]

Hi Sam,

I haven't worked with the Base EDI adapter, but I have with the HIPAA EDI
adapter, for that the T/P flag is set in the send port transport properties.
I've looked at this in a Base EDI send port and don't see the same field.
You are right that flag should be configurable, considering both were
written by Covast for MS I'm guessing this was something they realized need
to be doen between the development of each.

Your pipeline comp might be the best solution, especially if you can use aa
app.config to make the flag configurable without redeploying the assemply.

- Jeff

"Sam Vanhoutte" <sam.vanhoutte@gmail.com> wrote in message
news:1136563714.761823.278820@z14g2000cwz.googlegroups.com...
> Hello all,
>
> I have set up a flow receiving messages from Navision, sending them to
> a trading partner in X12 format.  As we are currently testing out this
> setup, I need to be able to specify the testing flag at the end of the
> ISA header segment.  (*T*>, instead of *P*> )
>
> Currently I have not found a flag, promoted property, or a field in the
> database that I can set to define this indicator.  As a temporary
> solution, I created a custom pipeline component, but I am pretty sure
> this should be possible out of the box.  (allthough, this EDI adapter
> really is not a piece of artwork...)
>
> Anyone has a good idea on this?
>
> Best regards
>

[ Post a follow-up to this message ]

I suppose the app.config idea would only work if you wanted all projects
using this pipeline comp to use the same flag, that seems unlikely, oh well.

"Jeff Wessling" <jeff.wessling@qualifacts.com> wrote in message
news:uqHATuVFGHA.3172@TK2MSFTNGP10.phx.gbl...
> Hi Sam,
>
> I haven't worked with the Base EDI adapter, but I have with the HIPAA EDI
> adapter, for that the T/P flag is set in the send port transport
> properties. I've looked at this in a Base EDI send port and don't see the
> same field. You are right that flag should be configurable, considering
> both were written by Covast for MS I'm guessing this was something they
> realized need to be doen between the development of each.
>
> Your pipeline comp might be the best solution, especially if you can use
> aa app.config to make the flag configurable without redeploying the
> assemply.
>
>    - Jeff
>
> "Sam Vanhoutte" <sam.vanhoutte@gmail.com> wrote in message
> news:1136563714.761823.278820@z14g2000cwz.googlegroups.com... 
>
>

[ Post a follow-up to this message ]