Forum Replies Created
-
Posts
-
Hello.
I’m assuming the records will always be in order and it is either 1 record or two.
In the past, we use the code below to compare the current value with the past value. It would return true (for them being the same) or false (if different).
You can use a scripting functoid with code like this to return true or false:
string sPastValue = \”\”;
string bReturn = \”\”;public string M1(string param1)
{
if (sPastValue!= param1)
{
sPastValue = param1;
bReturn = \”true\”;
}
else
bReturn = \”false\”;return bReturn;
}
This will let you know what type of mapping you need for the record. Then you can use conditional logic to map or add as needed. For the addition, I might try to use the Index functoid along with a counter in the above script to extract out the two values to add together.
Another option would be to use pure custom XSLT. I would think this would be doing using position() and position()-1 to check values and add them.
I would start in this order and work piece by piece:
Map the whole record as normal using the mapper using a looping functoid
Get the 6 replaced with a 4 on the correct row by using conditional logic
Get the sum to workMapper logic is hard to explain in a message and I find playing around with it is something the best way to figure it out.
Hope this helps.
Yes, that is correct.
When you build the Orchestration it will build to a specific version. This allows for multiple versions of the same assembly to be in the GAC (a.k.a. side by side versioning).
Are you changing your version on purpose?
If not, one simple thing to change is make the version of the .net component static. In the AssemblyInfo file, change the version from 1.0.* to 1.0.0.0. Then, when you build it you keep your same version number and do not need to rebuild the Orchestration. You just need to re-GAC the .net component and restart the hosts.
Hope this helps.
Thanks,
What you said didn’t exactly work but it got me going in the right direction. I ended up using a looping function with the two input params (Value1 and Value2) and the output going to the Detail node. then I mapped Value2 and Value2 to the Value node and the Number straight across.
Some things to check or at least think about:
– make sure the user accounts you are using for setup are in the correct user groups
– if you are doing a multi computer install you are using domain accounts like domain\\name
– if you are re-running the installation make sure all the databases and user accounts that were automatically created have been removed
– you have all required components installed
– you have not installed any beta software (like Biztalk 2006, VS 2005, .net 2.0) on the computer prior to installing BiztalkIt almost sounds like something might not have gotten installed correctly? If nothing else works, you might want to uninstall and reinstall Biztalk 2004.
Hope this helps.
Base Edi does not have this information.
You should use full Covast EDI Accel.
http://support.microsoft.com/default.aspx?scid=kb;en-us;840113
Here is a quote from Microsoft on Base EDI limitation (Covast wants you to buy the full version:))
Miscellaneous EDI schema limitations
No floating segment support. This limitation is the same as in Microsoft BizTalk Server 2002.
Very limited binary segment support. This limitation is the same as in BizTalk Server 2002.
[b:f69c076ace]EDI Envelope data is not conveyed on the inbound. Therefore, the data is not available for use in the BizTalk Mapper or in orchestrations. This limitation is the same as in BizTalk Server 2002.[/b:f69c076ace]
EDI Envelope layouts cannot be customized or modified. This limitation is the same as in BizTalk Server 2002.
The list of supported X12 Functional Group Identifiers is fixed according to the 4050 version. This means you cannot use transaction sets that were introduced after the 4050 version, because the system does not know which functional group identifier belongs to it (because that is not part of the schema).
The EDI Annotation <b:RecordInfo count_ignore=\”yes\”> is ignored by the Base EDI Adapter. The Base EDI Adapter uses hard-coded technology to count the segments in EDI transactions.
The BizTalk Server 2004 Base EDI Adapter uses stricter EDI character set validations than BizTalk Server 2002. For example, when an EDIFACT UNOA interchange is received, it will validate the characters in the interchange according to the defined character set that belongs to the UNOA syntax (which is a subset of ISO-646).
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:I used covast edi for biztalk a lot.
The incoming 850 is translated to xml by covast edi accelerator.
I have seen the header for the ISA and it has the partner id (sender).You are using base EDI biztalk right?
Maybe the base edi don’t have it. In the Covast EDI schema, there is a thing called CovastEnvelopeLook for it even if you are using the base EDI.
If not, then go to Covast website and send an email and ask. They wrote the Base EDI too.
That should not be a problem with Biztalk 2006 Beta 1. I have not actually tried it but I have not heard of anything having problems with it.
I run mine on a Windows 2003 VPC through.
I don’t think you will see any improvements in that area in 2006. We may have to wait until 2008 on that one. Best of luck with the custom functoid.
Stephen,
I have thought about that since posting. You can create a Custom Functoid using .NET classes, by inheriting from the Microsoft.BizTalk.BaseFunctoids class. There’s a sample in the SDK that comes with BizTalk 2003 -but it’s not a database sample.
Ideally it would be great if you could inherit from the standard database functoid, then add another input for a second datase column, but I can’t see any example code that shows how to construct such an input. So I’m a bit stuck.
I hope they have extended this area in the new 2006 version !
-John
Hello.
I don’t know of a way around it.
Could you call a custom .net component inside the map to return your data?
I’m having a bit of trouble with a map I’m working on and wondering if anyone can shed some light on this.
I’ve got a source document where I need to take the data under a given node and map it to two or more nodes in the destination.
For example:
The source doc is:
<Header>
<Customer>ABC</Customer>
<Date>1/1/2005</Date>
<Details>
<Detail>
<Value1>A</Value>
<Value2>B</Value>
<Number>100</Number>
</Detail>
</Details>
</Header>I need to end up with:
<Header>
<Customer>ABC</Customer>
<Date>1/1/2005</Date>
<Details>
<Detail>
<Value1>A</Value>
<Number>100</Number>
</Detail>
<Detail>
<Value>B</Value>
<Number>100</Number>
</Detail>
</Details>
</Header>I just can’t seem to figure out how to get Biztalk to create 2 detail records from one.
Any help would be greatly appreciated.
Hello.
That can not really be done inside an Orchestration.
But, you would use Content Based Routing and Orchestrations with the Rules Engine to achieve something close to dynamic workflows. Each message would have properties set on it what would route it to the correct “next step” in the process. Then, at the end it will run through the rules engine again to see where to go next.
I saw a demo using this by a Microsoft guy. It was awesome.
Hope this helps.
Fab,
I would check a couple of things.1 – Make sure that the adapter is installed correctly. Have you tried a very simple example with the adapter just to verify it works?
2 – make sure you have the pre-req’s installed. SQLXML 3.0 would be the key one.
3 – What does your stored proc look like? Have you verified you are not maybe returning an unsupported type, etc? Does the stored proc work outside of the adpater?
Todd
