Much quieter week on first line support last week with only 4 support emails / calls. Subject covered included replacement embedded report logo [Nav 2013r2], permission changes [Nav 2009 RTC] and adding an existing bespoke field off the item table to another table [Nav 2009 RTC].
However last week saw the start in earnest of the job timesheets implementation for a client [Nav 2013r2]. Started with initial configuration on the GB and US databases for the live companies for jobs, timesheets and resources. Also completed all proposed developments for GB database on a local PC ready to deliver to the client's DEV environment this week for testing. [Nav 2013r2].
Sent on quotes for specific development requests for recent client to stop document approval repeats for minor changes to a PO and stop users printing a PO when not approved. [Nav 2017]. Awaiting approval. Will then schedule the work. Also started the first permissions test for a specific department for the same client. All seems to be going well or nominated user not used Nav yet. [Nav 2017].
Also reviewed client's Nav 2016 implementation for a number of companies to identify best configuration and master file company to use. Yes on separate companies. Report on differences and made a recommendation for Nav 2018 configuration. [Nav 2016].
Finally demo'd requisitions and PO process as well as document approval in Nav on a conference call. Client to send requirements and we will then identify what can be done 'out of the box' and what developments are required. [Nav 2013].
Plans for this week focusing on data migration for live companies from GB to DE database covering the start of Nav use to date. [Nav 2017]. Full document (purchase invoice) data required so big job.
Will also chase up client re starting Nav 2018 implementation, job timesheets implementation data re legacy jobs, resources etc [Nav 2013r2] and configured database for BACS export report development [Nav 2013r2].
That's all for this week folks.
Monday, 19 March 2018
Monday, 12 March 2018
Dynamics Nav services for week ending 09/03/18
More support calls / emails last week totalling 21. Areas covered included how to get manual applications to work (user kept getting posted but no entries message from Nav) [Nav 2013], confirmed invoice posted with new dimension group values for general ledger entries [Nav 2013], resolved posting date range issue for a company (caused by multiple user domain logins in Nav and posting date assignment to other one) [Nav 2013], replicated warehouse reclass and item excel upload for multiple users [Nav 2009 RTC], fixed bug in bespoke report where excel uploads going to another user batch (caused by global text ENG and ENU being different) [Nav 2009 RTC], confirmed how to resolve blank General Prod Posting Group error [Nav 2013], confirmed how to clear blocked dimension error for invoice posting [Nav 2013], confirmed idle session limit set by client's own IT department [Nav 2013], permission changes (various clients), extending permissions role out to more departments [Nav 2009 RTC], adding new code field to bespoke table (simple no validation field) [Nav 2009 RTC] and deleting redundant user ids from Nav application [Nav 2009 Classic].
Developments completed included customer statement (make FR database statement same as GB statement) [Nav 2013] and stopping deletion of warehouse shipments where there are registered picks [Nav 2009 RTC].
Other work completed included creating 2 new instances for client for new 2 development databases for current timesheet implementation project that started last week. [Nav 2013r2].
Project work completed last week included minor objects / configuration fixes for GB to DE database move [Nav 2017] and new instances as per note above [Nav 2013r2].
Quotes submitted last week included matching batches to user ids for warehouse journals [Nav 2009 RTC] and fix for item data import re bar codes [Nav 2009 RTC].
Attended client site for tutorial on permissions work and to discuss more support needed [Nav 2017]. For same client published final proposed permission set for one department in client. [Nav 2017].
Plans for this week include new mirror image company creation in GB and US databases, confirm table data for SQL Synch and start configuration for timesheets for GB and US database. Then ready to test SQL Synch and then start development for Nav synch between companies. All for timesheet implementation project. Also report back to client on differences between multiple test companies on Nav 2016 implementation to confirm which data to use for Nav 2018 implementation.
Start permissions test for 1 of client's departments. [Nav 2017]. Send on quote for additional development work discussed last week re work flow repeat process issues. [Nav 2017].
Developments completed included customer statement (make FR database statement same as GB statement) [Nav 2013] and stopping deletion of warehouse shipments where there are registered picks [Nav 2009 RTC].
Other work completed included creating 2 new instances for client for new 2 development databases for current timesheet implementation project that started last week. [Nav 2013r2].
Project work completed last week included minor objects / configuration fixes for GB to DE database move [Nav 2017] and new instances as per note above [Nav 2013r2].
Quotes submitted last week included matching batches to user ids for warehouse journals [Nav 2009 RTC] and fix for item data import re bar codes [Nav 2009 RTC].
Attended client site for tutorial on permissions work and to discuss more support needed [Nav 2017]. For same client published final proposed permission set for one department in client. [Nav 2017].
Plans for this week include new mirror image company creation in GB and US databases, confirm table data for SQL Synch and start configuration for timesheets for GB and US database. Then ready to test SQL Synch and then start development for Nav synch between companies. All for timesheet implementation project. Also report back to client on differences between multiple test companies on Nav 2016 implementation to confirm which data to use for Nav 2018 implementation.
Start permissions test for 1 of client's departments. [Nav 2017]. Send on quote for additional development work discussed last week re work flow repeat process issues. [Nav 2017].
Monday, 5 March 2018
Dynamics Nav services w/e 2/3/18
Quieter on the first line support last week - only 13. Areas covered included confirming best report to show open items at a set date [Nav 2013], confirmed development required to show external document number on aged creditor report [Nav 2013], expansion of permissions role out [Nav 2009 RTC], report fix for excel import data load for reclass journals [Nav 2009 RTC], discussion of options and ball park cost for upgrade from 2009 to 2018 or re-implementation [Nav 2009 RTC] and fixed lack of depreciation calculation for as asset [Nav 2013r2] to name but a few.
Developments completed last week included extending dimension as columns off general ledger entry and vendor ledger entry using functionality in purchase document line pages and related tables [Nav 2013] and amended posted sales credit memo report as per spec [Nav 2013].
First proposed set of permission sets for specific end user group for client created but subject to change after queries raised. Start of an ongoing process. [Nav 2017]. Attending same client site to discuss more work this week.
Configuration work completed for a client last week was for an additional dimension with 2 values and assigning default value / force data population for selected range of general ledger codes across a number of companies on 1 database (GB) and the only company on another database (FR). [Nav 2013].
Pretty quiet week last week really.
Plans for this week include starting data migration of full transaction history for GB to DE database move [Nav 2017], start timesheet implementation when we get instance addresses confirmed [Nav 2013r2] and start Nav 2018 implementation when client confirms configuration data. [Nav 2018].
That's all folks.
Developments completed last week included extending dimension as columns off general ledger entry and vendor ledger entry using functionality in purchase document line pages and related tables [Nav 2013] and amended posted sales credit memo report as per spec [Nav 2013].
First proposed set of permission sets for specific end user group for client created but subject to change after queries raised. Start of an ongoing process. [Nav 2017]. Attending same client site to discuss more work this week.
Configuration work completed for a client last week was for an additional dimension with 2 values and assigning default value / force data population for selected range of general ledger codes across a number of companies on 1 database (GB) and the only company on another database (FR). [Nav 2013].
Pretty quiet week last week really.
Plans for this week include starting data migration of full transaction history for GB to DE database move [Nav 2017], start timesheet implementation when we get instance addresses confirmed [Nav 2013r2] and start Nav 2018 implementation when client confirms configuration data. [Nav 2018].
That's all folks.
Monday, 26 February 2018
Dynamics Nav services: week ending 23/2/18
A busy week on first line support calls - 21! Areas covered by first line support calls included bug fix for post and email on US database [Nav 2013r2], confirm where and what fields to complete for a new vendor [Nav 2013], confirmed how to release blocked dimension to allow application posting [Nav 2013], confirmed how to force dimension data for posting by GL code and how to assign defaults by GL code [Nav 2013], confirmed lack of default VPPG on GL code caused error on document creation [Nav 2013], confirmed possible data views in Nav for invoices with amount exc VAT, VAT, including VAT and VAT rate [Nav 2016], extracted permission set by user for client [Nav 2009 Classic], confirmed how to view dimensions for a posted document [Nav 2013], confirmed options to reclassify asset type and deprecation for an asset where cost and depreciation posted [Nav 2013r2], changed column layout (trend type) to follow accounting year in company [Nav 2013r2], assigned recent backup of live database to existing UAT instance [Nav 2009 RTC], confirmed Jet Professional licensing managed by client's own IT [Nav 2013], confirmed best way to remove a posted transaction (not possible) failing the use of Reverse Entry is to create correcting journal [Nav 2013], amended vat difference for currency via currency code settings [Nav 2013], set up new dimension code and 2 values and assigned defaults / forced data populated for a test company for client to test [Nav 2013], changed default location for warehouse journal for one user [Nav 2009 RTC] and confirmed how due date calculated from payment terms / document date and when the due date would then be different [Nav 2013].
Developments completed last week and delivered over the week end were a batch completed on the client's GB database that were also made to their FR database. 20 odd changes all completed and delivered. [Nav 2013].
Developments this week scheduled included amended credit note report and viewing dimension set entries on GL entries / vendor ledger entries. All Nav 2013.
Completed change log configuration once approved by client. [Nav 2017].
One project due to start this week following approval is timesheet implementation. [Nav 2013r2].
Project started last week for as GB to DE database move with us creating a test company for GB staff to check functionality on DE database. Delivered. Testing has started. [Nav 2017].
Permissions setting process to start for a client this week for one department after client confirmed requirements for department. We will send on proposed permission sets and once approved will assign to one user for them to test on behalf of their department. [Nav 2017].
That's all folks.
Developments completed last week and delivered over the week end were a batch completed on the client's GB database that were also made to their FR database. 20 odd changes all completed and delivered. [Nav 2013].
Developments this week scheduled included amended credit note report and viewing dimension set entries on GL entries / vendor ledger entries. All Nav 2013.
Completed change log configuration once approved by client. [Nav 2017].
One project due to start this week following approval is timesheet implementation. [Nav 2013r2].
Project started last week for as GB to DE database move with us creating a test company for GB staff to check functionality on DE database. Delivered. Testing has started. [Nav 2017].
Permissions setting process to start for a client this week for one department after client confirmed requirements for department. We will send on proposed permission sets and once approved will assign to one user for them to test on behalf of their department. [Nav 2017].
That's all folks.
Monday, 19 February 2018
Dynamics Nav week ending 16/2/18
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.
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, 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!
Subscribe to:
Posts (Atom)
