New PIN timeline and discontinued support for PKI

In March, we wrote about the support for BAPI in this blog post: Dutch Tax BAPI Support Changing to KPN Certificates (2012).

From that time on there have been some changes from several directions. We like to update you with the latest status, which should be a stable one.

1. Only KPN certificates. The tax authorities, since 1st of July, definitely support only the certificates, issued by KPN. This also means that the return messages that where mentioned in the comments of the first blog can be processed again. The reason at that time for not being able to process them was the fact that we had to deal with two certificates, while Microsoft Dynamics NAV only supports one.
2. PIN support extended. The tax authorities changed the timeline for the support of PIN, the public key method. The deadline was previously set to 1-1-2013 for support of VAT and ICP. Now the support for VAT and ICP submission through PIN is extended to 1-1-2014.
3. PKI functionality discontinued. Recent research, due to changes in certificate supplier, showed that the number of Microsoft Dynamics NAV customers using the PKI method is minimal. Given the fact that coding, hence a new release, was needed to support the PKI method with KPN certificates, we decided to unplug support for PKI. This private key method will also be discontinued by the tax authorities per 1-1-2014. We have informed and advised all concerned partners to move to PIN. We are looking to support Digipoort / XBRL for the near future.

We want to repeat the comment that Jacco Stolk (thx Jacco!) made regarding getting the BAPI software. Microsoft Dynamics NAV does not deliver the required BAPI.dll and CL32.dll, since it is owned by the tax authorities’ organizations. In this case you can subscribe to the OSWO site (https://www.oswo.nl) to obtain the latest version of the BAPI software and find answers to technical problems that might occur.

Best regards,

Coen Overgaag

Microsoft SQL Server 2012 was released in March with many new and interesting capabilities. For further information, please take a look at the product information at Microsoft SQL Server.  

Over the last few months the Microsoft Dynamics NAV product team has been testing the compatibility and we are now proud to announce that Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2 are compatible with Microsoft SQL Server 2012!

Please note that this applies to the following editions of Microsoft SQL Server:

• Express Edition
• Standard Edition
• Enterprise Edition
• Business Intelligence Edition

There are a couple of special cases, where the support will stay on SQL Server 2008. These areas are Business Notification, Business Analytics, and Commerce Gateway.

For further information please look at the System Requirements – Available on PartnerSource.

Connector for Microsoft Dynamics V2 Rollup 1 was released on Friday! This release includes enhanced integration options and maps, and also resolves some of the key issues that you might be facing with your V2 deployments. Additional features and updates are listed later in this post.

Stay tuned to the Connector blog for upcoming videos that detail the new features and functionality.

To download this release for Microsoft Dynamics NAV, go to PartnerSource:

• Connector for Microsoft Dynamics NAV
• This version requires Microsoft Dynamics NAV hotfix 2597312 and hotfix 2721512 when integrating Microsoft Dynamics CRM with Microsoft Dynamics NAV 2009 R2.

Don’t have access to PartnerSource but would like to know more? Check out the User Guide for NAV and begin your installation preparation.

• Connector for Microsoft Dynamics User Guides

Here is an overview of the feature list:

• Features across ERP products:
• Microsoft Dynamics CRM Duplicate detection rules are now supported on child entities as well as on parent entities, reducing the likelihood of duplicate records getting into your system.
• On-demand workflows for account and contact are now installed in Microsoft Dynamics CRM 2011 that allow you to “Bulk submit” these entities and streamline the process for creating new accounts and contacts.
• The Microsoft Dynamics CRM 2011 Configuration utility no longer overwrites your custom changes to object provider configuration files, so you don’t have preserve a separate copy when re-running the Configuration utility.
• If attributes are deleted in Microsoft Dynamics CRM 2011, then re-running the Microsoft Dynamics CRM 2011 Configuration utility removes them from the object provider configuration file for that entity. You no longer have to do this manually.
• Microsoft Dynamics CRM 2011 entities that appear in the log not only have their unique key listed in the “Key” column but also have the value of their primary attribute listed. This allows for easier troubleshooting of integration errors within Microsoft Dynamics CRM 2011.
• A help file has been added to the function selection page that explains all of the functions in our default library, so you can easily search for the function that you may need for customization.
• Documentation has been updated to include more detail on how each map functions and the assumptions that they make about your data, which improves your upfront costing when evaluating Connector for Microsoft Dynamics.
• Primary contacts that are associated to accounts in Microsoft Dynamics CRM 2011 are now checked to see if they have been previously submitted when the account is submitted, so you will no longer receive an error in Connector for Microsoft Dynamics when this situation occurs.
• Parent accounts that are associated to contacts in Microsoft Dynamics CRM 2011 are now checked to see if they have been previously submitted when the contact is submitted, so you will no longer receive an error in Connector for Microsoft Dynamics when this situation occurs.
• Custom entity references have their “Integration Key” attribute set up when they are retrieved from Microsoft Dynamics CRM 2011, so if your customization needs to get data in or out of this field they can do so.
• GetCurrencyName() and GetCurrencySymbol() functions are updated to not return blank if the ISO code that is supplied is invalid or out of date. This reduces errors during the integration of currencies.
• Local machine accounts are now supported for running the Connector for Microsoft Dynamics service, thus removing the dependency on Active Directory for the service account.
• Connector for Microsoft Dynamics client start time has been improved so the log no longer needs to be cleaned up manually in order to speed up client load time.
• The Microsoft Dynamics CRM 2011 Configuration utility now uses the integration specific settings for the Microsoft Dynamics CRM 2011 adapter. This allows you to launch the Microsoft Dynamics CRM 2011 Configuration utility directly from the integration settings and not have to re-enter the settings for your integration.
• Features for Microsoft Dynamics NAV:
• Mapped fields in Microsoft Dynamics CRM 2011 have the same length as they do in Microsoft Dynamics NAV, preventing data input errors that cause integration failures.
• After applying the Microsoft Dynamics NAV hotfix found in this KB 2721512 (http://support.microsoft.com/kb/2721512), country/region codes from Microsoft Dynamics NAV are integrated into a global option set in Microsoft Dynamics CRM 2011. Country/region codes that are supplied by users are validated against this list, preventing invalid data from being entered in Microsoft Dynamics CRM 2011.
• Microsoft Dynamics CRM 2011 account numbers can no longer be updated after the account has been submitted, eliminating potential integration errors when users inadvertently change an account number in Microsoft Dynamics CRM 2011.
• “Blocked” customers and items in Microsoft Dynamics NAV are set to an inactive state and status in Microsoft Dynamics CRM 2011, which helps to prevent them from being added to a sales order.
• Address types are defaulted and not editable in Microsoft Dynamics CRM 2011, which prevents data input errors.
• Fields in Microsoft Dynamics CRM 2011 that have no corresponding field in Microsoft Dynamics NAV are set to be read-only in Microsoft Dynamics CRM 2011, which helps to  prevent data input errors
• Posted Sales orders that are integrated from Microsoft Dynamics NAV into Microsoft Dynamics CRM 2011 have their status set to “Billed” to allow you to more easily distinguish open invoices from posted ones in Microsoft Dynamics CRM.