First line support calls resolved last week included setting up a new user, confirming issue with Jet report view for non Jet users [Nav 2013] and confirming initial Jet access error post install down to connection data [Nav 2013].
Some chargeable time this week! At last but just before holiday season. :(
Completed on site training for 2 days covering sale and purchase ledger. [Nav 2013]. Developments completed included bespoke report enhancements and a proposed payment report which lists documents paid as well as overall payment per vendor. [Nav 2013].
Of the 3 quotes outstanding awaiting approval, we have been asked to split one into 2 phases and send on as 2 documents. Also set up some jobs in 2 databases so client staff can set up and test SQL synch by company and specific modules. This will then free up the start of another mini project so our quote approval should follow. [Nav 2013r2]. For another client we are now agreeing a start date of early March next year for 1 project and June for another [Nav 2017]. All looking positive and if all come off we will be busy in 2018.
Plans for this week include starting permissions and role centre assignment [Nav 2013], running through proposed re implementation plan with client [Nav 2018], updating dataport for one more column of data [Nav 2009 Classic] and re-issuing document including quotes as requested by client after splitting project into 2 phases. So busy week for the week before Xmas.
That's it for this week folks. No more blogs until 2018 so have a great Xmas and New Year!
Monday, 18 December 2017
Monday, 11 December 2017
Week ending 8/12/17
Much busier week last week on first line support. Confirmed action required for purchase return order left as unposted after fully shipped and credit note raised [Nav 2009 RTC] and issues with creating and posting general journals (down to defaults on GL codes and lack of user understanding) [Nav 2013].
Did not manage to resolve missing posted sales invoice issue. Down we believe to user deleting invoice. All users super users so that would explain it. Buit surprised that Nav allows a user to delete anything posted but it does. [Nav 2009 RTC].
Had a meeting at our site with client to discuss how to get them live on Nav 2018. So far failed to go live in Nav 2016 but loads of data we can use to help with Nav 2018. Will create and publish a plan this week listing all tasks required to be completed, by whom and by when. This will ensure if followed the client will go live.
Sent on final quotes re Nav 2017 re-implementation. Awaiting client response. Potential go live not until April 2018 so more news on this next year.
Quote submitted for new company config for client to approve. [Nav 2016] Go live Jan 2018 so again more news on this next year.
Confirmed significant quotes to a client will be reviewed in Jan 2018. [Nav 2013r2].
Plans for this week showing an improvement in trade - at last - though with only 1 client at the moment. 2 days on site training booked for last this week and report quote approved late last week which we started Friday. This will be completed today / tomorrow.
That's all folks.
Did not manage to resolve missing posted sales invoice issue. Down we believe to user deleting invoice. All users super users so that would explain it. Buit surprised that Nav allows a user to delete anything posted but it does. [Nav 2009 RTC].
Had a meeting at our site with client to discuss how to get them live on Nav 2018. So far failed to go live in Nav 2016 but loads of data we can use to help with Nav 2018. Will create and publish a plan this week listing all tasks required to be completed, by whom and by when. This will ensure if followed the client will go live.
Sent on final quotes re Nav 2017 re-implementation. Awaiting client response. Potential go live not until April 2018 so more news on this next year.
Quote submitted for new company config for client to approve. [Nav 2016] Go live Jan 2018 so again more news on this next year.
Confirmed significant quotes to a client will be reviewed in Jan 2018. [Nav 2013r2].
Plans for this week showing an improvement in trade - at last - though with only 1 client at the moment. 2 days on site training booked for last this week and report quote approved late last week which we started Friday. This will be completed today / tomorrow.
That's all folks.
Monday, 4 December 2017
Week ending 1/12/17
First line support calls resolved last week included changes to table captions for a bespoke table [Nav 2009 RTC] and taking a client through how to create a new customer [Nav 2013]. So another quiet week on the first line support side.
Had a number of issues with loading a development for client UAT onto their test database but this was eventually resolved by their MS Partner. Hopefully client testing this week. [Nav 2009 Classic].
No developments completed as no quotes signed off.
But prospects still looking good.
Due to send out more quotes this week for a report development [Nav 2013] and company creation / configuration / data migration [Nav 2016]. Also discussing some one off on site training needed urgently this week.
Client been in touch this week to discuss next steps re implementation and how to get the client to a go live on Nav 2018. Original implementation was on Nav 2017 but client failed to go live. Hence the need for our help this time.
Getting to the final stages of spec'ing out a quote for a database move from 2 to 1 databases [Nav 2017]. Will get quote out with supporting document this week. Potential go live data April 2018.
We need to chase up any progress on other significant quotes that need to be approved [Nav 2013r2]. Some were due to be started last week so presume client deadline for go live has changed. I am guessing as we have now hit December, both quotes will be deferred until Jan / Feb 2018.
Oh and largest fixed price first line support client on an annual renewal will send on PO to confirm renewal this week. [Nav 2009 Classic].
Bar that don't forget Nav 2018 published last week. So if you want to see it, contact us - we have installed on PC here.
That's it folks!
Had a number of issues with loading a development for client UAT onto their test database but this was eventually resolved by their MS Partner. Hopefully client testing this week. [Nav 2009 Classic].
No developments completed as no quotes signed off.
But prospects still looking good.
Due to send out more quotes this week for a report development [Nav 2013] and company creation / configuration / data migration [Nav 2016]. Also discussing some one off on site training needed urgently this week.
Client been in touch this week to discuss next steps re implementation and how to get the client to a go live on Nav 2018. Original implementation was on Nav 2017 but client failed to go live. Hence the need for our help this time.
Getting to the final stages of spec'ing out a quote for a database move from 2 to 1 databases [Nav 2017]. Will get quote out with supporting document this week. Potential go live data April 2018.
We need to chase up any progress on other significant quotes that need to be approved [Nav 2013r2]. Some were due to be started last week so presume client deadline for go live has changed. I am guessing as we have now hit December, both quotes will be deferred until Jan / Feb 2018.
Oh and largest fixed price first line support client on an annual renewal will send on PO to confirm renewal this week. [Nav 2009 Classic].
Bar that don't forget Nav 2018 published last week. So if you want to see it, contact us - we have installed on PC here.
That's it folks!
Monday, 27 November 2017
Week ending 24/11/17
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.
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, 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)
