With the release of Office 2010 and SharePoint 2010 the relationship between internal line of business applications and business productivity software is stronger than ever. There have been added many exciting new features, which will bring value to many customers, including those customers that are using Microsoft Dynamics NAV today.
The user interface (UI) is the "face" of a software application - A good user interface is intuitive, familiar, and easy to use. It improves productivity by minimizing the number of clicks required to get a task done. This is what we accomplished with the release of the RoleTailored client in Microsoft Dynamics NAV 2009. The Fluent UI is now used by all Microsoft Office programs as well as SharePoint Server 2010, and does away with menus, which were growing increasingly complex, replacing them with a clear set of icons that are relevant to the task being performed.
With the 2010 release, Microsoft Office, Microsoft SharePoint Server, and Microsoft Dynamics now share this strong "facial" resemblance, making them more consistent to use and easier to adopt.
Just as beauty is more than skin deep, so the ties between Microsoft Dynamics and Microsoft's business productivity infrastructure run deeper than just the UI. Business Connectivity Services (BCS) is a new technology that crosses Microsoft Office 2010 and Microsoft SharePoint Server 2010, and can be thought of as "plumbing" for connecting business applications through Web Services in Microsoft Dynamics NAV 2009 with SharePoint and Office. This is no ordinary plumbing, though, as it enables some powerful new scenarios for Microsoft Dynamics NAV customers, including the ability to update information stored in a Microsoft Dynamics NAV database directly from a SharePoint site, and making it easier to take Microsoft Dynamics NAV information offline through either Outlook 2010 or SharePoint Workspace 2010.
The majority of Microsoft Dynamics customers use Microsoft Excel to analyze their business information. PowerPivot for Microsoft Excel 2010 offers the ability to quickly create PivotTables or PivotCharts that are pulling in data from Microsoft Dynamics ERP or CRM in real time. New Excel 2010 features such as Slicers and Sparklines can then be added to bring the numbers to life and gain deeper insights into what's happening in the business.
Since Microsoft Dynamics NAV always has had a strong integration to the Office and SharePoint products, we are proud to announce that Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 5.0 SP1 Update 2 are compatible with Microsoft Office 2010 and Microsoft SharePoint 2010!
The details in the support for the different Office and SharePoint integrations are listed below. Please note that Office 2010 is available in both a 32-bit version and a 64-bit version, but some NAV areas are currently not supported in the 64-bit version. The recommended version of Office 2010 in combination with NAV is the 32-bit version. Further reading on the difference between the two versions can be found here: http://blogs.technet.com/b/office2010/archive/2010/02/23/understanding-64-bit-office.aspx.
With Microsoft Dynamics NAV 2009 R2 it is time to drill into the new features we have for you in the reporting area.
Enhanced connection with Visual Studio when editing layout (RDLC)
a. Easy refresh of dataset in Visual Studio
In NAV 2009 SP1 you had to close down Visual Studio when you made any modifications to the dataset (Section designer). With NAV 2009 R2 you can keep both the NAV Report designer and Visual Studio Layout designer open.
To see this feature in action
1. Open a report in design mode and select “View/Layout”
2. With both Report Designer and Visual Studio window, open add new field to the dataset (Section Designer)
3. Now, to activate the refresh action you need to both save and compile. Only saving, or only compiling the report, will not activate the dataset refresh action in Visual Studio.
4. Navigate back to Visual Studio and you will see this message:
5. Select “Yes” to accept the Refresh
6. Lastly, right click ”Result” under ”DataSet”, and select Refresh
Select the Refresh Button
7. You will now see your new added item to the dataset, and you can now add this to your layout.
b. Better protection when closing Report Layout in Visual Studio
In NAV 2009 SP1, it was possible to accidentally close down the Report Designer in NAV and thereby leaving Visual Studio with the Layout open in an unsaved state. With NAV 2009 R2 it is no longer possible to close down the Report Designer in NAV without closing Visual Studio first.
To see this feature in action:
2. With both Report Designer and Visual Studio window open, try closing the NAV Report Designer window. You will see this message:
c. Better protection when opening report layout for design in Visual Studio
In NAV 2009 SP1 it was possible to accidentally open several version of the same report layout in Visual Studio. This can easily cause confusion, so with NAV 2009 R2 it is no longer possible to open several versions of the layout in a report.
2. With both Report Designer and Visual Studio window open select “View/Layout” again and you will see this message:
Printer Selections now available in Role Tailored client
In NAV 2009 SP1 the only way to define which reports should be printed to which printers was in the Printer Selections form as Printer Selections did not work from Role Tailored client. So you had to have the Classic client installed to configure the Printer Selections in NAV 2009 SP1. You could of also have use the workaround described here: http://blogs.msdn.com/b/nav-reporting/archive/2009/10/19/printer-selections-in-role-tailored-client.aspx
With NAV 2009 R2 we now have Printer Selections working from Role Tailored client.
1. Open Role Tailored client and type “Printer” in the search box
2. Select Printer Selections and you get this page:
3. To edit the list or create a new select “New” and you will be able create a new or edit what you already have defined:
New action images for PDF
You might have seen my blog post on how to send an e-mail with a report attached as a PDF file. If you have not seen this here is the link: http://blogs.msdn.com/b/nav/archive/2009/10/08/send-email-with-pdf-attachment-in-nav-2009.aspx
In NAV 2009 R2 we have some new icons which we can use.
So if you want to send an e-mail with a report attached as a PDF file in NAV 2009 R2, you might want to consider using the image called: “SendEmailPDF”
And if you want to save a report as a PDF file from RoleTailored client, you might want to use the image called:” SendAsPDF”
And yes it would be great if guys one day could add your own icons to the RoleTailored client. Hopefully we will have this feature in a future version of NAV.
Recently Microsoft hosted a Hot Topic session that included the reporting features discussed in this post. It is called "Microsoft Dynamics NAV 2009 R2 Hot Topic: What's New for Developers." A recorded version of the session can be seen at the Partner Learning Center.
This is what I had to share today; I hope you appreciate the new reporting features which will be available in NAV 2009 R2. And as always I’m happy to get feedback about reporting features you would like for us to implement in future releases. So use the Contact Form to write directly to the core reporting team or use MS Connect to give suggestions:https://connect.microsoft.com/dynamicssuggestions
Thanks, Claus Lundstrøm, Program Manager, Microsoft Dynamics NAV
As most of you have already found out, we, the NAV R&D team, have developed a new Help Server that shows Help on a website. Help is available for the Windows client as in earlier versions. With the Help Server, the same Help is available from the Web client. Choose a field, and context-sensitive Help opens.
The Help Server is a website that displays HTML files. Yes, you read correctly: HTML files. So you don’t have to decompile the Microsoft CHM files anymore. But the really good news is that the Help that you created for your current NAV solution will still work with the new Help Server. You just need to build it again with the new Help Toolkit, and then copy the resulting HTML files to the relevant folder on the Help Server website. Then, you can start connecting your users to the Help Server.
Here are the main steps for deploying your Help to your customers.
Rebuild your existing Help files with the NAV 203 version of HelpBuilder, but change some of the configuration settings. For more information, see Upgrading Your Existing Help Content in the MSDN Library.
Add the HTML files that HelpBuilder creates to the relevant language-specific folders on your Help Server website.
Grant your users access to the website.
This is different depending on your deployment scenario. For more information, see Microsoft Dynamics NAV Help Server in the MSDN Library.
Configure the Microsoft Dynamics NAV 2013 R2 clients to look up Help on your Help Server.
This configuration is part of Microsoft Dynamics NAV 2013 R2 Setup. Alternatively, you can configure the Web client server components and the Windows clients manually.
Start a Microsoft Dynamics NAV 2013 R2 client and access Help.
You can set up a Help Server that all your users can access, or you can set up multiple Help Servers. You can modify the Microsoft-provided Help content without decompiling anything, and you can add and remove Help content whenever you want to. You can add links to existing Word documents or PDF documents to the navigation pane of the Help Server website, so that you users have a single point of entry for Help.
With the Microsoft Dynamics NAV 2013 R2 Help Server, you can provide the Help content that is relevant for your users, and you can update Help without modifying each client computer.
We will improve the Help Server in future releases of Microsoft Dynamics NAV, so we hope you will like it as much as we do.
The Dynamics NAV team
Update rollup 6 for Microsoft Dynamics NAV 2013 (Build 35345) has been released.
Update rollup 6 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:
Where to find update rollup 6
You can download update rollup 6 from KB 2881294 - Update Rollup 6 for Microsoft Dynamics NAV 2013 (Build 35345).
The hotfixes that have been released since update rollup 5 are listed in KB 2881294. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:
For more information about update rollups for Microsoft Dynamics NAV 2013, see Announcement of new hotfix process for Microsoft Dynamics NAV 2013.
Update rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076) has been released.
Update rollup 11 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 and includes hotfixes that apply to all countries and hotfixes specific to the following local versions:
Where to find update rollup 11
You can download update rollup 11 from KB 2930616 - Update Rollup 11 for Microsoft Dynamics NAV 2013 (Build 36076).
The hotfixes that have been released since update rollup 10 are listed in KB 2930616. For a full list of all hotfixes included in the update rollup, see the following CustomerSource and PartnerSource pages:
We recently shipped the Application Test Toolset for Microsoft Dynamics NAV 2013.
The supplement is applicable to the following country releases of Microsoft Dynamics NAV 2013:
W1, AU, CA, DE, DK, ES, FR, GB, IN, IT, MX, NL, NZ, SE and US
The supplement contains the following per country:
You may attempt to apply the W1 version to other country versions, but you should expect parts of the toolset to not work.
To install the supplement, do the following:
How Do I Use This?
The simplest way to make use of this supplement is to run the Test Tool page (130021) directly from the development environment. This launches the following page:
Click Get Test Codeunits and then select All Test Codeunits.
After Microsoft Dynamics NAV finishes loading all test codeunits, they are displayed on the Test Tool page. To run them, click the Run action and then select All.
It will take about 1 – 2 hours depending on your machine and the setup to run all tests. When the run is completed it will show the results in the Test Tool page:
Any changes done to the database through running of tests from the Test Tool are automatically rolled back using the Test Isolation testability feature of Microsoft Dynamics NAV 2013. (See the Additional Resources section in this post.)
During typical development, it is unacceptable to have to wait hours to get results from tests, which is why we have built an advanced test selection feature to help identify the relevant tests. (See the Test Selection section in this post.)
Alternatively, you can run individual tests or codeunits by selecting them and choosing either Active Line or Active Codeunit after you click the Run action.
If any test fails, you can attach a debugger session and re-run the failing test. The debugger will then break at the line where the test failed and you will be able to inspect the call stack and examine variables to determine the underlying cause of the failure.
Extending the Toolset With Your Own Tests
After you have written your first test codeunit, you can easily integrate it into the tools we provide in this supplement.
To include your own tests, in the Test Tool page, simply run the page from the development environment and click the action Get Test Codeunits and choose Select Test Codeunits. This will display a page listing all available test codeunits, including your own:
Select the codeunits you would like to add to the tool and press OK. The new test codeunits appear at the bottom of the Test Tool list, and you can now select them and run them just like any of the tests we included.
Again, Test Isolation prevents your tests from persisting changes to the database. During development it may be beneficial to actually see the output produced by the tests. It is possible to disable Test Isolation just by running the test codeunit directly from the development environment, however, instead we recommend attaching a debugger session, breaking at the test entry point, then stepping through test execution and inspecting variables to determine if your test is behaving as expected.
Speeding Up Development of Your Own Tests
The tests that we have developed are built on top of a layer of libraries that contain helper functionality to automate many aspects of Microsoft Dynamics NAV. For example, the library named Library – Sales contains functionality related to working with customers and sales documents, including creating new customers, sales headers, sales lines and posting sales documents. The library is extensive and has functionality in many areas of the product, such as finance, service, jobs, warehousing, inventory, etc.
Instead of re-inventing the wheel when developing your own tests, we highly suggest that you look into our existing helper functionality for functions you can leverage.
To help you find your way around the libraries, we have shipped a Microsoft Compiled HTML Help file (*.chm), which is bundled together with the .fob file you installed. When you open the .chm file, you are prompted with the following window:
This lists all our libraries and the functions inside them. However, normally you don’t know which library to look for, You can search it from the Search tab. Try searching for "finance charge memo" and you will have a couple of choices to pick from:
Code Coverage Tools
Code coverage is the means of being able to track which part of the application code has been exercised during some activity. In Microsoft Dynamics NAV, code coverage is recorded by AL code line and in addition to knowing if a code line was exercised it also records the number of times it was recorded.
The code coverage activity that we record can be any interaction with Microsoft Dynamics NAV, be it manual user interaction, automated test execution, NAS, Web services, etc. You can, of course, record code coverage of your own tests exercising your own objects.
The toolset includes a page (130002), Code Coverage List, which you can use to track code coverage. Run the page from the development environment:
From this page you can start/refresh/stop the code coverage recorder. If you click the Start action, the code coverage engine is turned on and code coverage is captured. However, you will not be able to see any updated information before you click either Refresh or Stop, at which time you are presented with the code coverage information:
The information contains coverage of objects, triggers/functions and individual lines (code and empty) as determined by the column Line Type. Only lines of type Code can have coverage. Lines of type Trigger/Function show the average coverage of all code lines in the trigger/function. Lines of type Object show the average coverage of all code lines inside the object.
From the above picture, you can read that the activity exercised 33.93% of the Currency table (4). It covered 100% of the OnModify trigger and that comes from 100% of a single Code line.
It is often desirable to filter on Line Type = Object to first get a high-level overview of the coverage result:
Then from here, you can filter to look at individual objects and expand the Line Type filter to include triggers/functions as well:
This way you can drill-down into the results starting from a high-level view going to a low-level view.
Note #1: Code coverage is recorded globally for all sessions when using this tool, so make sure you are running in a controlled environment so you don’t have any activity from unaccounted sessions.
Note #2: Only objects that are touched by the activity are recorded, meaning the coverage of any object not in the list is implied to be zero. If you would like to force the recorder to include specific objects even if they are not covered, you can usethe Load objects action and select the relevant objects from the subsequent page. This forces the code coverage engine to load these objects and provide information on even when no lines are covered.
Now that we have all the building blocks in place, I’d like to talk about an advanced feature we included with the tooling.
As mentioned previously, having to wait hours to run all tests is not feasible from a development point of view. Therefore we shipped the Test Selection, which helps you narrow the set of tests down to the relevant tests.
The feature works by analyzing the code coverage data from individual test codeunits and comparing it to the set of objects that have the Modified field set to Yes in the database.
To use this feature, you run the Test Tool page and go to the Actions tab and click Import/Export Test Map action. On the request page, make sure the direction is Import and click OK. Browse to the bundled "AppTestToolsetNAV2013-<countrycode>-Map.txt" file and import the file. This will take a couple of seconds. After it is done, click the Get Test Codeunits action. The prompt will now include a third option:
Select this third option and the tool will automatically detect the relevant tests to run and add them to your current suite.
Note #1: In typical circumstances you would want to make sure your suite is empty before using this feature.
Note #2: There is a small risk this feature will not identify all relevant tests in unusual circumstances. Thus we strongly recommend running the full regression suite before shipping anything to the customer.
This feature also integrates with you own tests. Once enabled (by loading the Test Map), the information will auto-update when any test is run – including your own tests. This means that you can load the map, run your tests and now export the map to another text file. You can then load the new map into another database and the test selection feature will now be able to suggest your own tests based on modified objects in this other database. If your test codeunit is not present in the database, you will be prompted with a list of missing test codeunits that could not be added. Import the missing test codeunits into the database and re-run the test selection feature.
In one of our previous blog post we discussed the possibility to do Transfooter and Transheader functionality in RDLC(SSRS) reports and describes a viable solution for this in RDLC.
In this blog post we would like to suggest an alternative, a bit more economical and easier to implement solution for the same problem.
For the demo we use the same table and the same report and will strive to achieve the same results as in the mentioned in our previous blog post.
1. Create new report blank report with table 18
2. Create DataItem ”Customer”
3. Go to Section Designer and add the following fields:
4. Save the report as ID 50000 – Transfooter / Transheader
5. Now go to Visual Studio (View / Layout)
6. Create table and add the fields No, Name and Debit Amount
7. Give this table the name "MainTable"
8. Now we have added the basic for this report. But I would also like to have a Grand total of the Debit Amount so I add this as well. I add this in the Footer of the table
="GrandTotal: " & sum(Fields!Customer__Debit_Amount_.Value)
9. Now if my report is printed I get a list of my all my customer with Debit Amount displayed and with GrandTotal in the end of the report:
10. Now I create a small block of VBS code in order to perform some calculations and store intermediate data
Open “Report->Report Properties” dialog and select “Code” tab, enter the following VBS code:
11. Define a hashtable for storing running accumulated sums for each page of the report
Shared RunningTotals As New System.Collections.Hashtable
12. Define two public functions, which populate and query the hashtable from above
Public Function GetRunningTotal(ByVal CurrentPageNumber)
Return IIF(CurrentPageNumber > 0, RunningTotals(CurrentPageNumber), 0)
Public Function SetRunningTotal(ByVal CurrentPageTotal, ByVal CurrentPageNumber)
RunningTotals(CurrentPageNumber) = CurrentPageTotal + GetRunningTotal(CurrentPageNumber - 1)
13. Ok, it’s now time to add a Transfooter and Transheader.
Enable Page Header and Page Footer in the report (click “Report->Page Header” and “Report->Page Footer”).
14. In the Page Footer I place a text box with the following expression:
="Transfooter subtotal = " & Code.SetRunningTotal( Sum(ReportItems!Customer__Debit_Amount_.Value), Globals!PageNumber)
This code actually performs the following actions:
- calculate the sum of all “Debit Amount” values on the current page (sic)
- adds this value to the running total, which has been already calculated for the previous page
- returns this value as the actual running total for the current page
15. In the Page header I place a text box with the following expression:
="Transheader subtotal = " & Code.GetRunningTotal(Globals!PageNumber-1)
This code fetches the running total, calculated up to the previous page
16. And then I set distinctive BackgroundColor and font Color just so this Transfooter and Transheader stand out in my report
17. Now I’m almost done but I would like to not see the Transheader on the first page and not to see the Transfooter on the last page.
So I set the following expressions for the “Visibilty->Hidden” properties of the page header:
=IIF(Globals!PageNumber > 1, False, True)
And for the page footer:
=IIF(Globals!PageNumber < Globals!TotalPages, False, True)
18. Now I’m done, I save, import into NAV and compile. After some fit and finish on the report it now looks like this when I print
Now I’m done, I save, import into NAV and compile. After some fit and finish on the report it now looks like this when I print:
Question: Would this also work in the example of having a list of sales order lines per sales header and the sales order lines goes to multiple pages?
Answer: The report above is a bit simplified in order to illustrate the point. It can be easily extended to support your scenario. I.e. the key for the hash should include page number AND header no to accomplish this.
You can download the report object here, thanks to Nickolay Belofastow.
It’s no secret that Microsoft Dynamics NAV customers and partners have needed an ad hoc reporting solution that’s easy to use. Well, now we have one!
We’ve been working in cooperation with Jet Reports, Inc. on the development of an Excel-based reporting solution. The result is Jet Reports Express for Microsoft Dynamics NAV – a simple but effective business reporting tool that gives customers an easy and simple way to create high impact reports and helps us to enhance our BI & Reporting value proposition.
Within a familiar Microsoft Excel environment, users will be able to access Microsoft Dynamics NAV data and utilize all of the Excel capabilities, such as Power Pivot, formatting, charting and Pivot Tables, to create powerful, insightful and well-formatted reports. There are multiple report templates available out of the box.
Plus, users will be able to answer and analyze ad hoc business queries with real time data from Microsoft Dynamics NAV. It’s possible to access and combine data from NAV – including tables, fields, flow fields and dimensions, and you can slice and dice data and do consolidation. You can also drill down into any value in a report to see the underlying data with just one click.
Jet Reports Express for Microsoft Dynamics NAV really is simple to work with and very easy to demo. It’s the perfect solution for the majority of the Microsoft Dynamics NAV customers who need a basic ad hoc reporting solution.
Jet Reports Express for Microsoft Dynamics NAV will be available to Microsoft Dynamics NAV customers as new functionality at no additional costs, provided they are on an active Business Ready Enhancement Plan.
The product can be downloaded via a link from PartnerSource and CustomerSource that will be available sometime in Q3 CY2011. Look out for more information on final release date.
Stay tuned for more information about all the cool things customers can do and partners can demo with this smart reporting tool.
In this blog is described a very simple usage of the .NET interoperability feature with Microsoft Dynamics NAV 2009 R2 and can be considered an extension of my previous blog: http://blogs.msdn.com/b/nav/archive/2010/07/09/let-nav-speak-with-a-simple-and-useful-client-add-in.aspx.
It is intended just to familiarize you with this brand new feature proposed with the NAV 2009 R2 release.
If you want to know more about .NET interoperability for NAV 2009 R2, please refer to MSDN link:
Extending Microsoft Dynamics NAV Using Microsoft .NET Framework Interoperability
The .NET interoperability code snippet in this blog is based on the System.Speech namespace.
Create your "Speak it!" action and let NAV speak Customer Names :
1. Open Classic Client
2. Go to the Object Designer
3. Select Page object (alt+g)
4. Select Page 22 "Customer List"
5. Design Page 22 "Customer List" (alt+d)
6. Select View > Page Actions (al+v, o)
7. Create a new Action (F3) in the ActionItems container (see below)
8. Change the properties of the Action as below:
Caption - Speak it !
Image - ViewComments
Promoted - Yes
PromotedCategory - Process
PromotedIsBig - Yes
9. Edit the code in the Speak it! Action (F9)
10. Add those LOCAL variables
Subtype: System.Speech, Version=18.104.22.168, Culture=neutral,PublicKeyToken=31bf3856ad364e35.System.Speech.Synthesis.SpeechSynthesizer
Subtype: System.Speech, Version=22.214.171.124, Culture=neutral,PublicKeyToken=31bf3856ad364e35.System.Speech.Synthesis.SpeechSynthesizer
Subtype: System.Speech, Version=126.96.36.199, Culture=neutral,PublicKeyToken=31bf3856ad364e35.System.Speech.Synthesis.VoiceGender
NOTE: RUNONCLIENT is a property of each DotNet variable (shift+f4)
11. Add this code snippet in the OnAction trigger
// Copyright © Microsoft Corporation. All Rights Reserved.
// This code released under the terms of the
// Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)
// Use the constructor to create a new Synthesizer
Synth := dnSpeech.SpeechSynthesizer();
// This is an enumeration assignment:
dnVoiceGender := 2; //Female
// NOTE: it will take the voice depending on what is
// installed locally (e.g. Windows 7 has Microsoft Anne voice)
// Please, speak slowly (range [-10:10])
Synth.Rate := -3;
// Row below is not needed. Synth is a local variable therefore it will be
// automatically disposed
12. Save and compile (ctrl+s) page 22 "Customer List"
Now... you are ready to let NAV speech the Customer Name from the customer list by simply click on the "Speak it!" action.
These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.
Duilio Tacconi (dtacconi)
Microsoft Dynamics Italy
Microsoft Customer Service and Support (CSS) EMEA
There have been some changes from the tax authorities since this post. For information about the changes, see Changes in Dutch Tax BAPI Support - Part 2.
Electronic communication with the Dutch Tax administration is based on trusted connections using Digital Certificates. In 2011 an incident has occurred with Diginotar, one on the Certificate Authorities (CA), resulting in a situation that an infiltrator was able to create new certificates on his own for every random domain. This made the whole certificate-based environment unsecure and required facilities to make sure that trusted digital communication remains possible in the future.
The Dutch Tax administration evaluated the different existing communication channels and decided to phase out one of these channels: BAPI-PIN. It has also been decided to no longer use Diginotar certificates but to give KPN (Getronics) the role as the Certificate Service Provider (CSP) for the future.
SUBMITTING VAT AND ICP DECLARATIONS USING MICROSOFT DYNAMICS NAV
You can choose to submit VAT and or ICP to the Dutch Tax Authority by manually filling in a web form (www.belastingdienst.nl). There is a limit however for the ICP declaration. The website allows a maximum of 99 lines to be entered manually. An ICP Declaration report can be printed from Microsoft Dynamics NAV to use as a guideline.
Microsoft Dynamics NAV supports the BAPI channel electronic communication. Within the BAPI channel both PIN and PKI method are possible by Microsoft Dynamics NAV.
PIN is the public key method and mostly used within the Microsoft Dynamics NAV community. For this method you only need the certificates from the Tax authorities and CSP. To get these you have to fill in the fields on tab Certificates of the ‘Elec. Tax Declaration Setup’ page and get the certificates by the function ‘Get CA Tax Auth. Certificates’. The certificates for the PIN method can be acquired at no cost.
PKI is the private key method. This method uses user certificates for encrypting the message and providing a digital signature. For PKI 4 different types of certificates are needed:
A company has to buy the user certificates. On the KPN site you will find all this information.
With respect to PIN and PKI the following timeline has been set by the Tax authorities (latest communication in Feb 2012):
MICROSOFT DYNAMICS NAV AND BAPI PIN
In order to continue using PIN until 2013 you will need to change the certificate settings to KPN before June 2012.
To realize this, please change the following settings in the “Electr. Tax Declaration Setup” under the “Certificates” Fast TAB (production environment parameters). Make sure you have no ongoing declarations.
CN=KPN Corporate Market Tax CA G2,O=KPN Corporate Market BV,C=NL
CN=Belastingdienst,OU=Servercertificaat E - zie CPS,L=Apeldoorn Joost van den Vondellaan 14 (0000),O=Belastingdienst (2000000002),C=NL
No need to change other settings. After that you can renew the certificate by using the function “Get CA Tax Auth. Certificates” and do your normal submissions again.
For testing purposes you can use the following test environment parameters (you should have a test account at Tax Authorities):
CN=KPN Corporate Market Tax TEST CA G2,O=KPN Corporate Market BV,C=NL
CN=TEST Belastingdienst,OU=Servercertificaat E - zie CPS,L=Apeldoorn Joost van den Vondellaan 14 (0000),O=Belastingdienst (2000000002),C=NL
MICROSOFT DYNAMICS NAV AND BAPI PKI
If you are using the PKI method to submit the declarations, then you will need to ask for a (re)new(al) certificate at KPN. The Tax Authorities have already informed the users of PKI certificates on this process. Microsoft needs to investigate if Microsoft Dynamics NAV is able to work with KPN certificates under which conditions.
Tests for requesting KPN PKI certificates and submitting declarations are in process at the moment. You will be informed in a timely manner what changes are needed.
As a follow up to my previous post, we are happy to announce that, from build 32942, the hotfix releases will detect if objects need to be recompiled and prompt you to recompile accordingly. This will happen when importing incompatible fobs files or when applying new platform hotfixes.
If you try to import fob files from previous (or possibly also newer versions), or if you export them from newer builds (32942 and newer) and back to NAV 2009 R2 or newer versions (up to build 32942), the system will detect that the metadata is incompatible and force a recompilation when imported. The same detection will happen if you apply a hotfix to your system, and your objects need to be recompiled.
In the future, the metadata version (which is now in the Object Metadata table in field 27) will be updated if a compilation will be needed after applying a hotfix, not making it necessary always to re-compile the objects every time you apply a new hotfix (and preventing the RTC client from losing the connection to the server). The current metadata version is 60300, whereas the R2 runtime metadata version is 60200.
Since we are changing a system table (table 2000000071), we need to do a database conversion. Moreover, since the objects are not recompiled with a database upgrade, you also need to recompile the objects that you need. The nice feature now, is that the RTC will prompt you on demand to recompile the objects that need recompilation (basically, the ones you use).
Update: I stand corrected, embedding fonts into a PDF is not an option with the SAVEASPDF function in NAV 2009.
But now you at least know that this is solved in our next version.
I just want to share a small tip today. If you need to include a custom font into a RDLC report you need to first install the font, of course.
The Font must be a True Type font. If your font is an Open Type font you will need to convert this first for it to visible in Visual Studio.
Then you will need to restart the computer for the font to be embedded into the report when saving as PDF.
The restart issue took me some time to figure out, so with this small tip, you hopefully will not loose as much hair as I did, when you include a custom font into a RDLC report.
I have attached a sample RDLC report with a custom barcode font.
What is silent or unattended installationSimply said silent install is installation without any UI. In this case it’s about how to run “setup.exe” in silent mode. It’s recommended that you only run “setup.exe” when you install a new NAV installation, because the installer have been tested by them using this procedure only. So by that said it’s no longer supported to install from the different msi files directly. This is true for all NAV 2009 releases. The major problem you may run into if you are installing directly from the msi files is that you will not get prerequisites (as .Net, Report Viewer and so on) installed and you will also miss out one some pre installs checks (validating that you have everything needed as outlook).
How to-do it?It’s very simple. “setup.exe” does support some different parameters for this purpose:/quiet <– will turn of the UI/log [filename] <– create a log text file in the specified location/config [filename]<– point to the configuration file to use during the installation/uninstall <– will simple un install the product/repair <– repairs a bad installation
The first thing that needs to be done is to create the configuration file that we will use.
You can create as many configuration files as you want for different purposes. Now, you can run the silent install by simply doing start -> run -> [setupExepath] /quiet /config [configfilepath.xml]. Be sure to take a look to the log file, to ensure everything went OK.
Example D:\setup.exe /quiet /config C:\configfiles\config1.xml /log C:\log.txt
With NAV 2009 R2 it is now possible to set how many XML records to send to RoleTailored Client (RTC), bypassing the previous hardcoded limitation of 5000 records.
This could be done by installing platform hotfix KB 2492490 Build no. 32146 or higher.
I just would like to explain how this Hotfix works in short.
In order to bypass the previous hardcoded limit of 5000 Max no. of xml records to send, after installing the aforementioned platform hotfix or higher, you have to set a key like that on every RTC Client machine in the ClientUsersSettings.config file
<add key="MaxNoOfXMLRecordsToSend" value="integerValue" />
(where integerValue is an integer value that represents the max number of xml records to send when using the Export to Microsoft Office feature)
Since the Classic Client handles this value directly from the IDE changing “Max. no. of XML records to send” property from Tools > Options, I have been requested if there is a more flexible way to manage this key in the ClientUsersSettings.config file.
I have then tried, in this blog, to mimic what Classic Client does and developed a simple page and codeunit to let the user change dynamically the value for this key and if the key is not present, by adding it directly to the ClientUsersSettings.config file with the desired value (this would also make the Hotfix deployment faster).
The code in the attached .txt file is quite simple and is based on .NET interoperability using the following:
A special thanks to Jorge Alberto Torres - DK-MBS NAV Development
This seems to be a good time of year for me to blog. When I do, I get to announce a new release of Dynamics NAV, and what could be more fun for someone in R & D? So I'm here again to tell you we shipped another version, this time Microsoft Dynamics NAV 2009 R2!
Last year, I had these philosophical thoughts to open the dialog:
"Microsoft Dynamics NAV 2009 was a release of courage. We made big bets. We wanted nothing short of transformation. And we accomplished our goal, shipping what is arguably the most significant release in Microsoft Dynamics NAV history.
Microsoft Dynamics NAV 2009 SP1, by contrast, is a release of precision. We listened and collaborated with you, our partners and customers. We refined. We executed predictably. And, less than 12 months after the release of Microsoft Dynamics NAV 2009, we are giving you a service pack that extends the value of Microsoft Dynamics NAV 2009 and meets our joint goal of making Microsoft Dynamics NAV simply the most productive middle-market ERP product on the planet. In this way, it is just as big as the release it is built upon."
If Microsoft Dynamics NAV 2009 was a release of courage and NAV 2009 SP1 was a release of precision, NAV 2009 R2 is a release of agility. Because of architectural investments we made in NAV 2009 and based on your increasing interest in hosting and the cloud, we were able to pull features together early and ship them to you now. Getting you value earlier and more often is something we will continue in the future, based on a more frequent release cadence. (The fact that we've shipped three versions of NAV in the past three years is indicative.)
Since RTM blogs should have an element of the retrospective (in addition to evangelism), let's rewind a bit to spring of this year. At that time, several things happened. First, we had done some investigations about running the RoleTailored client over wide-area networks, which would dramatically improve the usability of a hosted solution while reducing its cost. Second, we realized that many of the features we'd already done in NAV "7" could be shipped early. Finally, by working with the CRM Integration team in Microsoft, we both agreed that we wanted to get the CRM-to-NAV Connector out early. Thus, R2 was born. It was announced soon thereafter at Directions EMEA in May. Quickly, we got the release feature set together, spun off the appropriate people, and moved forward. Several clever Program Managers managed to get in additional features, such as Win 7 light-up integration, online payments, filtering ability on subpages, and .NET Interop. (This very cool last feature is also predicated on the architectural changes from NAV 2009...)
But we had a problem.
We were due to ship NAV 2009 SP1 in several countries in Central and Eastern Europe by the end of the year. We didn't know how we could handle another version of NAV and ship NAV 2009 SP1 to those countries that still hadn't received it. In retrospect, the answer was obvious, despite it being a course through uncharted waters: let's ship it in all the countries at the same time. So, for the first time, we give you a release of NAV in 42 countries simultaneously!
As much as I'd like to tell you about all the great value in this release (and how partners clapped for Michael Nielsen when he showed them the new database indicator feature), my team does that much better than I. They've already provided for you a set of excellent blogs on the topic.
Download a copy of Microsoft Dynamics NAV 2009 R2 on PartnerSource or CustomerSource and let us know what you think!
Once again, thanks to all the customers and partners who've worked with us on this release, giving us continuous feedback about what we should work on. We hope you enjoy NAV 2009 R2 as much as we enjoyed building it. Finally, thanks to all the people at Microsoft working their butts off on Microsoft Dynamics NAV to deliver this release to you. A greater group of passionate folks I have not met!
-DanGeneral Manager, Microsoft Dynamics NAV