New client on fixed price first line support signed up last week. [Nav 2017]
First line support calls resolved included setting up credit note and invoice for posting to correct VAT errors (more accounting support than Nav support) [Nav 2013], confirmed due date from payment terms for a purchase invoice did not reflect vendor payment terms as user had changed these on the invoice [Nav 2013r2], latest client development (significant as it involved warehousing) tested successfully with client and loaded into live as a result [Nav 2009 RTC], purchase invoice approved via Nav would not post as document re-opened after receipt posted [Nav 2013r2], confirmed consolidation business can have any currency code as a base currency {Nav 2017] and confirmed default Qty to Ship on US database not blank despite settings in S&R Set up as a bug. [Nav 2013r2]. Fixed via single line code to call existing function call.
So busier week on first line support!
Got a little bit more exciting at the end of last week as we were asked about 2 bits of potential work. For one we are expecting the formal request via email this week to quote to set up some new companies and new report development [Nav 2016]. The other involves confirming whether a client can use on country specific database rather than 2. We have asked to look at one specific issues and report back which we will do as part of our fixed price first line support - if it is possible we will then quote for. May lead to some chargeable work. [Nav 2017].
Chased up 2 previous large quotes for work last week to see whether timetable required by client still wanted (live in December 2017 for one) in which case need to start the work this week. Delay in approval caused by internal client resource (lack of) issues for non Nav expertise around SQL Server synching. Expecting an update this week. [Nav 2013r2].
That's all for this week folks!
Monday, 20 November 2017
Monday, 13 November 2017
Week ending 10/11/17
A very quiet week last week - both for developments and first line support.
No quotes approved as yet as no developments completed last week.
First line support queries resolved included fixing free stock for an item [Nav 2009 RTC], confirmed where external document found and how populated on customer ledger entry dataport (export) [Nav 2009 Classic], confirmed no off the shelf report for specific vendor details required [Nav 2013] and set up new user as requested with specific access to Nav [Nav 2016].
Quote sent for latter but as per above not approved as yet. Would have recommended RapidStart service for the data required but not a one off data request.
Managed to agree SLA for current client for them to move onto a fixed price first line support service.
That's all for this week folks. Looks like another quiet week this week.
No quotes approved as yet as no developments completed last week.
First line support queries resolved included fixing free stock for an item [Nav 2009 RTC], confirmed where external document found and how populated on customer ledger entry dataport (export) [Nav 2009 Classic], confirmed no off the shelf report for specific vendor details required [Nav 2013] and set up new user as requested with specific access to Nav [Nav 2016].
Quote sent for latter but as per above not approved as yet. Would have recommended RapidStart service for the data required but not a one off data request.
Managed to agree SLA for current client for them to move onto a fixed price first line support service.
That's all for this week folks. Looks like another quiet week this week.
Monday, 6 November 2017
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.
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.
Monday, 30 October 2017
Week ending 27/10/17
Developments completed last week add transfer to code to the pick report [Nav 2009 RTC] and add field to bespoke report data extract [Nav 2013].
First line support calls resolved last week included renaming companies for recent test database restore from live via SQL [Nav 2009 Classic), fixed bespoke report bug [Nav 2013], how to create new location for warehouse [Nav 2009 RTC], warehouse batch default fix to allow selection of different warehouse location [Nav 2009 RTC] and confirmed how to change default dimension value for specific general ledger code [Nav 2009 Classic]. Busy support call week!
Support call not resolved (needed up to date back up of live database) was for error bug for excel import [Nav 2009 RTC]. Backup restored to local PC so will resolve this week.
Attended client site to demo proposed time sheet use with jobs (not full functionality), run through a configured company (client configured so just needed to test) and discuss data flows (between) between 2 other applications and Dynamics Nav. As a result of the meeting, 2 quotes sent for approval. [Nav 2013r2]
Also 2 other quotes requested for a client re extra fields for a bespoke table (including changes to current excel data upload) and additional fields to manage user access rights that do not use permission sets (actually requirements of client could not be managed by table permissions). 1 quote sent and awaiting approval. Query on other requirement which will be resolved today and quote sent on. [Nav 2009 RTC].
Sent off quote for fixed price first line support to existing client to start once approved November.
So very much a quotes week.
Bar that a quiet week. That's all for now!
First line support calls resolved last week included renaming companies for recent test database restore from live via SQL [Nav 2009 Classic), fixed bespoke report bug [Nav 2013], how to create new location for warehouse [Nav 2009 RTC], warehouse batch default fix to allow selection of different warehouse location [Nav 2009 RTC] and confirmed how to change default dimension value for specific general ledger code [Nav 2009 Classic]. Busy support call week!
Support call not resolved (needed up to date back up of live database) was for error bug for excel import [Nav 2009 RTC]. Backup restored to local PC so will resolve this week.
Attended client site to demo proposed time sheet use with jobs (not full functionality), run through a configured company (client configured so just needed to test) and discuss data flows (between) between 2 other applications and Dynamics Nav. As a result of the meeting, 2 quotes sent for approval. [Nav 2013r2]
Also 2 other quotes requested for a client re extra fields for a bespoke table (including changes to current excel data upload) and additional fields to manage user access rights that do not use permission sets (actually requirements of client could not be managed by table permissions). 1 quote sent and awaiting approval. Query on other requirement which will be resolved today and quote sent on. [Nav 2009 RTC].
Sent off quote for fixed price first line support to existing client to start once approved November.
So very much a quotes week.
Bar that a quiet week. That's all for now!
Monday, 23 October 2017
2 weeks ending 20/10/17
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!
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, 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.
Subscribe to:
Posts (Atom)
