Forum Replies Created
-
Posts
-
Henry,
are you sure it's a general capability? I only remember it with the WSS Sharepoint adapter.
John D.
Larry,
BizTron's idea seems pretty good.
I was thinking (a) a map with a functoid, or (d) a custom pipeline component – both very heavy for what you want. You could also do it in an expression shape, I guess.
When you actually put the value in the database you could also fix it then.
John D.
ok thanks,
but what does it mean that Standard Edition is limited to 10/20 external trading partners?
Is it the number of parties I can define in the administration console?
As I understand these schemas (which has been very little up to now) there is "supposed" to be a standard format/schema and then a section of possible custom data. The trick in this case is to read the standard data the same way in every case but then pass the rest of the data according to another set of rules, say pass thru. However, in practice, as I've heard several Mainframe folks claim that the standards are rarely followed and new ones are created depending on which way the wind blows.
That said. I'll keep this issue in mind and review some internal work to see if I can find anything. I'm interested in a solution as well.
Esentially you're looking to do .NET interop on your "legacy" code. If it's not managed .NET, you're looking for a way to make BizTalk see it that way. How are you planning on using the code? Is this something complex that could use an adapter, or something simple that could be rewritten? Or somewhere in between?
I've found many ways to avoid calling libraries directly, and even created simple custom functoids with little effort vs. calling a library from an Orchestration. But, I'd want to know more about your plans before I made a serious suggestion.
That's probably right, but what version of Excel document do you have? I've seen a lot of custom work in the past using XML to represent Office metadata, but also, perhaps a conversion to an XML version of the document could help. Just a simple suggestion from the hip. I'd have to try it before I'd stand behind it though. 🙂
okay i promoted the values, enlisted the orchestration and BAM it works ^^ thanks for your help guys
So i played a littlebit around and get new error messages… the ones i got for the passThru pipeline …
i testet the flatfile disassembler with the pipeline tools and that worked so it seems like the schema and input file work correct together
In simple form my Flatfile looks like this
<CustomerID>;<ProductID>;<Productname>;<andSoOn>;
<CustomerID>;<ProductID>;<Productname>;<andSoOn>;
<CustomerID>;<ProductID>;<Productname>;<andSoOn>;
…
my schema looks like this
<Schema>
– ClaimList
– Claim
– CustomerID
– ProductID
– Producname
– andSoOn
max occurs are set to 1 so it breaks down the flatfile to several messages.
Then it comes to an orchestration where the values are mapped to another schema and then thex come to the sendport (also File)
The Pass Thru won't work, so any error messages you receive are expected.
- What do your flat file and flat file schema look like?
- What are you doing with the results of your receive port?
- Are you using an Orchestration, and if so, how?
In other words, what did you build to get to the point you are at now?
I cleared out the messages but the error is everytime the same. I now tried to go with the passThru pipeline and got 2 rooting error messages
This service instance exists to help debug routing failures for instance "{C1B592AA-DF19-4465-AAF6-B3390C00BC7E}". The context of the message associated with this instance contains all the promoted properties at the time of the routing failure.
and
The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.
Maybe this gives a hint what is wrong…
Concerning the configuration, to be honest i don't know which information i should post…
You can use a not equal (<>) functoid, and a value mapping functoid.
- Drag a line from the source element or attribute to the <> functoid.
- Create a constant in this functoid, but leave it blank.
- Drag a line from there to the value mapping functoid, as it needs to use the logical as its first connection.
- Now connect the same source element or attribute to the value mapper.
- Then from there to the output schema element.
- (And be sure the output element is nilable/optional.)
Have you tried this? Let me know if it doesn't work as expected and we can check a few properties.
This does assume you have 2 schemas. There are other ways to accomplish this, but this, I believe, makes the most sense.
