Quieter week on first line support - only 11 support calls / emails. These covered query on posted sales invoice print layout for 1 database different to another [Nav 2013], 'feature' of preview different view to pdf version of document print fixed by layout change [Nav 2013], block dimension values as change to configuration [Nav 2016], permissions issue on fixed assets and view of posted purchase documents [Nav 2013], confirmed where to enter customer VAT registration number [Nav 2013], confirmed how to filter posted sales invoice list by using posting description as part of invoice creation process [Nav 2013], confirmed issue re bank ledger entry caused by not posting payment at bank account level [Nav 2013r2], run through how to close year ends [Nav 2013] and cleared posting error re project dimension code total block [Nav 2013].
Also created step by step process based instructions on how to create a receipt posting and apply entries as part of this process and independently [Nav 2013] and cleared BACS payment journal after number series error.
Development completed last week was a fix for service change log table. If you use all 80 characters for the email address for a service contract it will error out on character length once you lock the contract. [Nav 2013r2] Fixed for GB and US databases. Took a while to find. A bug!
Quote for new client for change log set up and permissions starter work approved [Nav 2017]. Permissions will start when quoted for department's requirements confirmed. Started proposed change log configuration last week and will send on for approval today. Once approved we will set the change log up.
Developments to be completed this week include roll out of GB database developments to FR database (once client has confirmed which ones required) [Nav 2013], credit note document report changes (again once marked up changes confirmed by client) [Nav 2013] and start to look at changes required for FR customer statement report [Nav 2013].
Also planned for this week is attend recent new client site to discuss next steps re our support.
So busy week! That is all folks.
Monday, 19 February 2018
Monday, 12 February 2018
Dynamics Nav - week ending 9/2/18
Another busy week on first line support with the total number of calls / emails reaching 31! Issues raised and resolved included batch purchase invoice posting (how to do this) [Nav 2013], resolving permission issues as a result of rolling out appropriate permission sets by user [Nav 2009 RTC, Nav 2013 and Nav 2016], number series error arising from initial opening data load with same document number as current number series [Nav 2013], confirmed how applies to id gets populated [Nav 2013], resolved exchange rate revaluation dimension error issue [Nav 2013 *2], adding existing report to a page [Nav 2009 RTC], updating default general and VAT product posting groups after change of general posting set up [Nav 2013], update of VAT posting set up after changes to general posting set up [Nav 2013], confirmed reason for direct posting and how to be used for vendor posting group links and as a result recommended change of set up for GL code [Nav 2013], confirmed Preview report option not as good as other print options as it may show not show all lines but all other options do (specific issue re aged creditor report) [Nav 2013], confirmed no Item Copy function off item page card (only in AU country specific version) [Nav 2016, Nav 2018], issue on sent to excel / copy and paste formats lost down to windows not Nav [Nav 2013] and confirmed where to find GL entry creation date (off GL registers) [Nav 2017].
Also confirmed object changes over last year for client's auditors on 2 databases, ran change log entries report, confirmed permission sets by user and sent copy of our support log for last year [Nav 2017].
Developments completed last week were only minor amendments to existing developments following client review and use which included roll out of new bespoke field to purchase credit memos, change to BACS extract report and extra sign off boxes for bespoke proposed payment report. [Nav 2013].
Amended and sent on timesheet implementation proposal to client following discussion the previous week re data synch between Nav databases and Nav companies. Awaiting approval and then an agreed go live date. Also created 2 quotes for potential new client for change log configuration and permissions assignment and testing. Awaiting response / approval and then if approved we will schedule the work. [Nav 2017].
Quote for new reports off Nav 2016 / 2018 approved. Awaiting update from client whether implementing Nav 2018 or continuing with Nav 2016 application. Once we have this confirmed we will start the report developments. As a result of approval we now have latest backup of Nav 2016 database on a local PC here just in case go live will be on Nav 2016 not Nav 2018. More work associated with this implementation will come out of final client approval of which Nav to implement and which Nav 2016 company should be used for go live.
Plans for this week include preparation for the start of an Nav 2017 data move project from GB to DE database for some companies. This week we will request latest full sql database backups for both databases and then restore these to a local PC in the FPC office. Then next week we will start to create a test company on the DE database for end user functionality testing. [Nav 2017].
Bar that a quiet week. That is all folks!
Also confirmed object changes over last year for client's auditors on 2 databases, ran change log entries report, confirmed permission sets by user and sent copy of our support log for last year [Nav 2017].
Developments completed last week were only minor amendments to existing developments following client review and use which included roll out of new bespoke field to purchase credit memos, change to BACS extract report and extra sign off boxes for bespoke proposed payment report. [Nav 2013].
Amended and sent on timesheet implementation proposal to client following discussion the previous week re data synch between Nav databases and Nav companies. Awaiting approval and then an agreed go live date. Also created 2 quotes for potential new client for change log configuration and permissions assignment and testing. Awaiting response / approval and then if approved we will schedule the work. [Nav 2017].
Quote for new reports off Nav 2016 / 2018 approved. Awaiting update from client whether implementing Nav 2018 or continuing with Nav 2016 application. Once we have this confirmed we will start the report developments. As a result of approval we now have latest backup of Nav 2016 database on a local PC here just in case go live will be on Nav 2016 not Nav 2018. More work associated with this implementation will come out of final client approval of which Nav to implement and which Nav 2016 company should be used for go live.
Plans for this week include preparation for the start of an Nav 2017 data move project from GB to DE database for some companies. This week we will request latest full sql database backups for both databases and then restore these to a local PC in the FPC office. Then next week we will start to create a test company on the DE database for end user functionality testing. [Nav 2017].
Bar that a quiet week. That is all folks!
Monday, 5 February 2018
Week ending 2/2/18
An all time high for first time support calls in the week. 40! Issues raised and resolved included permission issues [Nav 2009 RTC, Nav 2013, Nav 2016], new users [Nav 2013], missing VAT Posting Setups [Nav 2013], minor report changes *3 [Nav 2009 RTC], exchange rate valuation issues [Nav 2013], non existent accounting period issue causing report to not run [Nav 2013], permissions roll out to more users [Nav 2013], rapidstart data issue [Nav 2016], missing General Posting Setup [Nav 2013], confirmation of reminders process [Nav 2013], confirm how to run customer statements [Nav 2013], new field for bespoke table [Nav 2009 RTC], confirmed date format issue on copy and pasting journal from excel [Nav 2016] and resolve end of number series error [Nav 2013]. So very busy week. We have a mix for time and materials for first line support and fixed price support for our clients.
Completed data migration for client for customers and vendors. [Nav 2016].
Attended client site to discuss 2 databases have the same job (and related table) data. SQL synch to be used but this creates the exact same data for the same company for selected tables in the other database. We will use Nav via CHANGECOMPANY to update the data in each live company. Once this resolved, project start date re jobs and time sheets will be confirmed. [Nav 2013r2].
Developments completed last week (all Nav 2013) included adding table field to page list, new fields for purchase invoices to allow use of unposted invoices as invoice register, amendment to invoice posting routine to check values in header and valid vendor bank details, default all new vendors to be blocked all, add more file export options for Fast Payments and amendments to existing sales and credit note posted print reports to allow description lines to show.
Plans for this week include chasing up debt owed by a client, once that is resolved roll out all GB database development to FR database [Nav 2013], confirm whether CHANGECOMPANY option for auto updates will work (see above) [Nav 2013r2].
No news on potential new client from a few weeks ago so looks like we did not get. [Nav 2017].
That's all folks!
Completed data migration for client for customers and vendors. [Nav 2016].
Attended client site to discuss 2 databases have the same job (and related table) data. SQL synch to be used but this creates the exact same data for the same company for selected tables in the other database. We will use Nav via CHANGECOMPANY to update the data in each live company. Once this resolved, project start date re jobs and time sheets will be confirmed. [Nav 2013r2].
Developments completed last week (all Nav 2013) included adding table field to page list, new fields for purchase invoices to allow use of unposted invoices as invoice register, amendment to invoice posting routine to check values in header and valid vendor bank details, default all new vendors to be blocked all, add more file export options for Fast Payments and amendments to existing sales and credit note posted print reports to allow description lines to show.
Plans for this week include chasing up debt owed by a client, once that is resolved roll out all GB database development to FR database [Nav 2013], confirm whether CHANGECOMPANY option for auto updates will work (see above) [Nav 2013r2].
No news on potential new client from a few weeks ago so looks like we did not get. [Nav 2017].
That's all folks!
Monday, 29 January 2018
Week ending 26/1/18
First line support calls for last week totalled 15 so another busy week on first line support. Calls included permissions issues [Nav 2016, Nav 2009 RTC, Nav 2013], set up of new users [Nav 2016], fiscal year set up [Nav 2016], confirmed no access to Nav as service stopped and needed to be restarted [Nav 2013], item numbering options [Nav 2013r2], confirmed how to create a payment journal and apply entries either manually or using Suggest Vendor Payments [Nav 2013] and confirmed and fixed issue with bespoke code to post and email sales order on US database (works on UK database) [Nav 2013r2].
Attended client site to provide ad hoc on site support. Resolved a number of end user issues that would have been raised on first line support log otherwise.
Development completed last week included adding vendor bank fact box to vendor card and list pages [Nav 2013]. Created page for licence permission by object ids for client to confirm what bespoke number series client has in their licence. Very useful. [Nav 2013].
Started permissions assignment and testing with client last week. This will continue for a few weeks. We currently have 2 clients where we have set up suggested permission sets and in the process of testing by representative end users for departments. Possibility of a third client (new to us) but we will get more news on that this week.
Plans for this week include a demo of Nav 2018 via TeamViewer to a current client, attend a meeting to discuss timesheet implementation (already quoted for) [Nav 2013] and completing a set of developments for a client. [Nav 2013].
Also hoping to hear back from a potential new client re quoting for permission sets and change log set up after reviewing their Nav 2017 database last week.
That's all folks.
Attended client site to provide ad hoc on site support. Resolved a number of end user issues that would have been raised on first line support log otherwise.
Development completed last week included adding vendor bank fact box to vendor card and list pages [Nav 2013]. Created page for licence permission by object ids for client to confirm what bespoke number series client has in their licence. Very useful. [Nav 2013].
Started permissions assignment and testing with client last week. This will continue for a few weeks. We currently have 2 clients where we have set up suggested permission sets and in the process of testing by representative end users for departments. Possibility of a third client (new to us) but we will get more news on that this week.
Plans for this week include a demo of Nav 2018 via TeamViewer to a current client, attend a meeting to discuss timesheet implementation (already quoted for) [Nav 2013] and completing a set of developments for a client. [Nav 2013].
Also hoping to hear back from a potential new client re quoting for permission sets and change log set up after reviewing their Nav 2017 database last week.
That's all folks.
Monday, 22 January 2018
Week ending 19/1/18
Another very busy week including a visit to a new potential client. Signed off NDA after visit so we will see what happens with them.
12 first line support calls resolved last week. Subjects included payment journal process queries [Nav 2013], ongoing permissions issues (as part of current permission testing process) but both down to policy of who has access to specific tables [Nav 2013], character limit issue on service contract (could not replicate either on local database or client live database) [Nav 2013r2], showed how to amend service invoice due date after created [Nav 2013r2], found bug for GL type report in Nav 2017 (did not fix), confirmed applications for 2 payments [Nav 2013], adding new users [Nav 2016], setting up new VAT Prod Posting Groups and completed VAT Setup [Nav 2016], deleted old redundant session on Nav via table (page action delete would not work) [Nav 2013], activated change log for vendor bank accounts [Nav 2013] and fixed issue with trend report via create new fiscal year. [Nav 2016].
Finally received approval for permissions related work for a client [Nav 2009 RTC] so started the work last week with 1 end user for a specific department.
Confirmed best solution minimal development for using additional approvals in document approvals for cost centre dimensions. First approvers use associated purchaser code to project code dimension. [Nav 2013].
Development completed last week added pick note numbers to posted sales invoice report. [Nav 2009 Classic].
Had a conference call with client to discuss next steps re Nav 2018 implementation. Client to confirm preferred go live data given peak in business activity coming up in the next few months.
Confirmed quotes for a number of reports for new Nav implementation. Approved but yet to schedule the development work.
So a very busy week. Attending client site this week to provide ad hoc support for 2 days so will be another busy week. Should find out the proposed go live date for Nav 2018 implementation this week. And perhaps hear back from potential client re the next steps.
That is all folks!
12 first line support calls resolved last week. Subjects included payment journal process queries [Nav 2013], ongoing permissions issues (as part of current permission testing process) but both down to policy of who has access to specific tables [Nav 2013], character limit issue on service contract (could not replicate either on local database or client live database) [Nav 2013r2], showed how to amend service invoice due date after created [Nav 2013r2], found bug for GL type report in Nav 2017 (did not fix), confirmed applications for 2 payments [Nav 2013], adding new users [Nav 2016], setting up new VAT Prod Posting Groups and completed VAT Setup [Nav 2016], deleted old redundant session on Nav via table (page action delete would not work) [Nav 2013], activated change log for vendor bank accounts [Nav 2013] and fixed issue with trend report via create new fiscal year. [Nav 2016].
Finally received approval for permissions related work for a client [Nav 2009 RTC] so started the work last week with 1 end user for a specific department.
Confirmed best solution minimal development for using additional approvals in document approvals for cost centre dimensions. First approvers use associated purchaser code to project code dimension. [Nav 2013].
Development completed last week added pick note numbers to posted sales invoice report. [Nav 2009 Classic].
Had a conference call with client to discuss next steps re Nav 2018 implementation. Client to confirm preferred go live data given peak in business activity coming up in the next few months.
Confirmed quotes for a number of reports for new Nav implementation. Approved but yet to schedule the development work.
So a very busy week. Attending client site this week to provide ad hoc support for 2 days so will be another busy week. Should find out the proposed go live date for Nav 2018 implementation this week. And perhaps hear back from potential client re the next steps.
That is all folks!
Monday, 15 January 2018
Week ending 12/1/18
Wow! Much busier last week on all services. 11 support calls in the week covering assigning new dimension group and allocating to journals [Nav 2017], confirmed you can delete unposted bank recs [Nav 2013], how to correct VAT posting off a document (do it properly, no short cuts) [Nav 2013r2], sorted permissions issue for posting vendor related journal [Nav 2016], set up new user [Nav 2009 Classic], collect rapid start services configuration lines from our local database (backup of clients) after user deleted lines (suggested client approves quote to change all users from SUPER to something more appropriate) [Nav 2009 RTC], fix currency page crash caused by exchange rate added but used 0 not 1 for relational exchange rate [Nav 2013] and confirmed issue with general journal document numbers in terms of immediate fix and planning for the future to avoid the issue. [Nav 2013].
Developments signed off last week which we started last week and are due to deliver / complete this week. [Nav 2013]. Included adding reason code to document lists, assigning default values for tables in the InitValue field and add fact box off purchase documents card showing vendor bank details.
On other matters, client confirmed that sql synch testing between GB and US databases for specific tables and companies will start this week after client's IT department configured and set up. Once the testing is complete, time sheet project to be planned in terms of start date and go live. [Nav 2013r2].
Also have a conference call today to start a Nav 2018 implementation for a client. Failed to go live on Nav 2016 so the call is about agreeing responsibilities and ownership. Our involvement on Nav 2016 implementation down to helping as and when required. This time our involvement includes project management.
Other plans for this week include delivering developments completed [Nav 2013], completing remaining developments approved and delivering [Nav 2013], investigating options for additional document approvers (how it works, can it be tweaked to work as required by client) and general support.
Last thing - attending potential client site (local) this week to discuss their requirements and how / if we can help.
So all in all business has picked up and the next 6 months looking busy!
That's it for this week folks.
Developments signed off last week which we started last week and are due to deliver / complete this week. [Nav 2013]. Included adding reason code to document lists, assigning default values for tables in the InitValue field and add fact box off purchase documents card showing vendor bank details.
On other matters, client confirmed that sql synch testing between GB and US databases for specific tables and companies will start this week after client's IT department configured and set up. Once the testing is complete, time sheet project to be planned in terms of start date and go live. [Nav 2013r2].
Also have a conference call today to start a Nav 2018 implementation for a client. Failed to go live on Nav 2016 so the call is about agreeing responsibilities and ownership. Our involvement on Nav 2016 implementation down to helping as and when required. This time our involvement includes project management.
Other plans for this week include delivering developments completed [Nav 2013], completing remaining developments approved and delivering [Nav 2013], investigating options for additional document approvers (how it works, can it be tweaked to work as required by client) and general support.
Last thing - attending potential client site (local) this week to discuss their requirements and how / if we can help.
So all in all business has picked up and the next 6 months looking busy!
That's it for this week folks.
Monday, 8 January 2018
Week ending 5/1/18
Happy New Year! Hope you all had a great Xmas and New Year.
So last week was quiet for first line support - only 2 support calls all week, one on a weird permissions issue (actually a licence issue) off a FR database where GB objects loaded [Nav 2013] and the other was a Aged Debt ageing issue caused by no financial year created for current year [Nav 2013r2] - but we were busy on some configuration for a new company (all completed and included some data migration) [Nav 2016] and starting the permissions set and role centre assignment for a client which took most of the week [Nav 2013].
Heard from a client (MS Partner) for the first time in a year confirming they need a quote for a BACS extract report from Nav 2013r2. Just waiting for spec at the moment - then we will send on quote.
Also fixed aged stock report (bespoke report) where ageing based on purchase history did not include enough detail. Original report looked at last 10 transactions - extended to 20. [Nav 2009 Classic].
Sent 1 quote last week for including pick numbers on posted sales invoice print [Nav 2009 RTC]. Not yet approved. Booked for on site training at a client site for 2 days end of January 2018 [Nav 2013].
This week's plans include testing user permission and role centre assignment with a user per client department [Nav 2013] and then if all ok role out to all users [Nav 2013] and a conference call with client's MS Partner to agree working relationship [Nav 2013].
One of last year's significant implementation quotes was approved and work is scheduled to begin mid Feb 2018 [Nav 2017].
That's it folks.
So last week was quiet for first line support - only 2 support calls all week, one on a weird permissions issue (actually a licence issue) off a FR database where GB objects loaded [Nav 2013] and the other was a Aged Debt ageing issue caused by no financial year created for current year [Nav 2013r2] - but we were busy on some configuration for a new company (all completed and included some data migration) [Nav 2016] and starting the permissions set and role centre assignment for a client which took most of the week [Nav 2013].
Heard from a client (MS Partner) for the first time in a year confirming they need a quote for a BACS extract report from Nav 2013r2. Just waiting for spec at the moment - then we will send on quote.
Also fixed aged stock report (bespoke report) where ageing based on purchase history did not include enough detail. Original report looked at last 10 transactions - extended to 20. [Nav 2009 Classic].
Sent 1 quote last week for including pick numbers on posted sales invoice print [Nav 2009 RTC]. Not yet approved. Booked for on site training at a client site for 2 days end of January 2018 [Nav 2013].
This week's plans include testing user permission and role centre assignment with a user per client department [Nav 2013] and then if all ok role out to all users [Nav 2013] and a conference call with client's MS Partner to agree working relationship [Nav 2013].
One of last year's significant implementation quotes was approved and work is scheduled to begin mid Feb 2018 [Nav 2017].
That's it folks.
Subscribe to:
Posts (Atom)
