Still no movement on sizeable quotes to clients re approval [Nav 2013r2] and scheduling the work (1 element required by Friday this week) so no developments last week and none scheduled for this week.
One small quote submitted for approval (minor report change) and waiting to hear. [Nav 2009 RTC].
Ongoing discussion re a client moving to 1 database from 2. Decision made to use 1 specific database and client will be in touch this week to confirm next steps and whether we are involved or not. [Nav 2017].
Another ongoing discussion re a report quote required from us for a bespoke customer report on deliveries. Key question is grouping required for customers which is not defined by customer posting group but by item sold. Weird so queried. [Nav 2016].
Also chased up potential quote re company creation for a client. Awaiting details of the companies and report required. [Nav 2016].
Quiet week on first line support as well - 2 calls from the same client re issues on stock quantity reports (inconsistent, down to different measures on location and lot (fixed for one, open for the other) so resolved) and a report error out due to an item being created with a single digit code (created in error and report looks using COPYSTR for specific characters / groups of characters so needs at least 3 character code). Latter fixed by filtering out erroneous item code. [Nav 2009 RTC].
Prospects are really very good at the moment with plenty of potential work but nothing approved as yet.
So another quiet week.
Monday 27 November 2017
Monday 20 November 2017
Week ending 17/11/17
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!
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 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.
Subscribe to:
Posts (Atom)
