Version 0.14.2

5545 ImportRefNo db migration: ensure field does not exist before creating it

To solve a client deployment problem with KensiumComm – where POS was installed at one location, but not the others – the ImportRefNo field was added to the register’s DbPatch.
However, this caused additional problems when the POS migration for this field was run.
The workaround is to add a check in the POS migration to ensure the field does not exist before attempting to add it.