BizTalk SOA Evangelist

Hi,

Whenever you create an schema using "Add Generated Metadata" and then you use promotion for the required elements sometimes you may receive this error. Baiscally, it means that the XML in the message doesn't contain the entire path to the element that the distinguished field points to. Thus you need to clearly verify that when you initialize the multipart message, make sure that field names are same. Since they are case sensitive so you need to take care that case is same as you have in the generated schema.

I receive the same because of the case problem.

Incorrcet Expression: 

// Intialize the SQL Request message

In multiple partner scenario who are sedning either similar or multiple EDI messages it is suggested to use Direct Binding.

Using Direct binding you can set the filter conditions at the Receive port. Thus as soon as the message is published to the Database depending on the filter condition the message will be picked up and processed.

For the party data validations you can extract ISA properties using BizTalk EDI context properties and compare them against the party configurations values stored in the EDI DBs.

Regards

Vishnu

Hi,

You may receive this error in the scenario when you add a schema using the "Add Generated Metadata"  and you promote the attribute or elements either as distinguished or as property promoted. Now when you are assigning any value or doing any comparison where the type or the distinguished field is to be changed "YOU WILL RECEIVE THIS ERROR".

Resolution: You need to use this paramter as below : --

InCorrect:

sbExMessage.Append("\n\nError Code: " + Msg_SQLResponse.parameters.Response.ErrorCode);

Correct:

sErrorCode = Msg_SQLResponse.parameters.Response.ErrorCode;

Regards

Vishnu