Just a quick blog as we have just had an Easter break. Support calls / emails last week totalled 6. Subjects covered included GL code error (very strange one this - client used item number but could not create line without getting an error message re GL code, down to item config) [Nav 2013r2], permissions issue resolved [Nav 2017], issue re item tracking on physical inventory journal [Nav 2017] and confirmed how to import objects into dev environment (step by step process based instructions) [Nav 2017].
Developments completed last week included: fix to stop recurring document approval process when expected receipt date changed [Nav 2017], stop users printing / sending POs pre approval [Nav 2017], BACS export report [Nav 2013r2], post and send on a sales order [Nav 2016]
Ongoing permissions work for 2 clients [Nav 2009 RTC][Nav 2017] which will continue this week. Hoping both (one for a single department, the other client for the whole company) will be completed in the next 2 weeks.
On the jobs and timesheets project, SQL Synch now working (work done by client IT) so this week we will convert and load UK and US resources to each live company on each database (US, GB), complete all remaining developments, complete development testing, complete step by step process based instructions supported by screen shots showing the whole new process and then hand over to the client for extensive user testing. [Nav 2013r2].
That's all for this week folks!
Tuesday, 3 April 2018
Monday, 26 March 2018
Dynamics Nav Services: week ending 23/3/18
More first line support calls last week (13) but still not as high as it
has been in the last few months. Areas covered included general posting
set up invalid entry (caused by defaults) [Nav 2013], viewing 3rd
dimension off GL entries page [Nav 2017], best to highlight preferred
vendors [Nav 2013], created 7 day payment terms [Nav 2013], resolving
cheque posting / printing issue [Nav 2013], resolving suggest payments
not working on vendor as balance in debit [Nav 2013], confirming simple
way to use requisitions in Nav using simple stock [Nav 2013], fixing
accounts schedules issue where no data in overview (column trend dates
issue and GL codes not selected using '...' prompt) [Nav 2013r2],
confirmed approach to ball park estimate to upgrade from Nav 2013 to Nav
2018 (we do not do upgrades but we do complete re-implementations),
confirmed purchase journal to create an invoice needs to payment type
Invoice not Payment [Nav 2013] and clear down data bug from payment
journal (Nav 2009 Classic].
Created new companies (4) and then started historic full transaction data migration last week for GB to DE move. 3 of 4 companies done. Biggest to be done this week. Will take all week as 5 years need to be migrated. [Nav 2017].
Issues with SQL Synch on jobs / timesheets implementation last week after table objects amendment load. Client's IT department resolving. As soon as resolved we will load in some resource data provided by client on both GB and US database, create some timesheets and then check is Nav Synch working for data pulls from US to GB. Then amend US non table objects and load into database. Then hand over to client for testing for a few weeks. All on DEV databases. [Nav 2013r2].
Plans for this week bar that mentioned above include completing BACS report export development for client, complete minor developments re stopping repeating document approval for minor (date related) changes on POs [Nav 2017], check with Nav 2018 implementation as to what new go live date is and go for a few days away over Easter making the most of the bank holidays.
That's all folks.
Created new companies (4) and then started historic full transaction data migration last week for GB to DE move. 3 of 4 companies done. Biggest to be done this week. Will take all week as 5 years need to be migrated. [Nav 2017].
Issues with SQL Synch on jobs / timesheets implementation last week after table objects amendment load. Client's IT department resolving. As soon as resolved we will load in some resource data provided by client on both GB and US database, create some timesheets and then check is Nav Synch working for data pulls from US to GB. Then amend US non table objects and load into database. Then hand over to client for testing for a few weeks. All on DEV databases. [Nav 2013r2].
Plans for this week bar that mentioned above include completing BACS report export development for client, complete minor developments re stopping repeating document approval for minor (date related) changes on POs [Nav 2017], check with Nav 2018 implementation as to what new go live date is and go for a few days away over Easter making the most of the bank holidays.
That's all folks.
Dynamics Nav sevices: week ending 23/3/18
More first line support calls last week (13) but still not as high as it has been in the last few months. Areas covered included general posting set up invalid entry (caused by defaults) [Nav 2013], viewing 3rd dimension off GL entries page [Nav 2017], best to highlight preferred vendors [Nav 2013], created 7 day payment terms [Nav 2013], resolving cheque posting / printing issue [Nav 2013], resolving suggest payments not working on vendor as balance in debit [Nav 2013], confirming simple way to use requisitions in Nav using simple stock [Nav 2013], fixing accounts schedules issue where no data in overview (column trend dates issue and GL codes not selected using '...' prompt) [Nav 2013r2], confirmed approach to ball park estimate to upgrade from Nav 2013 to Nav 2018 (we do not do upgrades but we do complete re-implementations), confirmed purchase journal to create an invoice needs to payment type Invoice not Payment [Nav 2013] and clear down data bug from payment journal (Nav 2009 Classic].
Created new companies (4) and then started historic full transaction data migration last week for GB to DE move. 3 of 4 companies done. Biggest to be done this week. Will take all week as 5 years need to be migrated. [Nav 2017].
Issues with SQL Synch on jobs / timesheets implementation last week after table objects amendment load. Client's IT department resolving. As soon as resolved we will load in some resource data provided by client on both GB and US database, create some timesheets and then check is Nav Synch working for data pulls from US to GB. Then amend US non table objects and load into database. Then hand over to client for testing for a few weeks. All on DEV databases. [Nav 2013r2].
Plans for this week bar that mentioned above include completing BACS report export development for client, complete minor developments re stopping repeating document approval for minor (date related) changes on POs [Nav 2017], check with Nav 2018 implementation as to what new go live date is and go for a few days away over Easter making the most of the bank holidays.
That's all folks.
Created new companies (4) and then started historic full transaction data migration last week for GB to DE move. 3 of 4 companies done. Biggest to be done this week. Will take all week as 5 years need to be migrated. [Nav 2017].
Issues with SQL Synch on jobs / timesheets implementation last week after table objects amendment load. Client's IT department resolving. As soon as resolved we will load in some resource data provided by client on both GB and US database, create some timesheets and then check is Nav Synch working for data pulls from US to GB. Then amend US non table objects and load into database. Then hand over to client for testing for a few weeks. All on DEV databases. [Nav 2013r2].
Plans for this week bar that mentioned above include completing BACS report export development for client, complete minor developments re stopping repeating document approval for minor (date related) changes on POs [Nav 2017], check with Nav 2018 implementation as to what new go live date is and go for a few days away over Easter making the most of the bank holidays.
That's all folks.
Monday, 19 March 2018
Dynamics Nav services: week ending 16/3/18
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.
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, 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.
Subscribe to:
Posts (Atom)
