Off last week so this week's post includes the last 2 weeks though obviously nothing happened last week.
First line support calls resolved over the last 2 weeks included:
Queries on a new company config and discussion of data streams to and from Dynamics Nav. Suggested solution and meeting with client this week to discuss further. [Nav 2013r2].
Confirmed need to create user and assign permission sets to both UK and US database. [Nav 2013r2].
Fixed year end roll error by manually creating journals and posting. [Nav 2017].
Interesting issue re print to excel for a report and only allowing opening as pdf for one user. [Nav 2009 RTC]. Resolved itself so suspect not a Nav issue but a local Pc windows config issue.
Query raised by client as to why 2 databases in use on Nav 2017 - GB and DE. Confirmed down to country specific requirements.
Completed various fixes for project report development. [Nav 2013].
Developments completed included various job related changes for data imports and exports via dataports [Nav 2009 Classic], include validation on date field for bespoke table [Nav 2009 RTC] and add payment terms to pick report (for prepay customers) [Nav 2009 RTC].
Plans for this week include on site meeting to test new company configuration, proposed time sheet solution and discuss data flows to and from Nav. [Nav 2013r2]. Bar that a quiet week but as away last week suspect will have a few first line support calls. :)
That's it for this week folks!
Monday, 23 October 2017
Monday, 9 October 2017
Week ending 6/10/17
First line support calls resolved included commenting on Nav performance issues (likely to be SQL Server or just server performance) [Nav 2009 Classic], sent on instructions on creating and restoring a company back up for updating latest test company [Nav 2009 Classic], commented on posting block off payment journal posting [Nav 2009 Classic] and adding access to company for specific user via permission sets. [Nav 2009 Classic].
Only 1 development approved and completed last week - added bar code search field (bespoke) to put away report. [Nav 2009 RTC]. Another development (bespoke project report) delivered and tested by client last week. Amendments requested, made and delivered. Awaiting client further testing. [Nav 2013].
Sent on to client screen shots (mocked up) showing use of jobs, resources and time sheets without integration to GL avoiding complex control issues but using time sheet functionality in Nav [Nav 2013r2].
Attended a potential new client to discuss using us to assist in documenting requirements for Nav 2009 to Nav 2017 re-implementation. As a result sent on quotes for documenting requirements and providing on site training. Awaiting a response.
Finally received approval for a development quoted for 2 months ago last week. So will review requirement for developments and schedule work. [Nav 2009 Classic].
Bar that a quiet week last week.
Onwards and upwards!
Only 1 development approved and completed last week - added bar code search field (bespoke) to put away report. [Nav 2009 RTC]. Another development (bespoke project report) delivered and tested by client last week. Amendments requested, made and delivered. Awaiting client further testing. [Nav 2013].
Sent on to client screen shots (mocked up) showing use of jobs, resources and time sheets without integration to GL avoiding complex control issues but using time sheet functionality in Nav [Nav 2013r2].
Attended a potential new client to discuss using us to assist in documenting requirements for Nav 2009 to Nav 2017 re-implementation. As a result sent on quotes for documenting requirements and providing on site training. Awaiting a response.
Finally received approval for a development quoted for 2 months ago last week. So will review requirement for developments and schedule work. [Nav 2009 Classic].
Bar that a quiet week last week.
Onwards and upwards!
Monday, 2 October 2017
Week ending 29/9/17
First line support calls resolved last week included resolving posting sales document issue (down to mismatched amounts) [Nav 2013r2], remaining amount on positive adjustment on item ledger entry [Nav 2009 RTC], changing user profile issue [Nav 2013r2], confirmed how to populate global dimension 1 on purchase order header and impact on lines [Nav 2013r2] and confirmed reason for discount GL code for invoice posting down to 1p difference between unit cost and line amount. [Nav 2013r2].Also fixed issue re sales return order and population of external document number after changing vendor shipment number on warehouse receipt. [Nav 2009 RTC]. Finally confirmed how to post only some lines of payment journal. [Nav 2013].
Received request for proposed payment report off payment journals. Drafted up proposed layout in excel and send for approval. Will then quote for. [Nav 2013].
Investigated and reported back on use of jobs and resources in Nav as a replacement for existing bespoke application. Proposed solution. Requested by client to draw up some screen shots to illustrate proposed solution. [Nav 2013r2].
Development completed last week was a bespoke project spend report [Nav 2013].
Plans for this week include potential new client meeting re mapping requirements for a Nav 2009 to Nav 2017 upgrade, pull together some screen shots re proposed part use of jobs to allow full use of time sheet functionality [Nav 2013r2], delivery of bespoke project report [Nav 2013] and create step by step process based instructions on how to create a new test company as a copy of a live on the same database in Nav 2009.
So busy week this week.
That's all folks.
Received request for proposed payment report off payment journals. Drafted up proposed layout in excel and send for approval. Will then quote for. [Nav 2013].
Investigated and reported back on use of jobs and resources in Nav as a replacement for existing bespoke application. Proposed solution. Requested by client to draw up some screen shots to illustrate proposed solution. [Nav 2013r2].
Development completed last week was a bespoke project spend report [Nav 2013].
Plans for this week include potential new client meeting re mapping requirements for a Nav 2009 to Nav 2017 upgrade, pull together some screen shots re proposed part use of jobs to allow full use of time sheet functionality [Nav 2013r2], delivery of bespoke project report [Nav 2013] and create step by step process based instructions on how to create a new test company as a copy of a live on the same database in Nav 2009.
So busy week this week.
That's all folks.
Monday, 25 September 2017
Week ending 22/9/17
It has been a while so apologies for that.
Developments approved and completed last week included adding pallet summary to packing report [Nav 2009 Classic] and fix for carrying the external document number to the posted credit memo from a sales return order. [Nav 2009 RTC].
Also attended client site to discuss use of timesheets and therefore jobs. [Nav 2013r2]. The client has sent some resource and project (job) related sample data so we will configure a test company for jobs and timesheets.
Support calls last week included:
Confirming best way to amend sales order to reflect complex US sales tax based on service type. So user raising sales order does not understand US sales tax regulations by state so a finance user has to amend the SO afterwards. [Nav 2013r2].
Confirmed best way of correcting shipped resource (cannot use Undo Shipment) is by creating negative resource line on same sales order. [Nav 2013r2].
Some bug fixing re reports off packing list development. [Nav 2009 RTC].
Sent off step by step process based instructions on how to set up and use Nav consolidation. [Nav 2013r2].
Developments approved and completed last week included adding pallet summary to packing report [Nav 2009 Classic] and fix for carrying the external document number to the posted credit memo from a sales return order. [Nav 2009 RTC].
Also attended client site to discuss use of timesheets and therefore jobs. [Nav 2013r2]. The client has sent some resource and project (job) related sample data so we will configure a test company for jobs and timesheets.
Support calls last week included:
Confirming best way to amend sales order to reflect complex US sales tax based on service type. So user raising sales order does not understand US sales tax regulations by state so a finance user has to amend the SO afterwards. [Nav 2013r2].
Confirmed best way of correcting shipped resource (cannot use Undo Shipment) is by creating negative resource line on same sales order. [Nav 2013r2].
Some bug fixing re reports off packing list development. [Nav 2009 RTC].
Sent off step by step process based instructions on how to set up and use Nav consolidation. [Nav 2013r2].
Monday, 4 September 2017
Week ending 1/9/17
Better chargeable week last week with a Nav 2017 implementation kick off meeting, developments completed for new fields to pick lists [Nav 2009 RTC] and misc support for SEPA extracts [Nav 2016]. Also starting packing list development that was approved lasy week. [Nav 2009 RTC]. Will be completed this week.
First line support calls included development requests [Nav 2009 RTC], confirmed process for shipment error on sales order [Nav 2013r2], confirmed correction process re document number error on payment journal [Nav 2013r2], confirmed process for writing off a fixed asset in Nav [Nav 2013r2], confirmed work around for bank card creation error re To-Dos.[Nav 2013r2], fixed 2 separate Jet Reports from 2 different members of staff from the same client that were not showing Salesperson codes [Nav 2013r2].
Client requested details of the benefits from upgrading from Nav 2013 to Nav 2017 and a ball park estimate of our costs for completing a re-implementation. Re-implementation recommended by us as current config and use of Nav 2013 bad (not our issue, we took on the first line support a few years after the client went live). Send details on both on. This was all triggered by latest BREC (maintenance) invoice to the client from their MS Partner.
Client requested I demo Nav 2017 at their site and run through the changes from Nav 2013r2. Completing this this week.
Business definitely picking up with a fully chargeable week this week.
First line support calls included development requests [Nav 2009 RTC], confirmed process for shipment error on sales order [Nav 2013r2], confirmed correction process re document number error on payment journal [Nav 2013r2], confirmed process for writing off a fixed asset in Nav [Nav 2013r2], confirmed work around for bank card creation error re To-Dos.[Nav 2013r2], fixed 2 separate Jet Reports from 2 different members of staff from the same client that were not showing Salesperson codes [Nav 2013r2].
Client requested details of the benefits from upgrading from Nav 2013 to Nav 2017 and a ball park estimate of our costs for completing a re-implementation. Re-implementation recommended by us as current config and use of Nav 2013 bad (not our issue, we took on the first line support a few years after the client went live). Send details on both on. This was all triggered by latest BREC (maintenance) invoice to the client from their MS Partner.
Client requested I demo Nav 2017 at their site and run through the changes from Nav 2013r2. Completing this this week.
Business definitely picking up with a fully chargeable week this week.
Monday, 28 August 2017
Week ending 25/8/17
Created a support call log on our Nav 2017 so now we can track all our fixed price first line support calls. 7 calls last week covering licence session blockage [Nav 2013r2], caption changes for a bespoke table [Nav 2009 RTC], confirmed how foreign (non base) currency works on supplier ledger [Nav 2013r2] and confirmed how US sales tax works and to ignore VAT Prod Posting Group settings on US database [Nav 2013r2]. The remaining calls ended up being developments on Nav 2009 RTC.
Developments completed last week included adding outstanding quantity to PO list, taking some bespoke fields from unregistered picks to registered picks, add registered VAT number to a bespoke report using Company Info and add bespoke fields to unregistered put aways table.
Some progress re implementation project and take on of first line support but still early days. So will report on any progress next week.
Had a meeting with a client to discuss further enhancements to PO and PI dataport imports / exports to allow for more data to be passed between a legacy system and Nav 2009 Classic. Quote submitted. Awaiting approval.
Also sent off details re training at client site we provide to a potential client including a schedule of modules we cover.
Lastly submitted a quote for fixed price first line support to a potential new client and awaiting feedback.
In short there is more 'noise' out in the market so may be the quiet period is over?
That's it for this week folks!
Developments completed last week included adding outstanding quantity to PO list, taking some bespoke fields from unregistered picks to registered picks, add registered VAT number to a bespoke report using Company Info and add bespoke fields to unregistered put aways table.
Some progress re implementation project and take on of first line support but still early days. So will report on any progress next week.
Had a meeting with a client to discuss further enhancements to PO and PI dataport imports / exports to allow for more data to be passed between a legacy system and Nav 2009 Classic. Quote submitted. Awaiting approval.
Also sent off details re training at client site we provide to a potential client including a schedule of modules we cover.
Lastly submitted a quote for fixed price first line support to a potential new client and awaiting feedback.
In short there is more 'noise' out in the market so may be the quiet period is over?
That's it for this week folks!
Monday, 21 August 2017
Week ending 18/8/17
Quiet week last week for first line support calls: just the one which was for any work around for a document approval where approvers on holidays. [Nav 2013r2].
Fixed permissions issue re posting to customer ledger entry following exchange movement. [Nav 2017]. Confirmed issue for customer statement report layout and potential fixes. [Nav 2013r2 DE].
Completed Jet Training at our site last week for a client member of staff. All went well and received positive feedback after the training day. Wrote 8 new Jet Reports off the Nav 2015 demo database and emailed as they would all work off any Nav database. Also sent on post training step by step instructions on creating / posting item journals, running customer item sales report, managing reservations, creating a Jet report via Table Builder and how to view stock by location. [Nav 2015].
Developments completed last week included a bug fix [Nav 2016] re credit memos and ship to codes, ship to address default from customer sell to address and copy document issues around the area. All fixed and working.
Previous development re emailing statements now confirmed as working on UK and US databases. [Nav 2013r2]. Phew!
On the work prospects front, looking more positive. Discussing taking over first line support for a partner client and running a new Nav implementation project on their behalf. Early stages of discussion but could be a significant change for our business.
Also discussing more development with a client this week re importing PO data back into a legacy system after invoice matching [Nav 2009 Classic].
Lastly contacted by recruitment agent re implementation project for Dynamics Nav starting soon. Discussed day rate and confirmed 3 references. Heard nothing since.
That's it for this week folks!
Fixed permissions issue re posting to customer ledger entry following exchange movement. [Nav 2017]. Confirmed issue for customer statement report layout and potential fixes. [Nav 2013r2 DE].
Completed Jet Training at our site last week for a client member of staff. All went well and received positive feedback after the training day. Wrote 8 new Jet Reports off the Nav 2015 demo database and emailed as they would all work off any Nav database. Also sent on post training step by step instructions on creating / posting item journals, running customer item sales report, managing reservations, creating a Jet report via Table Builder and how to view stock by location. [Nav 2015].
Developments completed last week included a bug fix [Nav 2016] re credit memos and ship to codes, ship to address default from customer sell to address and copy document issues around the area. All fixed and working.
Previous development re emailing statements now confirmed as working on UK and US databases. [Nav 2013r2]. Phew!
On the work prospects front, looking more positive. Discussing taking over first line support for a partner client and running a new Nav implementation project on their behalf. Early stages of discussion but could be a significant change for our business.
Also discussing more development with a client this week re importing PO data back into a legacy system after invoice matching [Nav 2009 Classic].
Lastly contacted by recruitment agent re implementation project for Dynamics Nav starting soon. Discussed day rate and confirmed 3 references. Heard nothing since.
That's it for this week folks!
Subscribe to:
Posts (Atom)
