Week ending 3/11/17

First line support calls resolved included confirmed shipping cost should not be an item but a GL code (in future could be an item charge) [Nav 2013r2], bug fix on pick report bespoke field where client changed field length in table but not report [Nav 2009 RTC] and confirmed issue re payment discount date between 2 databases different due to bespoke code on 1 database - suggested solution using payment terms config table [Nav 2013]. Fixed pick report re retrieval of vendor shipment number. [Nav 2009 RTC].
Also resolved direct contact via email (not a client) for a user who did not know how to remove a filter on Nav 2009 Classic for items.

2 quotes approved last week and as a result...
Developments completed last week included new fields for bespoke journal table (impacted 10 other objects so major change but all done and working) [Nav 2009 RTC] and adding a running total quantity to the item ledger entry page. [Nav 2009 RTC].

Still 2 quotes outstanding but significant changes made to one quote re time sheets as a result of requirement to run time sheets off 1 of 2 databases in operation - UK and US. Proposed solution synchronised jobs / time sheets between the 2 databases using trigger points and xmls in Nav. Client alternative solution was to use SQL synch. No expertise on this no client will implement. Expect to amend quote again assuming SQL synch works. [Nav 2013r2].

Working on another quote for a client regarding a weekly trend sales report based on dispatched sales and forward orders. Queried change to configuration re 2 sale / customer types and awaitng confirmation from client. Then we will send quote on. Also had a discussion with same client re upgrade / re-implementation to Nav 2017 or from 1/12/17 to Nav 2018 and as a result of the conversation confirmed object changes / bespoke objects on their current database and what this would mean for any upgrade / reimplementation. They are not yet live on Nav. [Nav 2016].

That's it for this week folks.