Dynamics Nav services: week ending 27/4/18

7 support calls / emails last week covering removal of unposted cash journal posting lines [Nav 2009 Classic], suggested solution to excel export error from report [Nav 2009 RTC], solution (dataport) for general ledger entries data extract as copying / pasting crashes [Nav 2009 Classic], set up missing general posting setup for assembly order posting [Nav 2013r2], bug fix for posted sales invoice report that shows all picks (text to text error as more picks than expected) [Nav 2009 RTC], confirm (and do via TeamViewer) to load amended table object [Nav 2017] and using Copy Doc where sales invoice posted in error [Nav 2009 RTC].
Received client full sql backup and successfully restored to a local database. Investigated client requirements and then put in a few quotes for fixes to client database re remittance advice (posted not the same layout as unposted) and a bespoke remittance report. [Nav 2013r2]. Awaiting approval.
Also confirmed you can easily change a database assigned to a Nav instance [Nav 2016].
Bar that a quiet week last week. Attended client site to successfully deliver, test and hand over development to add Post and Send to a sales order [Nav 2016, yes in Nav 2017 but not 2016!].
No client visits scheduled work for this week. So looks like another quiet week.
That's all folks.

Dynamics Nav services: week ending 20/4/18

Only 2 support calls / emails last week: query on bin for reclass journal [Nav 2009 RTC] and adding a new field to a bespoke table re creation date which included some code. [Nav 2009 RTC].
Also received a query on previously tested development re prepayments off POs. The result was a slight change to the development to allow the end user to force roundings off prepayment stats without changing the PO status and therefore triggering document approval. [Nav 2017].
Received 1 support call for customer that is on stop so that has been left unanswered for now [Nav 2013]. Customer still on stop as no payment received and no response to emails requesting payment. FPC Credit Control department about to start chasing payments this week.
Attended client site to run through jobs and time sheets implementation / development. Went well. Some minor changes completed and now awaiting client to confirm permissions required for the jobs and time sheets and then they will roll out testing to end users. [Nav 2013r2].
Major issue for FPC last week was a small electrical sub station fire Wed night just outside our office. No major damage but next morning no Internet (Virgin Cable) across some (not all weirdly) PCs / Laptops. Escalated to Virgin and technician came out to investigate / fix Saturday. So back on line now. Affected work last week so not much else to report on for the blog.
The main plan for this week is an on site attendance all day Wed to load in a development / provide support. [Nav 2016].
That's all folks!

Dynamics Nav services: w/e 13/4/18

Apologies for the delay in the blog this week - I was training at site yesterday re Nav 2017 to a couple of Nav consultants on the changes since Nav 2013r2. Major ones are always listed on the web but minor more significant from an end users perspective are not.
Support calls last week totalled 12 (up from the previous week) covering areas including set up and use of assembly orders [Nav 2013r2], permissions issues [Nav 2017, Nav 2013], sales invoice report layout issue re logo and company details [Nav 2009 RTC], year end close process run through via TeamViewer [Nav 2013] and some minor changes to developments recently delivered [Nav 2017].
Development completed last week after quote approved included page action to change Pending Prepayment status on PO to Released if all prepaid invoices are paid [Nav 2017].
Completed step by step process based instructions for jobs and time sheets implementation and delivered to client last week. Last set of enhancements and bugs fixed last week for jobs and time sheets development so this week will demo to client. [Nav 2013r2].
Plans for this week include on site training of consultants (mentioned at start of blog) and first run through jobs and time sheets implementation [Nav 2013r2]. Started work on how extensions work on Nav 2018 and made some progress. Need to finish this and bottom out how this works for Dynamics 365 and then we can formally quote for work for a potential new client.
A noteworthy business point arose this week - for the first time ever I have had to put a client on stop. Yesterday. A real shame and not something I thought (given my experience in running finance departments over 30 years) I would ever have to do. Never mind a first time for everything. Affects their first line support and all developments / quotes now on hold.
That's it for this week folks.

Dynamics Nav services: w/e 6/4/18

Another quiet week on first line support (must be Easter!). Subjects covered included how to create a VAT only invoice [Nav 2013r2], how to apply entries between currency codes (or correct error where entries in different currency codes on the same customer account) [Nav 2013] and resolve new permissions issue [Nav 2013].
Last week's work focused on the job time sheet implementation for a client [Nav 2013r2]. Basically configuration testing followed by development testing for all developments completed on UK and US database. Nearly complete so will do end to end process test this week, create step by step process based instructions and then send onto the client requesting UAT.
The only other development completed last week was the removal of the document approval repeat process for prepayment % change on PO [Nav 2017].
Requests for quotes last week included PO change of status off Prepayment Pending when prepaid invoice paid (client confirming rule, then we will quote) [Nav 2017] and use of POP and requisitions specific to client needs (requires us to mark requirements as configuration, developments or cannot do and then quote for work) [Nav 2013].
Not a squeak from client who was going live on Nav 2018 1st April but then they did not get the data together to allow us to do it. Need to contact client re new go live data and when data available to us so we can get on with.
That's it folks.

Dynamics Nav services: week ending 30/3/18

Just a quick blog as we have just had an Easter break. Support calls / emails last week totalled 6. Subjects covered included GL code error (very strange one this - client used item number but could not create line without getting an error message re GL code, down to item config) [Nav 2013r2], permissions issue resolved [Nav 2017], issue re item tracking on physical inventory journal [Nav 2017] and confirmed how to import objects into dev environment (step by step process based instructions) [Nav 2017].
Developments completed last week included: fix to stop recurring document approval process when expected receipt date changed [Nav 2017], stop users printing / sending POs pre approval [Nav 2017], BACS export report [Nav 2013r2], post and send on a sales order [Nav 2016]
Ongoing permissions work for 2 clients [Nav 2009 RTC][Nav 2017] which will continue this week. Hoping both (one for a single department, the other client for the whole company) will be completed in the next 2 weeks.
On the jobs and timesheets project, SQL Synch now working (work done by client IT) so this week we will convert and load UK and US resources to each live company on each database (US, GB), complete all remaining developments, complete development testing, complete step by step process based instructions supported by screen shots showing the whole new process and then hand over to the client for extensive user testing. [Nav 2013r2].
That's all for this week folks!