Microsoft Dynamics NAV Team Blog

Equisys extends platform support for Zetadocs Express for Microsoft Dynamics NAV

navteam — Tue, 14 May 2013 12:00:00 GMT

Latest release adds support for further Microsoft platforms, including 64-bit editions of Outlook

Equisys are pleased to announce that platform support for ZetaDocsExpress for Microsoft Dynamics NAV has been extended to include Windows 8, Windows Server 2012, SharePoint 2013 and the 64-bit editions of Microsoft Outlook.

First launched in October 2011, Zetadocs Express is the downloadable document management module of Microsoft Dynamics NAV. It is available at no additional cost to NAV users on a Business Ready Enhancement Plan.

Zetadocs Express is designed to save finance teams time and money by providing three essential document management capabilities directly within Microsoft Dynamics NAV:

Drag and drop: Any file, email or attachment onto a record in the NAV Windows client to automatically store it in SharePoint. Documents are linked to their NAV record and listed in the Documents FactBox when the record is viewed.

Document approval: Initiate simple SharePoint workflows for any document listed in the FactBox – such as an invoice – and monitor the approval status in NAV.

Save and send NAV reports: Click the “Save and Send” button to email almost any customized NAV reports in PDF format. Delivered documents are archived automatically in SharePoint and listed in the Documents FactBox for future retrieval on-screen.

Speaking of the new release, Zetadocs for NAV Product Manager, Greg Cole, said, “As the foundation edition of our document management family, Zetadocs Express is a great introduction to the time-saving potential of our Zetadocs solutions.

“Since its launch, we have continued to receive great feedback from partners and customers alike, so I’m delighted to broaden the number of supported platforms even further.”

Zetadocs Express is available to users of Microsoft Dynamics NAV 2013 or Microsoft Dynamics NAV 2009 R2, with an active Business Ready Enhancement Plan. To download the latest version of Zetadocs Express, visit CustomerSource or PartnerSource.

Best regards,

The Microsoft Dynamics NAV team

Best Practices Analyzer for Microsoft Dynamics NAV 2013

navteam — Tue, 30 Apr 2013 10:00:00 GMT

The Best Practices Analyzer for Microsoft Dynamics NAV 2013 is a tool for identifying issues that can prevent you from successfully deploying a three-tier environment of Microsoft Dynamics NAV 2013. A three-tier deployment is one where the client, Microsoft Dynamics NAV Server, and SQL Server are installed on separate computers. These deployments can be challenging because they often require additional domain administration tasks. The tool is relevant whether the client is a RoleTailored client or a Web services client.

The Best Practices Analyzer for Microsoft Dynamics NAV 2013 performs the following verifications:

Verifies that an appropriate version of Microsoft Dynamics NAV Server is installed. Only Microsoft Dynamics NAV 2013 is supported.
Verifies Microsoft Dynamics NAV connection strings.
Verifies that the Microsoft Dynamics NAV Server service, the Microsoft Dynamics NAV Web services service, and the SQL Server service, which are required for Microsoft Dynamics NAV, are running.
Checks database permissions to make sure that the required resources can connect to the database.
Verifies that the necessary service principal names (SPN) have been created and correctly configured on the account that is running the Microsoft Dynamics NAV Server service.

You can find more information about the tool and download it from CustomerSource here or from PartnerSource here.

Best regards,

The Microsoft Dynamics NAV team

Announcement of new hotfix process for Microsoft Dynamics NAV 2013

Susanne Priess — Sun, 28 Apr 2013 19:43:00 GMT

Today we have released an update rollup that includes all application and platform hotfixes that have been released for Microsoft Dynamics NAV 2013. The update rollup includes hotfixes that apply to all countries and select local versions.

Going forward, we will release monthly update rollups instead of individual hotfixes.

What is an update rollup

An update rollup is a cumulative set of files that includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013, including hotfixes and regulatory features released in previous update rollups.

Where to find the update rollups

You can download the first update rollup from KB 2829782 - Update Rollup 1 for Microsoft Dynamics NAV 2013 (Build 34587). The hotfixes that are included in this update rollup are listed in the KB article.

You can find a list of all update rollups released for Microsoft Dynamics NAV 2013 in KB 2842257 - Released update rollups for Microsoft Dynamics NAV 2013.

You can find a list of all hotfixes included in update rollups for Microsoft Dynamics NAV 2013 on the following CustomerSource and PartnerSource pages:

CustomerSource

PartnerSource

Which countries are included in the update rollups

The first update rollup includes hotfixes that apply to all countries (W1) and local hotfixes for Germany (DE). Future update rollups will include local hotfixes for the following countries:

DE - Germany
DK - Denmark
FR - France
IT – Italy
NA – North America
NL - Netherlands
UK – United Kingdom

Local hotfixes for the following countries will not be included in update rollups:

AT – Austria
AU - Australia
BE - Belgium
CH - Switzerland
ES - Spain
FI - Finland
IN – India
IS – Iceland
NO - Norway
NZ - New Zealand
SE - Sweden

Instead, we will continue to release local hotfixes for these countries as individual hotfixes.

For these countries, you can find the released platform hotfixes and the application hotfixes that apply to all countries (W1) on the following pages:

CustomerSource

PartnerSource

Local application hotfixes for these countries can be found on the following pages:

CustomerSource

Overview of Local Application Hotfixes not Included in Update Rollups for Microsoft Dynamics NAV 2013

PartnerSource

Overview of Local Application Hotfixes not Included in Update Rollups for Microsoft Dynamics NAV 2013

Weekly platform rollups

To ensure early access to platform hotfixes, weekly platform rollups will be released between monthly update rollups.

Access to update rollups

Please note that a CustomerSource or PartnerSource login is required to access the update rollups and all links in this blog post.

Microsoft Dynamics NAV 2009 SP1, Microsoft Dynamics NAV 2009 R2, and Microsoft Dynamics NAV 2013 are compatible with Microsoft Office 2013

navteam — Tue, 23 Apr 2013 08:36:00 GMT

We are happy to announce compatibility between Microsoft Office 2013 and the following versions of Microsoft Dynamics NAV:

Microsoft Dynamics NAV 2009 R2
Microsoft Dynamics NAV 2009 SP1
Microsoft Dynamics NAV 2013

Microsoft Office 2013 is available in a 32-bit version and a 64-bit version. The recommended version of Microsoft Office 2013 in combination with Microsoft Dynamics NAV is 32-bit, since some of the Office Integration areas in Microsoft Dynamics NAV is not supported in the 64-bit version.

For more information about the difference between the 32-bit version and the 64-bit version of Microsoft Office 2013, see 64-bit versions of Office 2013.

Please note the following:

Sending data from Microsoft Dynamics NAV to both Microsoft Office Word and Microsoft Office Excel using basic export is fully compatible with Microsoft Office Word 2013 and Microsoft Office Excel 2013. The same applies to exporting to Excel from reports and for export of Budgets, Account Schedules, Analysis by Dimensions, and so on.
Interactions such as letters initiated from Microsoft Dynamics NAV are compatible with Microsoft Office Word 2013.

Remark:
You must apply a hotfix to enable the scenario in Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2. Refer to KB article: 2836732 (This has not been published yet. We will provide a link when it is generally available. Until then, contact your Microsoft Support contact.)

Sending emails from Microsoft Dynamics NAV is only compatible with Microsoft Office Outlook 2013 32-bit version.
Outlook Synchronization is only compatible with Microsoft Office Outlook 2013 32-bit version.
Email Logging was rebuilt in Microsoft Dynamics NAV 2013, due to Office removed the support for CDO. For more information, see Collaboration Data Objects (CDO) 1.2.1 is not supported with Outlook 2010.

Email logging in Microsoft Dynamics NAV 2013 are supported for Microsoft Office 2013 and for Office 2010 SP1.
Email logging in Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2 is supported for Office 2010 SP1. It is not supported for Microsoft Office 2013.

OneNote integration available with Microsoft Dynamics NAV 2013 is fully compatible with Microsoft Office 2013.

Best regards,

Rikke Lassen and the Microsoft Dynamics NAV team.

Working with SQL Server through .NET Interop

navteam — Thu, 18 Apr 2013 08:00:00 GMT

The Upgrade Toolkit objects that shipped with Microsoft Dynamics NAV 2013 have a good example of code that works directly with SQL Server through the .NET Framework library. On the product media, navigate to this location:

..\UpgradeToolKit\Data Conversion Tools\601\

Import the Upgrade 601700.2.fob file. This contains codeunit 104050 Upgrade - SQL Mgt.:

and codeunit 104049 Upgrade Dimension entry - SQL:

The same code structure should be applicable to Microsoft Dynamics NAV 2009 R2, though only for the RoleTailored client.

I hope this helps you create codeunits that connect to SQL Server through .NET Interop.

Best regards,

Alexey Finogenov

How to get English text for a system error based on a foreign language screenshot in Microsoft Dynamics NAV

navteam — Tue, 16 Apr 2013 08:30:00 GMT

Working in support services, we are often presented with screenshots of system errors (the error that based on 'core' issue. The text for this error not related to text constants from codeunits, reports and etc.) that are in a language we don't understand. For example, I might see a screenshot that is in German, or Russian, or...

Something like as on these pictures:

Microsoft Dynamics NAV 2009 R2 Russia (Classic client):

Microsoft Dynamics NAV 2013 Germany (Windows client):

How do I get an error on the system is not clear and I want immediately to look for something similar on the Internet or any other sources, documents?

Local text for Microsoft Dynamics NAV isn't enough. You need to have the English text of the error. And how to get the English text, when all you have is a picture?

Do the following:

In the folder where you installed Microsoft Dynamics NAV, find the local subfolder (RUS or DEU or ..), and then locate the fin.etx file.

This subfolder is the equivalent of, for example, C:\Program Files (x 86) \Microsoft Dynamics NAV\60\Classic\RUS\ or C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\DEU\.

Open the fin.etx file in Word

You may have to go through a file conversion of the file, depending on the codepages. For example, if you want to open the fin.etx for the Russian product, make sure that the encoding is set to Cyrillic (DOS). And if you want to open the fin.etx for the German product, make sure that the encoding is set to Western European (DOS).

Look for the Russian/German/.. text. When you recognize the right error text, remember the specific number.

In the Russian example above, the entry in the fin.etx file looks like this:
@2@1281@0@
Первичный ключ таблицы должен включать следующее поле.
The German example has the following entry in the fin.etx file:
@2@55@0@
Die Anzahl der Datensätze in der Tabelle überschreitet die maximale
Anzahl von %1.

Next, in the folder where you installed Microsoft Dynamics NAV, find the ENU subfolder with the fin.etx, such as C:\Program Files (x 86) \Microsoft Dynamics NAV\60\Classic\ENU or C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\ENU.
In the ENU file find the English version of the text error based on the specific number.

In the Russian example above, the entry in the fin.etx file looks like this:
@2@1281@0@
The following field must be included in the table's primary key.
The German example has the following entry in the fin.etx file:
@2@55@0@
The number of records in the table exceeds the maximum number of %1.

This should help you solve the problem. If you need more help, you can search online for the error text.

For example, enter the following error message in the search box on Bing.com:
The number of records in the table exceeds the maximum number of %1.
This returns various fixes for the same problem by other people working with Microsoft Dynamics NAV.

I hope this trick helps you the way it has helped me.

Best regards,

Alexey Finogenov

Delivering customer value sooner with RapidStart compatible ISV solutions

navteam — Fri, 12 Apr 2013 11:55:46 GMT

RapidStart helps to reduce the time to implement Microsoft Dynamics NAV, but what about ISV add-ons?

Once your customer has agreed to a Microsoft Dynamics NAV implementation, they immediately start to look for a return on their investment. RapidStart is designed to help meet customer expectations for a faster time to value by simplifying the configuration of Microsoft Dynamics NAV – but, ISV add-ons can add complexity to the project – especially if the setup process is not managed in the same way as the rest of the Microsoft Dynamics NAV product.

Selecting software solutions compatible with RapidStart Services for Microsoft Dynamics NAV allows you to deliver more within the initial implementation further reducing your customers’ time to value.

Equisys, the Microsoft Dynamics ISV behind Zetadocs Express, is an example of a company that has embraced RapidStart to make life easier for partners. Equisys provides
RapidStart files for Zetadocs that can be used on any Microsoft Dynamics NAV 2013 system to create security roles and permissions. Partners that have created Configuration Packages in RapidStart Services can now extend those packages to include the Zetadocs objects and standard configuration data.

Simpler deployments

“Zetadocs Express provides an easy way to link documents, such as supplier invoices, to Microsoft Dynamics NAV records,” says Greg Cole, Zetadocs Product Manager. "By shipping RapidStart files and configuration data that can get a standard Microsoft Dynamics NAV system running in hours, we’ve made the implementation of Zetadocs super simple. All you need to add is your Microsoft Office SharePoint URL and you’re ready to start dragging and dropping documents onto any page in Microsoft Dynamics NAV. We’ve also gone a step further and created a tool that adds the Document FactBox to your pages without the need to write a line of code.”

Simple to add real value

Greg continues, “Partners are looking for repeatability and inexpensive ways to add value to their Microsoft Dynamics NAV offering. RapidStart is a great tool to help deliver both Microsoft Dynamics NAV and document management in the same timeframe as the Microsoft Dynamics NAV project – without affecting implementation times.

By coupling RapidStart with Zetadocs Express, partners have a great way to differentiate their Microsoft Dynamics NAV offering and deliver real value for customers at no additional cost.”

Simple for you, too

Learn more about how to extend the standardized Configuration Package that comes out of the box with RapidStart Services tips and tricks. Zetadocs Express for Microsoft Dynamics NAV is our downloadable document management module for Microsoft Dynamics NAV, available at no additional cost to users of the Microsoft Dynamics NAV Windows client who are on a Business Ready Enhancement Plan

Best regards,

The Microsoft Dynamics NAV Product Management team

Sending E-mails via Dynamics NAV and the Outlook Security dialog box requesting permissions to send on behalf

mmels — Fri, 12 Apr 2013 09:51:59 GMT

It has been a while ago since I last talked about the Outlook Security dialog box in combination with E-mail logging. Now it is time to summarize all what we have up to now since we are a couple of releases later and the classic application server is no longer needed within Dynamics NAV 2013 release.

When sending E-mails via customization in combination with an attachment or when sending E-mails via a segment, a Outlook Security message dialog box could pop up.

After pressing Log, the following appears to happen. A dialog box pops up.

After allowing access for a specific number of minutes, another dialog box pops up:

After pressing Allow button, the segment continues to be logged successfully.

The reason why this happens is because of the design of Outlook starting with Outlook 2000 in combination with a service release. All relevant information can be read below. If a program tries to access the Outlook Address Book automatically, this message box is presented to the user.

More information can be found here:
OL2000: Information About the Outlook E-mail Security Update

New Programmability Behavior
When you install the update, programmatic access to Outlook is restricted. If other applications try to use Outlook on your behalf, you receive a warning message and you are prompted to confirm what the other application is doing. You receive warning messages when another application tries to do anything in the following list:

·         Send mail on your behalf
·         Access your address book
·         Access E-mail names from your messages
·         Access E-mail information from your contacts or other types of items
·         Save your messages to the file system
·         Search your messages for content
·         Use Simple Messaging Application Programming Interface, Simple MAPI, to send messages without your consent

The update may affect how other applications interact with Outlook by changing the default security zone settings from "Internet" to "restricted," and by automatically disabling script in Hypertext Markup Language (HTML) E-mail messages and unpublished custom Outlook forms. For additional information about developer-related updates and how they may impact third-party products and custom Outlook solutions, click the article number below to view the article in the Microsoft Knowledge Base:
262701 OL2000: Developer Information About the E-mail Security Update

For Exchange Administrators, there is the following KB article:
263297 Administrator information about the Outlook E-mail Security update: June 7, 2000

When using Exchange 2003, you can use the 2003 Office Resource Kit that has the Outlook Security Settings template.

For Exchange 2007 and Exchange 2010 in combination with either Office 2007 or Office 2010, there are administrative templates that can be downloaded (see links at the end of this posting below).

For IT Admins:
http://technet.microsoft.com/en-us/library/ff657852.aspx

For non IT Admins:
http://office.microsoft.com/en-us/outlook-help/how-outlook-helps-protect-you-from-viruses-spam-and-phishing-HA010355583.aspx

So, that said, you need the Exchange Administrator or IT Admin to be involved helping you to configure all this.

That used to be enough when utilizing E-mail logging in Dynamics NAV 2009 R2. This however is not enough when utilizing sending of E-mails via either customization in combination with attachments or sending segment mailing where the checkbox “Send Word Docs. as Attmt.:” is selected within the new or follow up segment. There are a couple of things that are important. Starting with Outlook 2007, Outlook 2007 and later release will validates whether there is an up to date antivirus solution installed. If the signatures are outdates, the Outlook Security Settings dialog box will pop up again. You can find the validation information within the Trust Center Security settings:

If you are on a test system with no internet access, etc., you may want to bypass this security limitation via a registry key:

Outlook 2010
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook\SecurityDWORD: ObjectModelGuardValue: 2

You can also set the keys below. As always, if the keys don't exist in the registry, you'll need to create them.
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\outlook\securityDWORD: PromptOOMSendValue: 2DWORD: AdminSecurityModeValue: 3

Outlook 2007
If you are using Outlook 2007, the keys are as follows.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Outlook\SecurityDWORD: ObjectModelGuardValue: 2

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\outlook\securityDWORD: PromptOOMSendValue: 2DWORD: AdminSecurityModeValue: 3

NOTE: the above registry keys should only be set on test systems and not on production systems.

Now we have received a new support request where the message box was still popping up. After doing some analysis, it appeared that either the GPO or the Outlook Security Settings template was not complete since for sending E-mails directly out of Dynamics NAV, another set of registry key or GPO settings were required. You can find more about this below.

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Security

DWORD: PromptSimpleMAPISend
Value: 2
DWORD: PromptSimpleMAPINameResolve
Value: 2
DWORD: PromptSimpleMAPIOpenMessage
VALUE: 2

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\Security

DWORD: PromptSimpleMAPISend
Value: 2
DWORD: PromptSimpleMAPINameResolve
Value: 2
DWORD: PromptSimpleMAPIOpenMessage
Value: 2

All the mentioned registry keys needs to be applied on a users workstation. The script with all required registry settings are listed below. Save the file as a REG file and add it to a logon script so that the workstations will get it automatically.

///

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook]

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\Security]

"PromptOOMSend"=dword:00000001

"PromptOOMAddressBookAccess"=dword:00000002

"PromptOOMAddressInformationAccess"=dword:00000002

"PromptOOMMeetingTaskRequestResponse"=dword:00000001

"PromptOOMSaveAs"=dword:00000001

"PromptOOMFormulaAccess"=dword:00000001

"PromptSimpleMAPISend"=dword:00000002

"PromptSimpleMAPINameResolve"=dword:00000002

"PromptSimpleMAPIOpenMessage"=dword:00000002

///

However, there is a better way to add the registry keys to every single workstation. This is where the GPO comes into action. Download links for the administrative templates can be found are here.

- Administrative Template for Office 2007
- Administrative Template for Office 2010
- Administrative Template for Office 2013

Updated administrative templates:

- Updated Administrative Template for Office 2007
- Updated Administrative Template for Office 2010

NOTE: the main administrative templates for Office 2013 do already contain the additional required settings. How to configure the GPO can be found in the relevant KB’s below:

http://support.microsoft.com/kb/953806/en-us
http://support.microsoft.com/kb/2723336/en-us

To summarize of the required setting that needs to be configured for utilizing E-mail logging in releases prior to Dynamics NAV 2013 and the required settings that needs to be configured for utilizing segment mailing with attachment and / or sending E-mails with attachments via code, the following applies.

- Configure Simple MAPI sending prompt
- Configure Simple MAPI name resolution prompt
- Configure Simple MAPI message opening prompt
- Configure Outlook object model prompt when accessing an address book
- Configure Outlook object model prompt when reading address information

Hope this does help you further whenever you do come across the additional security features built in within Outlook.

Regards,

Marco Mels
CSS EMEA

This posting is provided "AS IS" with no warranties, and confers no rights

NEW Jet Reports Player for Microsoft Dynamics NAV

navteam — Thu, 04 Apr 2013 09:00:00 GMT

We are excited to announce that the new Jet Reports Player for Microsoft Dynamics NAV is available from the Windows 8 app store.

This app enables business users to easily download, find, organize and share Microsoft Excel reports and dashboards for Microsoft Dynamics® NAV


View organized report libraries to find the right report for the task at hand. You can also upload new report library	Select individual reports to see the details. The interface is touchscreen enabled for easy navigation.	Share reports via email or upload to Microsoft SkyDrive using the Windows 8 Share Charm function.

Other Features

Launch reports in Excel with one click
See report details at a glance
Upload the latest report libraries

You can download the player from the Microsoft Win 8 App store.

Best regards

- The Microsoft Dynamics NAV Product Management team

Coming Soon: Enabling Commerce Gateway for Microsoft Dynamics NAV 2013

navteam — Fri, 22 Mar 2013 06:00:00 GMT

With Commerce Gateway for Microsoft Dynamics NAV, companies can use Microsoft Dynamics NAV to electronically exchange trading documents with business partners regardless of conversion requirements and data formats. This helps streamline business processes and reduce transaction costs. Commerce Gateway also makes it easier for companies to meet the changing demands of their trading partners, regardless of the industry they are in, the system that they use, or the standards that their partners require.

As some of you may have noticed, Microsoft Dynamics NAV 2013 shipped without Commerce Gateway. We have explored a number of different options for enabling Commerce Gateway. This blog post describes the recommended upgrade path for users of Commerce Gateway to make their solution compatible with Microsoft Dynamics NAV 2013.

We are currently working on a sample application that will demonstrate how to upgrade the Commerce Gateway solution. The sample will show how you should set up the connection between Microsoft BizTalk and Microsoft Dynamics NAV using a web service. The sample will be shipped through the hotfix process, after it has been through testing. For now, we expect to release the sample at the end of March.

New customers that need Commerce Gateway will have to upgrade their solutions from Microsoft Dynamics NAV 2009 to Microsoft Dynamics NAV 2013. For more information, see Upgrading to Microsoft Dynamics NAV 2013.

Commerce Gateway is still included in the license as part of the product and can be purchased as normal.

Architectural changes

In architectural terms, the Commerce Gateway solution consists of an application part, a communication part, and a BizTalk part. The communication part is the part that requires the most changes to be able to run with Microsoft Dynamics NAV 2013. We recommend that you change the communication part to use a web service connection instead of using the Request Client and the Request Server. For this to work, it is also required that you make a few changes to the Microsoft BizTalk configuration. There are minor changes to the application part.

The main reason changes to Commerce Gateway were required for it to work on Microsoft Dynamics NAV 2013 are the architectural changes that were introduced with this version, such as the 64-bit Microsoft Dynamics NAV Server, as well as the removal of COM support on the server. Both changes require a change in the Commerce Gateway implementation, since it relies on a 32-bit COM implementation for the Request Server and the Request Client.

Summary of recommended changes

Upgrade application code to Microsoft Dynamics NAV 2013. The application code is impacted by the removal of support for forms.
Change the connection between the Microsoft BizTalk server and Microsoft Dynamics NAV 2013 to use a new web service, which will be defined in the sample. Changing your solution to use web services will simplify the Microsoft Dynamics NAV 2013 installation, as you will no longer be required to use the Commerce Gateway Request server and the Commerce Gateway Request Client.
The Microsoft Dynamics NAV 2013 architecture does not allow the use of automation on the server. Consequently, we have changed five objects to use the .NET Framework XML Document Object Model (DOM). You will have to upgrade your solution to merge in these changes.
Change the connection setup on the Microsoft BizTalk Server to use the web service. You will need to create a new Send port and to reconfigure the orchestrations.

All of the above changes will be described and implemented in the code sample that will ship at the end of March.

Rikke Lassen

Senior Program Manager