Monthly Archives: October 2013

Directions USA 2013 | Web Services and .NET Interoperability (Capabilities & Set-up)

Ok, now here is a confusing title of a session.

The session is presented by Vjeko Babic, a friend and fellow member of Partner Ready Software.

Truth is, no-one knows where the title came from and Vjeko was certainly not talking about just Capabilities and Setup, he was doing black-belt stuff.

Being in the session I started writing my blogpost like I did with Tom and Heidi’s sessions, but after 5 minutes I noticed that I was never able to keep up with his speed.

Therefore I am very happy that he wrapped up his presentation in his own blog post so I only have to link to his which is here:

As you will read in my next blog, the NAV world is changing. We need to start understanding this stuff and Vjeko’s blog is the perfect way of starting that.



Directions USA 2013 | Cash Management Features

Cash Management Features


One of the big new things in NAV 2013 R2 is cash management. Heidi Andreasen is doing a presentation on this.

Cash Management is a continue of the Cash flow features introduced in 2013.

Cash Management contains the following:

*  Payment registration

*  Bank reconciliation

*  Vendor Payments

*  SEPA Direct Debit to Customers

*  Data Exchange Framework & Schema viewer


Local vesions vs. generic features

Up until R2 cash management was mainly a local feature not being part of W1. Some countries had some, some had nothing.

NAV 2013 R2 introduces a new generic framework that talks to the local features where necessary and provides functionality in those countries who have nothing.

Introduction new features

Payment Registration

In W1 this is done in the general journals manually. Cash Management enables users to import statements.

These formats can be setup in the bank account card.

After the import has been done the system can suggest which entry to apply the payments to. The applied lines light up green.


For the ones who are left there is an option to create mapping rules, so everytime something similar happens the same application is done

Bank Reconciliation

Some customers choose to reconciliate from the bank ledger entries. This has changed t from a ui perspective


A new page has been designed that has two parts that allow matching a bank file with the bank ledger entries

Register Payments Manually

This is a new page for people who want to process payments manually

The difference here is that the new page shows all entries from all customers.

In this page users can go around and manually try to match from the paper bank statement to the outstanding invoices.


Here you can even search for amounts that have not been posted from within a min and max amount.

Vendor payments export

This is the possibility to have the system look at outstanding vendor invoices and suggest to pay them and then export them into a bank format.

When the journal is posted and the file was exported the history is kept in a register.

Bank Integration ISO 20022xml/SEPA

With 2013 R2 Microsoft ships a framework that allows users to describe a file format and NAV will generate the setup.


Bonus Feature

Microsoft has added the feature to expose account schedules as a webservice. This allows you to consume this data in NAV or in a graph.

Directions USA 2013 | Real World Upgrades

Real world upgrades


For those of you who don’t know him, Tom Wickstrom is THE upgrade specialist. He has done over 600 upgrades since 1999.

I’ve personally worked with Tom on more than 30 projects.


Tom recommends quoting upgrades fixed price. However this requires to compile a list up front with objects that cannot be merged but need redesigned.

For comparing reports Tom has a tool that removes RDLC code to be able to see real changes to the report.

Another thing that needs to be considered are changes that cannot be brought forward or features that are now available in the standard solutions.

If programming is needed for redesign this needs to be included in the price, either fixed price or on hourly bases.

Customers also have to reconsider their hardware. Is the hardware still adequate for the new version.

Another advice is to add enough time for training and emotional support since end users will have to get used to new ways of working.


Look at your customer organisation and try to estimate if there will be resistance. Resistance is a big risk in the project.

Make sure to schedule time for testing.

The customers license needs to be refreshed and tested. It happens sometimes that refreshed licenses are not good.

If it is necessary to replace hardware make sure it is there in time and test on this hardware.

Test with end user access rights, not with super. Make sure the real endusers do testing.

Make sure no one is on vacation or unavailable when you need them for the project.

During the final cutover the database will be down. This takes time and need to be calculated.


Make sure to have test script.

If you cannot test on the golive machine, make sure to test on hardware that is equivalent.

Track the test results and maintain software incidents. (SIR).

Just because a document got posted does not mean the posted document is ok. Test, test test and look at the results.

Testing is the most important part of an upgrade.

If something went wrong, why did it go wrong. Is it programming or setup? Or is the user using the system wrong. Or is the new version behaving differently and is the result good but no what the customer expects.

Go Live

Before go-live use a testing complete sheet where the customer signs that the upgrade has been tested and no more errors exist.

After this is signed new errors are no longer within fixed price. This is not to make more money but to encourage people to test.

Everyone within the team needs to be available.

Be sure to be onsite for the first 1-3 days. Help endusers and do emotional support.

Recipes for disasters

By far the biggest risk is programming in live databases after the upgrade has been started.

Little less complicated is programming in the testing database, but that needs to be synchronised with the upgrade objects.


Compressed item ledger entries in older versions cannot be upgraded, the costing will be messed off.

This feature does not exist anymore.

If someone of the team is unavailable and needed for something.