Only 4 first line support calls / emails last week. Subjects covered included confirmed how to change posting dates allowed [Nav 2013], how to close fiscal year and clear down P&L balances to reserves [[Nav 2013r2], how to amend UK VAT statement for new VAT Prod Posting Group [Nav 2013r2] and how to retrieve licence details [Nav 2009 RTC]. Also confirmed never used bank statement import on Nav 2017 - mainly because copy / paste from Excel must easier and more flexible.
Developments completed last week included a GL data transaction report (export as csv file) [Nav 2009 RTC] and a new BACS export report [Nav 2017].
Bar that a very quiet week.
Starting to look at MTD and implications for Nav clients. Watch this space for more details as we find them. Received PO for Nav 2018 upgrade work on bespoke developments completed for clients off Nav 2009 Classic. Conference call this week to confirm when required for and which edition of Nav 2018.
Tuesday 28 August 2018
Monday 20 August 2018
Dynamics Nav services: w/e 17/8/18
8 first line support calls / emails last week covering the following subjects: how an item holds multiple vat rates [Nav 2009 RTC], change to posting number series [Nav 2013], change to same report layout for 2 different companies on same database (bespoke report) [Nav 2013], permission queries re recent jobs and timesheet implementation [Nav 2013r2], use of bill to number on customer cards [Nav 2013r2], how to get current year in accounts schedule that has a trend type layout [Nav 2013r2] and bug re post invoice and email page action off sales order [Nav 2013t2]. Latter not yet resolved.
Attended client site to discuss support following the client's MS Partner backing out [Nav 2015]. Ended up being a full day resolving bespoke (not ours) interface data feeds between CRM and Nav. Resolved.
Restored recent live back up to a local PC at FPC for new client where development quote approved. Will start the development this week. [Nav 2009 RTC].
Received a client query re MTD coming up next April. Will investigate further. I was hoping for much more clarity from HMRC before now. But never mind.
That's it for this week folks.
Attended client site to discuss support following the client's MS Partner backing out [Nav 2015]. Ended up being a full day resolving bespoke (not ours) interface data feeds between CRM and Nav. Resolved.
Restored recent live back up to a local PC at FPC for new client where development quote approved. Will start the development this week. [Nav 2009 RTC].
Received a client query re MTD coming up next April. Will investigate further. I was hoping for much more clarity from HMRC before now. But never mind.
That's it for this week folks.
Monday 13 August 2018
Dynamics Nav services: w/e 10/8/18
First line support calls / emailed totalled 9 for last week. Subjects covered included changes to dimension values and default dimensions [Nav 2013], confirmation of fields for BACS export report [Nav 2009 Classic], fix for zero quantity to handle on batch of picks [Nav 2009 RTC], confirm reverse transaction only works on journals not documents [Nav 2013], fix allocation line error (bespoke table) [Nav 2009 Classic], confirmed function of on hold field off vendor ledger entries [Nav 2013], fixed unposted and posted number series off purchase ledger to be the same number series [Nav 2013] and provided assistance where CRM invoice integration failed to process data [Nav 2015].
Sent out a quote for bespoke reports conversion from v4 to v2017 for a client. Awaiting approval and will then schedule the work. Needs to be completed pre October 2018.
Chased up some quotes made over the last month to see what status is. Needless to say most people on annual summer vacation.
Plans for this week include an on site client visit to discuss how we can help with first line support. Currently provide ad hoc, on site, Jet and development services. [Nav 2015].
That's it for this week. :)
Sent out a quote for bespoke reports conversion from v4 to v2017 for a client. Awaiting approval and will then schedule the work. Needs to be completed pre October 2018.
Chased up some quotes made over the last month to see what status is. Needless to say most people on annual summer vacation.
Plans for this week include an on site client visit to discuss how we can help with first line support. Currently provide ad hoc, on site, Jet and development services. [Nav 2015].
That's it for this week. :)
Monday 6 August 2018
Dynamics Nav services: w/e 3/8/18
Only 6 support calls / emails last week covering database versions [Nav 2013r2], specifics re different types of user roles for jobs and time sheet implementation [Nav 2013r2], resolved US database tax calc error [Nav 2013r2], mirror company permissions issues [Nav 2013r2], lost page action from recent jobs and time sheets implementation [Nav 2013r2] and resolving VAT Posting Setup error caused by not assigning default VPPG to a GL code [Nav 2013].
So you have probably gathered from common theme for above support calls last week we have started to roll out a jobs and time sheets implementation for a client that uses SQL Sync across 2 databases. Last week we brought all amended / new objects into the live databases from test. This week we will configure permission sets and role centres once the client has confirmed user ids and types. Either this week or next the client will then complete any job / resource data migration using Rapidstart services.[Nav 2013r2].
Completed bespoke customer statement development and delivered to client live database after making some changes to the menu suite and some page actions to run the new customer statement report. [Nav 2015].
Bar that a quiet week. Expecting this week to be the same bar the above comment on jobs and time sheet implementation.
That's all folks.
So you have probably gathered from common theme for above support calls last week we have started to roll out a jobs and time sheets implementation for a client that uses SQL Sync across 2 databases. Last week we brought all amended / new objects into the live databases from test. This week we will configure permission sets and role centres once the client has confirmed user ids and types. Either this week or next the client will then complete any job / resource data migration using Rapidstart services.[Nav 2013r2].
Completed bespoke customer statement development and delivered to client live database after making some changes to the menu suite and some page actions to run the new customer statement report. [Nav 2015].
Bar that a quiet week. Expecting this week to be the same bar the above comment on jobs and time sheet implementation.
That's all folks.
Monday 30 July 2018
Dynamics Nav services: w/e 27/7/18
Relatively quiet week last week on first line support desk last week at 8 calls / emails. Subjects covered included completing an out of working hours total back up from the Dynamics Nav application [Nav 2009 Classic) and then from SSMS, completing a budget load data load [Nav 2013], adding in the standard Nav Posting Description field to unposted sales and purchase document headers [Nav 2013], resolving Jet report data update issues [Nav 2013r2], resolving rapidstart export to excel error (missing codeunit) issue off FR database [Nav 2013] and resolving tracking spec and then reservation entry issues off sales invoice created from multiple shipments [Nav 2009 RTC].
Completed on site Jet training [Nav 2015] at client site where a number of Excel related reports from Nav created and tested and working. At same client also confirmed this week they have development environment access so we also completed the above change re posting description. [Nav 2015].
Only development completed last week was adding vendor name to the posted purchase invoice and credit memo lines pages [Nav 2013].
Also received a call re view on work involved for bring across customer ledger entries history for a new Nav version implementation. Lot of work (create / post sales documents, create / post receipt journals and then complete applications) for little benefit. Another call this week planned to discuss further.
Plans for this week include completing bespoke customer statement for client for open entries only and some other formatting mods. [Nav 2015].
Bar that a quiet week but then again it is holiday season! :)
That's all folks.
Completed on site Jet training [Nav 2015] at client site where a number of Excel related reports from Nav created and tested and working. At same client also confirmed this week they have development environment access so we also completed the above change re posting description. [Nav 2015].
Only development completed last week was adding vendor name to the posted purchase invoice and credit memo lines pages [Nav 2013].
Also received a call re view on work involved for bring across customer ledger entries history for a new Nav version implementation. Lot of work (create / post sales documents, create / post receipt journals and then complete applications) for little benefit. Another call this week planned to discuss further.
Plans for this week include completing bespoke customer statement for client for open entries only and some other formatting mods. [Nav 2015].
Bar that a quiet week but then again it is holiday season! :)
That's all folks.
Monday 9 July 2018
Dynamics Nav services: w/e 6/7/18
Another quiet week on first line support with 3 emails / calls. Subjects covered included adding fields to pages (2) [Nav 2013] and creating a new user [Nav 2009 Classic].
Other work completed last week included a conference call re latest proposed solution for 3rd party web based PO application [Nav 2013] including proposed solution document update, start of another mini project re 2 databases to 1 [Nav 2013] and creating 1st draft Nav xmls for web based PO implementation [Nav 2013].
Completed 1 development last week re bespoke payment report for 2 versions of Nav [Nav 2013r2] [Nav 2017].
Received enquiries (existing clients) for transmitting sales invoices to 3rd party application (not heard of file format so requested more details). Confirmed fixed asset functionality [Nav 2016].
No take up yet on the 15% discount we are offering - more details here.
That's it for this week! Keep cool!
Other work completed last week included a conference call re latest proposed solution for 3rd party web based PO application [Nav 2013] including proposed solution document update, start of another mini project re 2 databases to 1 [Nav 2013] and creating 1st draft Nav xmls for web based PO implementation [Nav 2013].
Completed 1 development last week re bespoke payment report for 2 versions of Nav [Nav 2013r2] [Nav 2017].
Received enquiries (existing clients) for transmitting sales invoices to 3rd party application (not heard of file format so requested more details). Confirmed fixed asset functionality [Nav 2016].
No take up yet on the 15% discount we are offering - more details here.
That's it for this week! Keep cool!
Monday 2 July 2018
Dynamics Nav services: w/e 29/6/18
Quieter on first line support last week - only 5 emails / calls. Subjects covered included how to get vendor name and address details from Nav to excel [Nav 2013], which email to use for emailing remittances [Nav 2013], confirmed rules for posting of purchase invoice not allowed if not BACS details on vendor [Nav 2013], confirmed previous BACS export developments have been completed to example files [Nav 2013r2], removed built in filter report for bespoke report previously developed [Nav 2013] and confirmed how to track item master file changes by user [Nav 2009 RTC],
Also last week completed 1 day's on site training of version 4 dataports, minor bespoke development for bespoke table (new field) [Nav 2013r2] and added bill to name to timesheet lines [Nav 2013r2].
Apart from that, both quotes for new work went in last week together with implementation proposal. Awaiting feedback on both. [Nav 2013, Nav v2.6]. This took most of last week to prepare and then submit. Especially a refresher on v 2.6 - it has been a while since I have looked at it.
Don't forget 15% discount on all Dynamics Nav services rates applies from July 1st to September 30th to celebrate 15 years in business in September 2018. Applies to existing and new customers. More details here.
That's it for this week. Keep cool!
Also last week completed 1 day's on site training of version 4 dataports, minor bespoke development for bespoke table (new field) [Nav 2013r2] and added bill to name to timesheet lines [Nav 2013r2].
Apart from that, both quotes for new work went in last week together with implementation proposal. Awaiting feedback on both. [Nav 2013, Nav v2.6]. This took most of last week to prepare and then submit. Especially a refresher on v 2.6 - it has been a while since I have looked at it.
Don't forget 15% discount on all Dynamics Nav services rates applies from July 1st to September 30th to celebrate 15 years in business in September 2018. Applies to existing and new customers. More details here.
That's it for this week. Keep cool!
Monday 25 June 2018
Dynamics Services: w/e 22/6/18
Busy week last week on first line support - 11 calls / emails. Subjects covered included refresher on jobs and timesheets [Nav 2013r2], Nav install issue re server and client application version mismatch [Nav 2013], permission issues [Nav 2016,Nav 2009 RTC], confirmed shipped not invoiced report subject to hot fix as bugged [Nav 2009 RTC], confirmed best method for getting general ledger data by month and dimensions for data migration [Nav v4, 2009 Classic], confirmed fix for crashing bespoke payment report [Nav 2013r2] and could not resolve bespoke code in Nav 2017 that sends pdf email but logo lost but queried why not using Company Information logo [Nav 2017].
Having one of these issues? We can help. More details on first line support services here.
Further discussions last week on 3rd party PO web based application and how to work with Nav 2013. Agreed high level data flows so we will create proposal and confirm quote this week.
Also pulling together quote this week (and detailed plan) for company hive up for a potential new client [Nav 2.6]. Requires new company and data migration.
Quote submitted last week for bespoke payment report [Nav 2013r2]. Yet to be approved.
Developments outstanding include bespoke customer statement - just awaiting confirmation of logo picture from client. [Nav 2015] Will chase this week so should get development done this week.
Other plans for this week include dataport training session for v2.6 and v4 for 2 client users.
That's all for this week folks. Stay cool or at least try to. We are!
Having one of these issues? We can help. More details on first line support services here.
Further discussions last week on 3rd party PO web based application and how to work with Nav 2013. Agreed high level data flows so we will create proposal and confirm quote this week.
Also pulling together quote this week (and detailed plan) for company hive up for a potential new client [Nav 2.6]. Requires new company and data migration.
Quote submitted last week for bespoke payment report [Nav 2013r2]. Yet to be approved.
Developments outstanding include bespoke customer statement - just awaiting confirmation of logo picture from client. [Nav 2015] Will chase this week so should get development done this week.
Other plans for this week include dataport training session for v2.6 and v4 for 2 client users.
That's all for this week folks. Stay cool or at least try to. We are!
Tuesday 19 June 2018
Dynamics Nav services: 2 weeks ending 15/6/18
Had a few days off last week and was at a client site yesterday providing support so apologies for delay in the blog.
Busy time on first line support with 24 support calls / emails over the last 2 weeks. Subjects covered included date formats on US posted sales invoices [Nav 2013r2], issue with bank rec lines not showing on bank rec (on other unposted bank recs) [Nav 2013], bin code would not delete as warehouse entries still exist [Nav 2009 RTC], confirmed best process for pro forma invoices for suppliers [Nav 2017], confirmed relationship between sub ledger and control accounts [Nav 2013], resolved issue with payment journal creation [Nav 2013], confirmed how to delete cheques [Nav 2013], resolved dimensions error on document posting arising from conflicting defaults off masters [Nav 2017], resolved customer workflow approval block [Nav 2017], fixed development bug for pre check on item tracking pre warehouse shipment creation [Nav 2009 RTC], resolved Jet report query re multiple lines off table query [Nav 2015] and default bank account to currency code (client bespoke field) error resolved [Nav 2013].
No developments completed in the last 2 week.
Attended client site yesterday to provide support for creating simpler dimension group with values and much simpler chart of accounts. [Nav 2015].
Took part in a conference call on getting data from and to 3rd party purchase order web application and as a result coming up with proposed Nav solution [Nav 2013], estimated timescales and a quote for the work this week.
Also received a number of enquiries from current and potentially new customers last week including adding logo to remittance report [Nav 2017], ball park quote for moving Nav 2009 Classic developments to Nav 2018 and ball park quote for more company implementations on Nav 2016. Received a call yesterday from a potential client re Nav support for company merging.
Plans for this week include conference calls [Nav 2013r2], remote training (Nav 2013r2] and catch up on proposed PO implementation [Nav 2013]. Also need to get started on 3rd party PO web application roll out with feeds from and to Nav 2013 - starting with high level proposed data flows between the 2 applications.
Lastly - as a result of trading for 15 years this September we are offering a 15% discount on all of our rates from now until the end of September 2018. More details here!
That's all for this week folks.
Busy time on first line support with 24 support calls / emails over the last 2 weeks. Subjects covered included date formats on US posted sales invoices [Nav 2013r2], issue with bank rec lines not showing on bank rec (on other unposted bank recs) [Nav 2013], bin code would not delete as warehouse entries still exist [Nav 2009 RTC], confirmed best process for pro forma invoices for suppliers [Nav 2017], confirmed relationship between sub ledger and control accounts [Nav 2013], resolved issue with payment journal creation [Nav 2013], confirmed how to delete cheques [Nav 2013], resolved dimensions error on document posting arising from conflicting defaults off masters [Nav 2017], resolved customer workflow approval block [Nav 2017], fixed development bug for pre check on item tracking pre warehouse shipment creation [Nav 2009 RTC], resolved Jet report query re multiple lines off table query [Nav 2015] and default bank account to currency code (client bespoke field) error resolved [Nav 2013].
No developments completed in the last 2 week.
Attended client site yesterday to provide support for creating simpler dimension group with values and much simpler chart of accounts. [Nav 2015].
Took part in a conference call on getting data from and to 3rd party purchase order web application and as a result coming up with proposed Nav solution [Nav 2013], estimated timescales and a quote for the work this week.
Also received a number of enquiries from current and potentially new customers last week including adding logo to remittance report [Nav 2017], ball park quote for moving Nav 2009 Classic developments to Nav 2018 and ball park quote for more company implementations on Nav 2016. Received a call yesterday from a potential client re Nav support for company merging.
Plans for this week include conference calls [Nav 2013r2], remote training (Nav 2013r2] and catch up on proposed PO implementation [Nav 2013]. Also need to get started on 3rd party PO web application roll out with feeds from and to Nav 2013 - starting with high level proposed data flows between the 2 applications.
Lastly - as a result of trading for 15 years this September we are offering a 15% discount on all of our rates from now until the end of September 2018. More details here!
That's all for this week folks.
Monday 4 June 2018
Dynamics Nav services: w/e 1/6/18
10 first line support calls / emails this week covering permissions issues (3) [Nav 2009 RTC], query on restriction to 13 columns of data for column layout on Preview (no limit on print / pdf) [Nav 2013r2], confirmed and showed how to to create a new test company as a copy of live [Nav 2015], confirmed new report needed for posted sales credit memo project data [Nav 2013], moved job tracker changes from test to live [Nav 2009 Classic], confirmed settings for VAT on settlement discounts [Nav 2009 RTC] and created number series for client via TeamViewer for customers and sales invoices [Nav 2015].
Developments completed and delivered for confirm box on creating pick and check item tracking completed at sales order level pre warehouse shipment creation [Nav 209 RTC].
Bar that a quiet week.
That's all folks.
Developments completed and delivered for confirm box on creating pick and check item tracking completed at sales order level pre warehouse shipment creation [Nav 209 RTC].
Bar that a quiet week.
That's all folks.
Tuesday 29 May 2018
Dynamics Nav services: w/e 25/5/18
Busy week last week on support calls - 13 calls and emails in the week. Subjects covered included
odd behaviour for description 2 lines on a sales return order - not resolved yet [Nav 2009 RTC], Jet report issues re data access down to Jet licence install [Nav 2013], set up partial VAT rates for subscription sales [Nav 2013r2], resolved general posting setup errors [Nav 2013r2], sent step by step instructions on setting up new currency code and exchange rates [Nav 2013], confirmed how to allow VAT changes on sales invoices and how to complete a VAT change [Nav 2013r2], confirmed best way to get journal details for a year is to use GL entries and filters (no report available) [Nav 2013], confirmed general journal with a VAT Prod Posting Group will populate VAT entry and therefore appear on VAT statement [Nav 2013r2], client confirmed smtp issue with Office 365 and multiple Nav users now fixed [Nav 2016] and confirmed how to export budget into excel [Nav 2015].
Quote submitted and approved last week for adding confirm box to create pick function [Nav 2009 RTC] and testing tracking lines exist pre warehouse shipment creation [Nav 2009 RTC]. Developments started last week and will be completed this week.
Bar that another quiet week on anything but first line support.
That's all folks.
odd behaviour for description 2 lines on a sales return order - not resolved yet [Nav 2009 RTC], Jet report issues re data access down to Jet licence install [Nav 2013], set up partial VAT rates for subscription sales [Nav 2013r2], resolved general posting setup errors [Nav 2013r2], sent step by step instructions on setting up new currency code and exchange rates [Nav 2013], confirmed how to allow VAT changes on sales invoices and how to complete a VAT change [Nav 2013r2], confirmed best way to get journal details for a year is to use GL entries and filters (no report available) [Nav 2013], confirmed general journal with a VAT Prod Posting Group will populate VAT entry and therefore appear on VAT statement [Nav 2013r2], client confirmed smtp issue with Office 365 and multiple Nav users now fixed [Nav 2016] and confirmed how to export budget into excel [Nav 2015].
Quote submitted and approved last week for adding confirm box to create pick function [Nav 2009 RTC] and testing tracking lines exist pre warehouse shipment creation [Nav 2009 RTC]. Developments started last week and will be completed this week.
Bar that another quiet week on anything but first line support.
That's all folks.
Monday 21 May 2018
Dynamics Nav services: w/e 18/5/18
7 support calls / emails last week (so quiet week again but see GDPR comment below re potential reasons) covering the following subjects: set up new user [Nav 2009 Classic], confirmed best way to filter on bin contents as another 'feature' found in Nav [Nav 2009 RTC], confirmed how to remove credit checks [Nav 2016], investigated excel upload for item reclass journal [Nav 2009 RTC], created in transit code for a new company [Nav 2009 RTC], confirmed reason for warehouse receipt header now showing for user [Nav 2009 RTC] and confirmed you cannot reverse posted assembly order except through item journal adjustments and then re do assembly order [Nav 2013r2].
Quiet week work wise but pretty sure that is down to GDPR. Attended client site last week to run through a number of Dynamics Nav 2015 areas - more of a question and answer session and also confirmation of what you can do in Nav 2015. Previously client on Nav 2009 Classic so quite a different end user experience. Discussed a new and better configuration re chart of accounts and dimensions. Time will tell if the client needs any more of our help.
The previous weeks development completed was amended last week for some more new columns. Based on posted sales invoice data. [Nav 2013].
Along with most other UK businesses, we have spent this week getting GDPR compliant. As a result we have updated our privacy policies and the web site includes this policies and a note of what we have done re GDPR.
Quiet week work wise but pretty sure that is down to GDPR. Attended client site last week to run through a number of Dynamics Nav 2015 areas - more of a question and answer session and also confirmation of what you can do in Nav 2015. Previously client on Nav 2009 Classic so quite a different end user experience. Discussed a new and better configuration re chart of accounts and dimensions. Time will tell if the client needs any more of our help.
The previous weeks development completed was amended last week for some more new columns. Based on posted sales invoice data. [Nav 2013].
Along with most other UK businesses, we have spent this week getting GDPR compliant. As a result we have updated our privacy policies and the web site includes this policies and a note of what we have done re GDPR.
Monday 14 May 2018
Dynamics Nav services: 2 week ending 11/5/18
On holiday last week so no blog.
8 support calls / emails over the last 2 weeks covering VAT calc and post settlement issue (not posted, down to user not posting it as resolved via posting) [Nav 2013r2], currency exchange rate issue (pages crashes as a result of relation exchange rate being zero, fixed via bespoke page) [Nav 2013], temporary permissions amendment [Nav 2013], confirmation that bespkoke auto exchange rate update from one company across all other GBP companies will not work for new USD companies [Nav 2009 RTC], confirmed connection issue not a Nav issue but a network issue [Nav 2013], permissions amendment to allow user to change project codes (global dimension 2) [Nav 2013] and confirmed error 59 operating system error not a Nav issue (query from contacts off our web page).
2 quotes raised last week: one for a current client re bespoke posted sales invoice report [Nav 2013] and the other for a number of reports for a potential new client. First one approved, developed and delivered this morning. Awaiting for feedback / approval for 2nd.
Only other developments completed over the last 2 weeks was amending remittance report off posted payment on vendor ledger entries as per client spec [Nav 2013r2].
Plans for this week include on site attendance to run through list of issues for a client (after their upgrade from Nav 2013r2 to Nav 2016, not done by us as we do not do upgrades). And of course fulfilling all the requirements for the new GDPR regulations that come into effect this month. What a pain but never mind. More red tape is what a small business needs.
Bar that a quiet week.
That's all folks!
8 support calls / emails over the last 2 weeks covering VAT calc and post settlement issue (not posted, down to user not posting it as resolved via posting) [Nav 2013r2], currency exchange rate issue (pages crashes as a result of relation exchange rate being zero, fixed via bespoke page) [Nav 2013], temporary permissions amendment [Nav 2013], confirmation that bespkoke auto exchange rate update from one company across all other GBP companies will not work for new USD companies [Nav 2009 RTC], confirmed connection issue not a Nav issue but a network issue [Nav 2013], permissions amendment to allow user to change project codes (global dimension 2) [Nav 2013] and confirmed error 59 operating system error not a Nav issue (query from contacts off our web page).
2 quotes raised last week: one for a current client re bespoke posted sales invoice report [Nav 2013] and the other for a number of reports for a potential new client. First one approved, developed and delivered this morning. Awaiting for feedback / approval for 2nd.
Only other developments completed over the last 2 weeks was amending remittance report off posted payment on vendor ledger entries as per client spec [Nav 2013r2].
Plans for this week include on site attendance to run through list of issues for a client (after their upgrade from Nav 2013r2 to Nav 2016, not done by us as we do not do upgrades). And of course fulfilling all the requirements for the new GDPR regulations that come into effect this month. What a pain but never mind. More red tape is what a small business needs.
Bar that a quiet week.
That's all folks!
Monday 30 April 2018
Dynamics Nav services: week ending 27/4/18
7 support calls / emails last week covering removal of unposted cash journal posting lines [Nav 2009 Classic], suggested solution to excel export error from report [Nav 2009 RTC], solution (dataport) for general ledger entries data extract as copying / pasting crashes [Nav 2009 Classic], set up missing general posting setup for assembly order posting [Nav 2013r2], bug fix for posted sales invoice report that shows all picks (text to text error as more picks than expected) [Nav 2009 RTC], confirm (and do via TeamViewer) to load amended table object [Nav 2017] and using Copy Doc where sales invoice posted in error [Nav 2009 RTC].
Received client full sql backup and successfully restored to a local database. Investigated client requirements and then put in a few quotes for fixes to client database re remittance advice (posted not the same layout as unposted) and a bespoke remittance report. [Nav 2013r2]. Awaiting approval.
Also confirmed you can easily change a database assigned to a Nav instance [Nav 2016].
Bar that a quiet week last week. Attended client site to successfully deliver, test and hand over development to add Post and Send to a sales order [Nav 2016, yes in Nav 2017 but not 2016!].
No client visits scheduled work for this week. So looks like another quiet week.
That's all folks.
Received client full sql backup and successfully restored to a local database. Investigated client requirements and then put in a few quotes for fixes to client database re remittance advice (posted not the same layout as unposted) and a bespoke remittance report. [Nav 2013r2]. Awaiting approval.
Also confirmed you can easily change a database assigned to a Nav instance [Nav 2016].
Bar that a quiet week last week. Attended client site to successfully deliver, test and hand over development to add Post and Send to a sales order [Nav 2016, yes in Nav 2017 but not 2016!].
No client visits scheduled work for this week. So looks like another quiet week.
That's all folks.
Monday 23 April 2018
Dynamics Nav services: week ending 20/4/18
Only 2 support calls / emails last week: query on bin for reclass journal [Nav 2009 RTC] and adding a new field to a bespoke table re creation date which included some code. [Nav 2009 RTC].
Also received a query on previously tested development re prepayments off POs. The result was a slight change to the development to allow the end user to force roundings off prepayment stats without changing the PO status and therefore triggering document approval. [Nav 2017].
Received 1 support call for customer that is on stop so that has been left unanswered for now [Nav 2013]. Customer still on stop as no payment received and no response to emails requesting payment. FPC Credit Control department about to start chasing payments this week.
Attended client site to run through jobs and time sheets implementation / development. Went well. Some minor changes completed and now awaiting client to confirm permissions required for the jobs and time sheets and then they will roll out testing to end users. [Nav 2013r2].
Major issue for FPC last week was a small electrical sub station fire Wed night just outside our office. No major damage but next morning no Internet (Virgin Cable) across some (not all weirdly) PCs / Laptops. Escalated to Virgin and technician came out to investigate / fix Saturday. So back on line now. Affected work last week so not much else to report on for the blog.
The main plan for this week is an on site attendance all day Wed to load in a development / provide support. [Nav 2016].
That's all folks!
Also received a query on previously tested development re prepayments off POs. The result was a slight change to the development to allow the end user to force roundings off prepayment stats without changing the PO status and therefore triggering document approval. [Nav 2017].
Received 1 support call for customer that is on stop so that has been left unanswered for now [Nav 2013]. Customer still on stop as no payment received and no response to emails requesting payment. FPC Credit Control department about to start chasing payments this week.
Attended client site to run through jobs and time sheets implementation / development. Went well. Some minor changes completed and now awaiting client to confirm permissions required for the jobs and time sheets and then they will roll out testing to end users. [Nav 2013r2].
Major issue for FPC last week was a small electrical sub station fire Wed night just outside our office. No major damage but next morning no Internet (Virgin Cable) across some (not all weirdly) PCs / Laptops. Escalated to Virgin and technician came out to investigate / fix Saturday. So back on line now. Affected work last week so not much else to report on for the blog.
The main plan for this week is an on site attendance all day Wed to load in a development / provide support. [Nav 2016].
That's all folks!
Tuesday 17 April 2018
Dynamics Nav services: w/e 13/4/18
Apologies for the delay in the blog this week - I was training at site yesterday re Nav 2017 to a couple of Nav consultants on the changes since Nav 2013r2. Major ones are always listed on the web but minor more significant from an end users perspective are not.
Support calls last week totalled 12 (up from the previous week) covering areas including set up and use of assembly orders [Nav 2013r2], permissions issues [Nav 2017, Nav 2013], sales invoice report layout issue re logo and company details [Nav 2009 RTC], year end close process run through via TeamViewer [Nav 2013] and some minor changes to developments recently delivered [Nav 2017].
Development completed last week after quote approved included page action to change Pending Prepayment status on PO to Released if all prepaid invoices are paid [Nav 2017].
Completed step by step process based instructions for jobs and time sheets implementation and delivered to client last week. Last set of enhancements and bugs fixed last week for jobs and time sheets development so this week will demo to client. [Nav 2013r2].
Plans for this week include on site training of consultants (mentioned at start of blog) and first run through jobs and time sheets implementation [Nav 2013r2]. Started work on how extensions work on Nav 2018 and made some progress. Need to finish this and bottom out how this works for Dynamics 365 and then we can formally quote for work for a potential new client.
A noteworthy business point arose this week - for the first time ever I have had to put a client on stop. Yesterday. A real shame and not something I thought (given my experience in running finance departments over 30 years) I would ever have to do. Never mind a first time for everything. Affects their first line support and all developments / quotes now on hold.
That's it for this week folks.
Support calls last week totalled 12 (up from the previous week) covering areas including set up and use of assembly orders [Nav 2013r2], permissions issues [Nav 2017, Nav 2013], sales invoice report layout issue re logo and company details [Nav 2009 RTC], year end close process run through via TeamViewer [Nav 2013] and some minor changes to developments recently delivered [Nav 2017].
Development completed last week after quote approved included page action to change Pending Prepayment status on PO to Released if all prepaid invoices are paid [Nav 2017].
Completed step by step process based instructions for jobs and time sheets implementation and delivered to client last week. Last set of enhancements and bugs fixed last week for jobs and time sheets development so this week will demo to client. [Nav 2013r2].
Plans for this week include on site training of consultants (mentioned at start of blog) and first run through jobs and time sheets implementation [Nav 2013r2]. Started work on how extensions work on Nav 2018 and made some progress. Need to finish this and bottom out how this works for Dynamics 365 and then we can formally quote for work for a potential new client.
A noteworthy business point arose this week - for the first time ever I have had to put a client on stop. Yesterday. A real shame and not something I thought (given my experience in running finance departments over 30 years) I would ever have to do. Never mind a first time for everything. Affects their first line support and all developments / quotes now on hold.
That's it for this week folks.
Monday 9 April 2018
Dynamics Nav services: w/e 6/4/18
Another quiet week on first line support (must be Easter!). Subjects covered included how to create a VAT only invoice [Nav 2013r2], how to apply entries between currency codes (or correct error where entries in different currency codes on the same customer account) [Nav 2013] and resolve new permissions issue [Nav 2013].
Last week's work focused on the job time sheet implementation for a client [Nav 2013r2]. Basically configuration testing followed by development testing for all developments completed on UK and US database. Nearly complete so will do end to end process test this week, create step by step process based instructions and then send onto the client requesting UAT.
The only other development completed last week was the removal of the document approval repeat process for prepayment % change on PO [Nav 2017].
Requests for quotes last week included PO change of status off Prepayment Pending when prepaid invoice paid (client confirming rule, then we will quote) [Nav 2017] and use of POP and requisitions specific to client needs (requires us to mark requirements as configuration, developments or cannot do and then quote for work) [Nav 2013].
Not a squeak from client who was going live on Nav 2018 1st April but then they did not get the data together to allow us to do it. Need to contact client re new go live data and when data available to us so we can get on with.
That's it folks.
Last week's work focused on the job time sheet implementation for a client [Nav 2013r2]. Basically configuration testing followed by development testing for all developments completed on UK and US database. Nearly complete so will do end to end process test this week, create step by step process based instructions and then send onto the client requesting UAT.
The only other development completed last week was the removal of the document approval repeat process for prepayment % change on PO [Nav 2017].
Requests for quotes last week included PO change of status off Prepayment Pending when prepaid invoice paid (client confirming rule, then we will quote) [Nav 2017] and use of POP and requisitions specific to client needs (requires us to mark requirements as configuration, developments or cannot do and then quote for work) [Nav 2013].
Not a squeak from client who was going live on Nav 2018 1st April but then they did not get the data together to allow us to do it. Need to contact client re new go live data and when data available to us so we can get on with.
That's it folks.
Tuesday 3 April 2018
Dynamics Nav services: week ending 30/3/18
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!
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!
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.
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!
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)
