BizTalk 2010 Error Encountered During Parsing HIPAA 5010 Transactions

Hello,

Last week I was testing the parties after configuration on a BizTalk 2010 server for HIPPA 5010 transactions. I was facing the following error with one of the parties:

Error:

Error encountered during parsing. The X12 interchange with id ’000000001′, with sender id ’9999999 ‘, receiver id ’1111111 ‘ had the following errors:

Error: 1 (Miscellaneous error)

16: Invalid Control Standard Identifier

Error: 2 (Field level error)

SegmentID: ISA

Position in TS: 1

Data Element ID: ISA11

Position in Segment: 11

Data Value: ^

7: Invalid code value

I checked the party settings, everything was looking fine but still I was getting the error.

We know that ISA11 can be used in X12 as a standard identifier or a repetition separator and if we want to use as a repetition separator then we need to check the Envelop value. I did the same but still getting the error.

Then I changed the property of UseIsa11AsRepetitionSeprator value to TRUE, EDI disassembler stage in the pipeline component and it worked.

- Ratikant Pawar

Error – Failed to Initialize Windows Azure Storage Emulator

Hello,

The Windows Azure SDK development environment includes the storage emulator, a utility that simulates the Blob, Queue, and Table services available in Windows Azure on your local development machine. If you are building a hosted service that employs the Windows Azure storage services, or writing any external application that calls the storage services, you can test your code locally against the storage emulator.

By default the Windows Azure storage emulator on local machine works with a SQL Server Express instance which needs to be named ‘SQLExpress’. But in the event that ‘SQLExpress’ is not installed or enabled on the local machine then it gives following error in Visual Studio when you try to debug Windows Azure project:

failed-to-initialize-windows-azure-storage-emulator-error-nimbo

If you look into output window in visual studio, the detailed message will look like this:

Windows Azure Tools: Failed to initialize Windows Azure storage emulator. Unable to start Development Storage. Failed to start Development Storage: the SQL Server instance ‘localhost\SQLExpress’ could not be found. Please configure the SQL Server instance for Development Storage using the ‘DSInit’ utility in the Windows Azure SDK.

The first time you run the Windows Azure storage emulator, an initialization process runs to configure the environment. The initialization process creates a database in SQL Server Express. You can use the DSInit command-line tool to configure the storage emulator to run against a local instance of SQL Server, rather than against SQL Express.

Note: You’ll need to have SQL Server installed and running on your machine for this to work.

To use SQL Server instead of SQL Server Express for Windows Azure storage:

  1. Click Start, point to All Programs, and then click Windows Azure SDK v1.4
  2. Right-click Windows Azure SDK Command Prompt, then click Run as Administrator
  3. In the Windows Azure SDK Command Prompt window, type the following command: DSInit /sqlInstance:<SQLServerInstance>
  4. Note: >SQLServerInstance< is the name of the SQL Server instance without the (< >)’s
    Note: You can also use the following command, which uses the default instance of SQL Server: DSInit /sqlInstance:.

An example of the steps above is shown in the image below:

windows-sdk-command-prompt-dsinit-sqlinstance-command-nimbo

Once you complete these steps, you shouldn’t have any issues debugging (or starting) a project in your development environment for Windows Azure. Have a look at a successful Development Storage Initialization shown in the image below.

development-storage-initialization-successful-windows-azure-nimbo

If you wanted to take a look at the database, just open up SQL Server Management Studio and look at the database that’s created. For this example, a database was created with the name DevelopmentStorageDb20090919 – although yours may be different.

The information above is displayed in the image below:

new-database-development-storage-windows-azure-created-nimbo

- Pravin Jape

How to Use the ADO.NET Entity Data Model Designer (Entity Designer) to Import a Stored Procedure

Hello,

In this article, I will describe how to use the ADO.NET Entity Data Model Designer (Entity Designer) to import a stored procedure.

When a stored procedure is added to a conceptual model, it is called a function import. Adding a function import allows you to call the corresponding stored procedure from your application code. A function import can return collections of simple types, EntityTypes, ComplexTypes, or no value.

When the Entity Data Model Wizard generates an .edmx file from a database, it creates entries in the storage model for each stored procedure in the database. Corresponding entries are added to the conceptual model when function imports are created.

Creating a Function Import

The procedure below describes how to create a function import. For information about calling a function import from application code:

  1. Right-click the Function Imports folder (in the EntityContainer node of the conceptual model information) and then select Add Function Import.
  2. The Add Function Import dialog box appears.
  3. The steps above are displayed in the image below.

  4. Fill in the settings for the new function import
    • Specify the stored procedure for which you are creating a function import in the Stored Procedure Name field. This field is a drop-down list that displays all the stored procedures in the storage model. If the desired stored procedure is not available, you may need to update your storage model
    • Specify the user defined name of the function import in the Function Import Name field.
    • Specify one of the four basic return types: None, Scalars, Complex, or Entities, and select the specific return type from the available drop-down list.
      1. None: specifies that function returns nothing.
      2. Scalars: specifies that function returns scalar value.
      3. Entities: specifies that faction returns entity type value.
      4. If you choose Complex, the Entity Designer can create a new complex type with properties that correspond to the columns returned by the stored procedure.
        • Click Get Column Information to retrieve column information.
        • Click Create New Complex Type.
        • Edit the name of the complex type in the Complex drop-down list
    • (Note: When you click OK, a new complex type is added to the conceptual model and the return type of the function import is set to this new type.)

  5. Click OK. The FunctionImport entry is created in the conceptual model.

How to Use the Imported Function in an Application using C#

The following information described how to use the imported function an an application using the C# programming language:

The following code executes a check_Login stored procedure where userid is a required parameter.

// Specify the userid.
// SchoolEntities used here is reference for entity name. 

int userid = 2;
SchoolEntities context = new SchoolEntities();
If(Context.check_Login(userid)>;1);
{
Console.WriteLine (“userid: ” + userid);
Console.WriteLine (“User exists. “);
}

- Pravin Jape

Hello From the Nimbo India Office!

We thought we’d introduce you to some of the wonderful team members in our India office.

From left to right: Ratikant Pawar, Amol Kudke, Soujanya Vangapelli, Ganesh Kashid, & Pravin Jape.

- Kristine Drier