Monday 18 December 2017

Week ending 15/12/17

First line support calls resolved last week included setting up a new user, confirming issue with Jet report view for non Jet users [Nav 2013] and confirming initial Jet access error post install down to connection data [Nav 2013].
Some chargeable time this week! At last but just before holiday season. :(
Completed on site training for 2 days covering sale and purchase ledger. [Nav 2013]. Developments completed included bespoke report enhancements and a proposed payment report which lists documents paid as well as overall payment per vendor. [Nav 2013].
Of the 3 quotes outstanding awaiting approval, we have been asked to split one into 2 phases and send on as 2 documents. Also set up some jobs in 2 databases so client staff can set up and test SQL synch by company and specific modules. This will then free up the start of another mini project so our quote approval should follow. [Nav 2013r2]. For another client we are now agreeing a start date of early March next year for 1 project and June for another [Nav 2017]. All looking positive and if all come off we will be busy in 2018.

Plans for this week include starting permissions and role centre assignment [Nav 2013], running through proposed re implementation plan with client [Nav 2018], updating dataport for one more column of data [Nav 2009 Classic] and re-issuing document including quotes as requested by client after splitting project into 2 phases.  So busy week for the week before Xmas.

That's it for this week folks. No more blogs until 2018 so have a great Xmas and New Year!



Monday 11 December 2017

Week ending 8/12/17

Much busier week last week on first line support. Confirmed action required for purchase return order left as unposted after fully shipped and credit note raised [Nav 2009 RTC] and issues with creating and posting general journals (down to defaults on GL codes and lack of user understanding) [Nav 2013].
Did not manage to resolve missing posted sales invoice issue. Down we believe to user deleting invoice. All users super users so that would explain it. Buit surprised that Nav allows a user to delete anything posted but it does. [Nav 2009 RTC].
Had a meeting at our site with client to discuss how to get them live on Nav 2018. So far failed to go live in Nav 2016 but loads of data we can use to help with Nav 2018. Will create and publish a plan this week listing all tasks required to be completed, by whom and by when. This will ensure if followed the client will go live.
Sent on final quotes re Nav 2017 re-implementation. Awaiting client response. Potential go live not until April 2018 so more news on this next year.
Quote submitted for new company config for client to approve. [Nav 2016] Go live Jan 2018 so again more news on this next year.
Confirmed significant quotes to a client will be reviewed in Jan 2018. [Nav 2013r2].
Plans for this week showing an improvement in trade - at last - though with only 1 client at the moment. 2 days on site training booked for last this week and report quote approved late last week which we started Friday. This will be completed today / tomorrow.

That's all folks.

Monday 4 December 2017

Week ending 1/12/17

First line support calls resolved last week included changes to table captions for a bespoke table [Nav 2009 RTC] and taking a client through how to create a new customer [Nav 2013]. So another quiet week on the first line support side.
Had a number of issues with loading a development for client UAT onto their test database but this was eventually resolved by their MS Partner. Hopefully client testing this week. [Nav 2009 Classic].
No developments completed as no quotes signed off.
But prospects still looking good.
Due to send out more quotes this week for a report development [Nav 2013] and company creation / configuration / data migration [Nav 2016]. Also discussing some one off on site training needed urgently this week.
Client been in touch this week to discuss next steps re implementation and how to get the client to a go live on Nav 2018. Original implementation was on Nav 2017 but client failed to go live. Hence the need for our help this time.
Getting to the final stages of spec'ing out a quote for a database move from 2 to 1 databases [Nav 2017]. Will get quote out with supporting document this week. Potential go live data April 2018.
 We need to chase up any progress on other significant quotes that need to be approved [Nav 2013r2].  Some were due to be started last week so presume client deadline for go live has changed. I am guessing as we have now hit December, both quotes will be deferred until Jan / Feb 2018.
Oh and largest fixed price first line support client on an annual renewal will send on PO to confirm renewal this week. [Nav 2009 Classic].
Bar that don't forget Nav 2018 published last week. So if you want to see it, contact us - we have installed on PC here.
That's it folks!

Monday 27 November 2017

Week ending 24/11/17

Still no movement on sizeable quotes to clients re approval [Nav 2013r2] and scheduling the work (1 element required by Friday this week) so no developments last week and none scheduled for this week.
One small quote submitted for approval (minor report change) and waiting to hear. [Nav 2009 RTC].
Ongoing discussion re a client moving to 1 database from 2. Decision made to use 1 specific database and client will be in touch this week to confirm next steps and whether we are involved or not. [Nav 2017].
Another ongoing discussion re a report quote required from us for a bespoke customer report on deliveries. Key question is grouping required for customers which is not defined by customer posting group but by item sold. Weird so queried. [Nav 2016].
Also chased up potential quote re company creation for a client. Awaiting details of the companies and report required. [Nav 2016].

Quiet week on first line support as well - 2 calls from the same client re issues on stock quantity reports (inconsistent, down to different measures on location and lot (fixed for one, open for the other) so resolved) and a report error out due to an item being created with a single digit code (created in error and report looks using COPYSTR for specific characters / groups of characters so needs at least 3 character code). Latter fixed by filtering out erroneous item code. [Nav 2009 RTC].
Prospects are really very good at the moment with plenty of potential work but nothing approved as yet.

So another quiet week.

Monday 20 November 2017

Week ending 17/11/17

New client on fixed price first line support signed up last week. [Nav 2017]
First line support calls resolved included setting up credit note and invoice for posting to correct VAT errors (more accounting support than Nav support) [Nav 2013], confirmed due date from payment terms for a purchase invoice did not reflect vendor payment terms as user had changed these on the invoice [Nav 2013r2], latest client development (significant as it involved warehousing) tested successfully with client and loaded into live as a result [Nav 2009 RTC], purchase invoice approved via Nav would not post as document re-opened after receipt posted [Nav 2013r2], confirmed consolidation business can have any currency code as a base currency {Nav 2017] and confirmed default Qty to Ship on US database not blank despite settings in S&R Set up as a bug. [Nav 2013r2]. Fixed via single line code to call existing function call.

So busier week on first line support!

Got a little bit more exciting at the end of last week as we were asked about 2 bits of potential work. For one we are expecting the formal request via email this week to quote to set up some new companies and new report development [Nav 2016]. The other involves confirming whether a client can use on country specific database rather than 2. We have asked to look at one specific issues and report back which we will do as part of our fixed price first line support - if it is possible we will then quote for. May lead to some chargeable work. [Nav 2017].
Chased up 2 previous large quotes for work last week to see whether timetable required by client still wanted (live in December 2017 for one) in which case need to start the work this week. Delay in approval caused by internal client resource (lack of) issues for non Nav expertise around SQL Server synching. Expecting an update this week. [Nav 2013r2].
That's all for this week folks!

Monday 13 November 2017

Week ending 10/11/17

A very quiet week last week - both for developments and first line support.
No quotes approved as yet as no developments completed last week.
First line support queries resolved included fixing free stock for an item [Nav 2009 RTC], confirmed where external document found and how populated on customer ledger entry dataport (export) [Nav 2009 Classic], confirmed no off the shelf report for specific vendor details required [Nav 2013] and set up new user as requested with specific access to Nav [Nav 2016].
Quote sent for latter but as per above not approved as yet. Would have recommended RapidStart service for the data required but not a one off data request.
Managed to agree SLA for current client for them to move onto a fixed price first line support service.
That's all for this week folks. Looks like another quiet week this week.

Monday 6 November 2017

Week ending 3/11/17

First line support calls resolved included confirmed shipping cost should not be an item but a GL code (in future could be an item charge) [Nav 2013r2], bug fix on pick report bespoke field where client changed field length in table but not report [Nav 2009 RTC] and confirmed issue re payment discount date between 2 databases different due to bespoke code on 1 database - suggested solution using payment terms config table [Nav 2013]. Fixed pick report re retrieval of vendor shipment number. [Nav 2009 RTC].
Also resolved direct contact via email (not a client) for a user who did not know how to remove a filter on Nav 2009 Classic for items.

2 quotes approved last week and as a result...
Developments completed last week included new fields for bespoke journal table (impacted 10 other objects so major change but all done and working) [Nav 2009 RTC] and adding a running total quantity to the item ledger entry page. [Nav 2009 RTC].

Still 2 quotes outstanding but significant changes made to one quote re time sheets as a result of requirement to run time sheets off 1 of 2 databases in operation - UK and US. Proposed solution synchronised jobs / time sheets between the 2 databases using trigger points and xmls in Nav. Client alternative solution was to use SQL synch. No expertise on this no client will implement. Expect to amend quote again assuming SQL synch works. [Nav 2013r2].

Working on another quote for a client regarding a weekly trend sales report based on dispatched sales and forward orders. Queried change to configuration re 2 sale / customer types and awaitng confirmation from client. Then we will send quote on. Also had a discussion with same client re upgrade / re-implementation to Nav 2017 or from 1/12/17 to Nav 2018 and as a result of the conversation confirmed object changes / bespoke objects on their current database and what this would mean for any upgrade / reimplementation. They are not yet live on Nav. [Nav 2016].

That's it for this week folks.

Monday 30 October 2017

Week ending 27/10/17

Developments completed last week add transfer to code to the pick report [Nav 2009 RTC] and add field to bespoke report data extract [Nav 2013].
First line support calls resolved last week included renaming companies for recent test database restore from live via SQL [Nav 2009 Classic), fixed bespoke report bug [Nav 2013], how to create new location for warehouse [Nav 2009 RTC], warehouse batch default fix to allow selection of different warehouse location [Nav 2009 RTC] and confirmed how to change default dimension value for specific general ledger code [Nav 2009 Classic]. Busy support call week!
Support call not resolved (needed up to date back up of live database) was for error bug for excel import [Nav 2009 RTC]. Backup restored to local PC so will resolve this week.

Attended client site to demo proposed time sheet use with jobs (not full functionality), run through a configured company (client configured so just needed to test) and discuss data flows (between) between 2 other applications and Dynamics Nav. As a result of the meeting, 2 quotes sent for approval. [Nav 2013r2]
Also 2 other quotes requested for a client re extra fields for a bespoke table (including changes to current excel data upload) and additional fields to manage user access rights that do not use permission sets (actually requirements of client could not be managed by table permissions). 1 quote sent and awaiting approval. Query on other requirement which will be resolved today and quote sent on. [Nav 2009 RTC].
Sent off quote for fixed price first line support to existing client to start once approved November.

So very much a quotes week.
Bar that a quiet week. That's all for now!

Monday 23 October 2017

2 weeks ending 20/10/17

Off last week so this week's post includes the last 2 weeks though obviously nothing happened last week.
First line support calls resolved over the last 2 weeks included:
Queries on a new company config and discussion of data streams to and from Dynamics Nav. Suggested solution and meeting with client this week to discuss further. [Nav 2013r2].
Confirmed need to create user and assign permission sets to both UK and US database. [Nav 2013r2].
Fixed year end roll error by manually creating journals and posting. [Nav 2017].
Interesting issue re print to excel for a report and only allowing opening as pdf for one user. [Nav 2009 RTC]. Resolved itself so suspect not a Nav issue but a local Pc windows config issue.
Query raised by client as to why 2 databases in use on Nav 2017 - GB and DE. Confirmed down to country specific requirements.
Completed various fixes for project report development. [Nav 2013].


Developments completed included various job related changes for data imports and exports via dataports [Nav 2009 Classic], include validation on date field for bespoke table [Nav 2009 RTC] and add payment terms to pick report (for prepay customers) [Nav 2009 RTC].


Plans for this week include on site meeting to test new company configuration, proposed time sheet solution and discuss data flows to and from Nav. [Nav 2013r2]. Bar that a quiet week but as away last week suspect will have a few first line support calls. :)
That's it for this week folks!


Monday 9 October 2017

Week ending 6/10/17

First line support calls resolved included commenting on Nav performance issues (likely to be SQL Server or just server performance) [Nav 2009 Classic], sent on instructions on creating and restoring a company back up for updating latest test company [Nav 2009 Classic], commented on posting block off payment journal posting [Nav 2009 Classic] and adding access to company for specific user via permission sets. [Nav 2009 Classic].

Only 1 development approved and completed last week - added bar code search field (bespoke) to put away report. [Nav 2009 RTC]. Another development (bespoke project report) delivered and tested by client last week. Amendments requested, made and delivered. Awaiting client further testing. [Nav 2013].
Sent on to client screen shots (mocked up) showing use of jobs, resources and time sheets without integration to GL avoiding complex control issues but using time sheet functionality in Nav [Nav 2013r2].

Attended a potential new client to discuss using us to assist in documenting requirements for Nav 2009 to Nav 2017 re-implementation. As a result sent on quotes for documenting requirements and providing on site training. Awaiting a response.
Finally received approval for a development quoted for 2 months ago last week. So will review requirement for developments and schedule work. [Nav 2009 Classic].

Bar that a quiet week last week.
Onwards and upwards!

Monday 2 October 2017

Week ending 29/9/17

First line support calls resolved last week included resolving posting sales document issue (down to mismatched amounts) [Nav 2013r2], remaining amount on positive adjustment on item ledger entry [Nav 2009 RTC], changing user profile issue [Nav 2013r2], confirmed how to populate global dimension 1 on purchase order header and impact on lines [Nav 2013r2] and confirmed reason for discount GL code for invoice posting down to 1p difference between unit cost and line amount. [Nav 2013r2].Also fixed issue re sales return order and population of external document number after changing vendor shipment number on warehouse receipt. [Nav 2009 RTC]. Finally confirmed how to post only some lines of payment journal. [Nav 2013].

Received request for proposed payment report off payment journals. Drafted up proposed layout in excel and send for approval. Will then quote for. [Nav 2013].

Investigated and reported back on use of jobs and resources in Nav as a replacement for existing bespoke application. Proposed solution. Requested by client to draw up some screen shots to illustrate proposed solution. [Nav 2013r2].

Development completed last week was a bespoke project spend report [Nav 2013].

Plans for this week include potential new client meeting re mapping requirements for a Nav 2009 to Nav 2017 upgrade, pull together some screen shots re proposed part use of jobs to allow full use of time sheet functionality [Nav 2013r2], delivery of bespoke project report [Nav 2013] and create step by step process based instructions on how to create a new test company as a copy of a live on the same database in Nav 2009.

So busy week this week.

That's all folks.

Monday 25 September 2017

Week ending 22/9/17

It has been a while so apologies for that.
Developments approved and completed last week included adding pallet summary to packing report [Nav 2009 Classic] and fix for carrying the external document number to the posted credit memo from a sales return order. [Nav 2009 RTC].
Also attended client site to discuss use of timesheets and therefore jobs. [Nav 2013r2]. The client has sent some resource and project (job) related sample data so we will configure a test company for jobs and timesheets.
Support calls last week included:
Confirming best way to amend sales order to reflect complex US sales tax based on service type. So user raising sales order does not understand US sales tax regulations by state so a finance  user has to amend the SO afterwards. [Nav 2013r2].
Confirmed best way of correcting shipped resource (cannot use Undo Shipment) is by creating negative resource line on same sales order. [Nav 2013r2].
Some bug fixing re reports off packing list development. [Nav 2009 RTC].
Sent off step by step process based instructions on how to set up and use Nav consolidation. [Nav 2013r2].




Monday 4 September 2017

Week ending 1/9/17

Better chargeable week last week with a Nav 2017 implementation kick off meeting, developments completed for new fields to pick lists [Nav 2009 RTC] and misc support for SEPA extracts [Nav 2016]. Also starting packing list development that was approved lasy week. [Nav 2009 RTC]. Will be completed this week.
First line support calls included development requests [Nav 2009 RTC], confirmed process for shipment error on sales order [Nav 2013r2], confirmed correction process re document number error on payment journal [Nav 2013r2], confirmed process for writing off a fixed asset in Nav [Nav 2013r2], confirmed work around for bank card creation error re To-Dos.[Nav 2013r2], fixed 2 separate Jet Reports from 2 different members of staff from the same client that were not showing Salesperson codes [Nav 2013r2].
Client requested details of the benefits from upgrading from Nav 2013 to Nav 2017 and a ball park estimate of our costs for completing a re-implementation. Re-implementation recommended by us as current config and use of Nav 2013 bad (not our issue, we took on the first line support a few years after the client went live). Send details on both on. This was all triggered by latest BREC (maintenance) invoice to the client from their MS Partner.
Client requested I demo Nav 2017 at their site and run through the changes from Nav 2013r2. Completing this this week.
Business definitely picking up with a fully chargeable week this week. 

Monday 28 August 2017

Week ending 25/8/17

Created a support call log on our Nav 2017 so now we can track all our fixed price first line support calls. 7 calls last week covering licence session blockage [Nav 2013r2], caption changes for a bespoke table [Nav 2009 RTC], confirmed how foreign (non base) currency works on supplier ledger [Nav 2013r2] and confirmed how US sales tax works and to ignore VAT Prod Posting Group settings on US database [Nav 2013r2]. The remaining calls ended up being developments on Nav 2009 RTC.

Developments completed last week included adding outstanding quantity to PO list, taking some bespoke fields from unregistered picks to registered picks, add registered VAT number to a bespoke report using Company Info and add bespoke fields to unregistered put aways table.

Some progress re implementation project and take on of first line support but still early days. So will report on any progress next week.

Had a meeting with a client to discuss further enhancements to PO and PI dataport imports / exports to allow for more data to be passed between a legacy system and Nav 2009 Classic. Quote submitted. Awaiting approval.

Also sent off details re training at client site we provide to a potential client including a schedule of modules we cover.

Lastly submitted a quote for fixed price first line support to a potential new client and awaiting feedback.

In short there is more 'noise' out in the market so may be the quiet period is over?

That's it for this week folks!

Monday 21 August 2017

Week ending 18/8/17

Quiet week last week for first line support calls: just the one which was for any work around for a document approval where approvers on holidays. [Nav 2013r2].
Fixed permissions issue re posting to customer ledger entry following exchange movement. [Nav 2017]. Confirmed issue for customer statement report layout and potential fixes. [Nav 2013r2 DE].
Completed Jet Training at our site last week for a client member of staff. All went well and received positive feedback after the training day. Wrote 8 new Jet Reports off the Nav 2015 demo database and emailed as they would all work off any Nav database. Also sent on post training step by step instructions on creating / posting item journals, running customer item sales report, managing reservations, creating a Jet report via Table Builder and how to view stock by location. [Nav 2015].
Developments completed last week included a bug fix [Nav 2016] re credit memos and ship to codes, ship to address default from customer sell to address and copy document issues around the area. All fixed and working.
Previous development re emailing statements now confirmed as working on UK and US databases. [Nav 2013r2]. Phew!
On the work prospects front, looking more positive. Discussing taking over first line support for a partner client and running a new Nav implementation project on their behalf. Early stages of discussion but could be a significant change for our business.
Also discussing more development with a client this week re importing PO data back into a legacy system after invoice matching [Nav 2009 Classic].
Lastly contacted by recruitment agent re implementation project for Dynamics Nav starting soon. Discussed day rate and confirmed 3 references. Heard nothing since.
That's it for this week folks!

Monday 14 August 2017

Week ending 11/8/17

First line support calls resolved included:
Finding issue with VAT Statement showing no data for a month (down to change of VAT product posting groups which were reflected in the VAT statement but the month in question had the old groups). [Nav 2013]
Confirmed how to activate the change log and how it takes to actually record changes. [Nav 2013].
Suggested reasons for changes to the Navigation Pane for the main departments and therefore a potential solution.[Nav 2013]
Confirmed link between header and lines for Jet reports for posted warehouse shipments. Confirmed location of item sales by customer report and how to add salesperson code filter. Confirmed how to select flowfields in Jet Table Builder. [Nav 2015].
Changed allocation of role centres for 2 database for client. Confirmed language pack (DE, GB) not yet installed properly by MS partner. [Nav 2017].
Still dealing with ongoing issues emailing statements [Nav 2013r2] for 1 user. Changed development to save the pdf to the TEMP directory, then a mapped P drive and then finally a shared drive off the server C drive. If all failed, an error message would be displayed. Worked initially and then did not. So client now re-installing Nav app for user. We have also suggested finding and deleting user zup file. Same change made to US database and issue resolved.
Completed on site training at a new client covering business process to standard Nav mapping. Another training session at our site tomorrow to cover off item journals etc and Jet Express Reporting.
So a busy week but not for chargeable work.


Monday 7 August 2017

Week ending 4/8/17

Well it is holiday season!
First line support queries resolved last week included year end roll for a client (do not forget when creating a new GL code to select Income / Balance correctly otherwise the clear down to P&L values to reserves will not be the same as your year end / statutory accounts) [Nav 2013r2] and changed field caption on table [Nav 2009 RTC].
Development completed last week was amendments for a Nav 2009 Classic item master dataport including a new form to show results of dataport load completed and delivered. Tested successfully by client. Basically the dataport not includes code to create an item master for specific rules and created extended text lines. [Nav 2009 Classic].
Developments completed and successfully client tested in previous weeks re emailing statement [Nav 2013r2] has had issues last week re attaching pdf (weird) or erroring out (very strange). So removed DOWNLOAD code and attached pdf directly from user TEMP file on server. Resolved all issues except for 1 user - obviously this is the 1 user who will use this functionality all the time. Suspect issue (not saving pdf to TEMP directory) is a ZUP file issue but working on a workaround just for that user this week. Not come across this before so this development has taken significantly more time that billed / invoiced. Never mind. The downside to fixed quote billings.
Gained a new client last week for on site and off site training on Dynamics Nav 2015. 1 day this week and 1 day next.
That's if for this week folks!


Monday 31 July 2017

Week ending 28/7/17

Definitely now into holiday season.
First line support issues resolved last week included:
Amending bespoke profile for warehousing staff to minimise page action and navigation pane options. Resolved flowfield issue arising from flowfield off a flowfield. Double link removed so Nav behaves normally now. [Nav 209 RTC].
Amended statement email body for additional line required on UK and US database. [Nav 2013r2].

No developments completed last week.
Another quote submitted to a potential new client last week for 1 day's Dynamics Nav 2015 off site (at our site) training. Awaiting approval / response.
Still awaiting approval of Nav 2017 implementation quote.
Quote submitted and approved to allow a client to load in new items via a dataport with specific rules re creation depending on batch numbers and also adding in extended text lines from same csv file. [Nav 2009 Classic]. This development will be completed this week.
That's it folks.

Monday 24 July 2017

Week ending 21/7/17

Well looked like a great week but as we are now into holiday season some quotes that have been approved are delayed.
First line support issues resolved included creating a new combination of General Posting and VAT Posting Set up for first time billing [Nav 2017] and confirmed fix for incorrect location code for a report (actually derived from warehouse journal batch list) [Nav 2009 RTC].
Development completed included emailing statement for selected customers - UK and US database [Nav 2013r2], adding bespoke reference field on posted sales invoice table to general ledger entries [Nav 2013r2], new field to allow only set warehouse employees to delete printed picks [Nav 2009 RTC] and adding requested delivery date to pick list [Nav 2009 RTC].
Schedule training we were providing today postponed awaiting approval of quote. [Nav 2016].
Sent quote for user permission and role centre allocation for approval [Nav 2009 RTC].
That is it!

Monday 17 July 2017

Week ending 14/7/17

Getting busier!
First line support calls resolved for company logos (adding) and user personalisation issues. Helped load budget file into Nav [Nav 2013] via Teamviewer and after creating new budget name.
Development started last week re emailing statements has thrown up an interesting error message that a user gets on 1 company but not another on the same database. We will investigate and resolve this week. Very odd. [Nav 2013r2].
Confirmed quote for CHAPS Nav export report even though 2 queries still outstanding. Now on back burner as taken a month to get answers to queries raised. Quite complex output file compared to BACS. [Nav 2013r2]
2 quotes approved last week [Nav 2009 RTC] and 1 just approved today [Nav 2013] - all developments. This weeks is a report development [Nav 2013]. Last week's approvals were both developments for minor changes to pages and report layouts. Last week's approved quotes developed and delivered. This week's approval will be developed this week.
Been on site to a potential client today to discuss proposed implementation plan and 'fit' of Dynamics Nav 2017 to their requirements. It is a good fit. So potential client going to discuss and then confirm whether they want to proceed.
Booked last week for super user training a week today. This has yet to be approved but it is pencilled into my diary. Should be approved this week - fingers crossed.
That is all folks.

Monday 10 July 2017

Week ending 7/7/17

Quiet first line support week but a busier week for developments / work completed and significant potential for more work. At last!

Support queries raised and resolved last week included creating a new user on Nav [Nav 2009 Classic], confirming use of default column filter and why this affects search as you type [Nav 2009 RTC] and BACS requires vendor sort code and account number on payment journals to work [Nav 2016].

We started the approved development for emailing statements (obviously Nav 2013r2 rather than Nav 2016 / 2017) last week (all working as required but a few queries so these have been raised with the client) and will complete this when we have had answers to our queries. Once user acceptance testing completed on the UK database we repeat the development on the US database. [Nav 2013r2].
Completed a 1 day on site training for Jet Express last week - specifically how to use of the GL function and Table Builder. Client feedback following training good. Sent on to the client details of our training by module document that describes what Nav training we provide by module for future reference in case any more training required. Of course we also will take Q&A sessions, train to client specific agenda and provide remote training.

Nearly (bit not quite) got to the point of quoting for a CHAPS Nav export but just need last 2 queries resolved. Hopeful we may either get answers this week or given the time that has elapsed the client will withdraw need for export. We usually get requests for BACS extracts which are, again usually, simple though different by UK bank. But we get quotes out very quickly. First time we have ever been asked for a CHAPS export and the file format required seems complex and a little like an EDI file. [Nav 2013r2].

Submitted some quotes last week. These included step by step process based instructions for Jet including screen shots from a demo database and a new accounts payable report looking at overdue ledger items by specific groups for dimensions and type of supply. [Nav 2013]. Neither yet approved.

Completed an implementation plan including day's effort and licence costs (via our business partner) and sent onto a potential client last week. So will see how that goes. Next stage as long as ball park costs are acceptable is to meet up and make sure Dynamics Nav fits.
That's all for this week folks. Keep cool!

Monday 3 July 2017

Week ending 30/6/17

A better week last week for developments and another really busy week on first line support.

Development completed and delivered included amending bespoke report to include 2 columns as replacements [Nav 2009 Classic].

Also created and configured (set permission sets, assigned companies) for new users for a client. [Nav 2016].

First line support issues resolved included activating change log for a bespoke table [Nav 2009 RTC], confirming how to change exchange rates [Nav 2013r2], confirming issue on US database where customer assigned USD on a US database and an end user created in error an exchange rate between the base currency (USD) and the customer currency (USD) that was not 1 to 1 [Nav 2013r2], confirmed configuration required for using items in Nav [Nav 2013r2] and confirmed best approach for creating accounting periods [Nav 2013r2].

There are 2 quotes that have been approved (prior week approval) which we are waiting to start work on. 1 is awaiting completion of a development by a 3rd party for the same client [Nav 2013r2] (emailing customer statement) and the other is dependent on confirming a quote for CHAPS export for a client. The latter taking a while (weeks) to confirm requirements for CHAPS file in Nav speak rather than bank terminology. [Nav 2013r2]. Emailing customer statement development (yes an older version of Nav so not in the application) should start this week.
That's it for this week folks.

Monday 26 June 2017

Week ending 23/6/17

Another quiet development week last week though one development passed customer approval.
One quote was amended and requested and then approved re emailing customer statements. [Nav 2013r2]. Work will be done this week.
Prospects last week which we will firm up this week includes more potential changes to sales invoice layout [Nav 2013r2]..

First line fixed price support continues to be very busy with the following issues raised and resolved:
Confirmed process to Import/Export Budgets [Nav 2013r2].
Resolved page ribbon customisation issue for an end user. [Nav 2013].
Created new text field on warehouse activity header table (and relevant pages) with no rules or links as required. Set property for warehouse activity pages to be for a single location. [Nav 2090 RTC].
Confirmed reason for error on document approval down to lack of email template. Confirmed how to create and then import. [Nav 2013r2].
Confirmed process to create a new company. [Nav 2013r2].
Confirmed how to set default role centre for user. [Nav 2013r2].

That's all for this week.







Monday 19 June 2017

Week ending 16/6/17

A better week last week work wise re chargeable work and more quotes sent out for approval. Another enquiry about a business relationship with an MS Partner short of resource. So business looking up. Oh yes!

Development completed last week was a posted sales invoice layout and then alternative logos via linked up between salesperson code and employee id (from HR module). [Nav 2013r2]
Still raising queries from responses for CHAPS export from Nav. Hopefully final answers this week and then we can quote for. [Nav 2013r2].

First line support queries resolved:
Confirmed best way to hide average purchase price from item list for all users bar one. [Nav 2009 RTC].
Confirmed work involved in making SUPER user not the default setting for all users. Suggested grouping users into categories and then we will quote for this work. [Nav 2009 RTC].
Confirmed approach to create new test company on live database for Nav 2013. Different from Nav 2013r2 as Companies menu option in IT Admin does not exist.
Confirmed off the shelf DD functionality in Nav [Nav 2013r2] and also best approach for getting DD required script on posted sales and service invoices re change of DD and / or date.
Quotes sent to a client re required changes to customer statement report to make it more UK like and to add email send functionality to the amended customer statement. [Nav 2013r2].
Confirmed Payment terms held on service contracts and customer cards. [Nav 2013r2].
Fixed VAT Posting Setup data issue that was stopping document posting. [Nav 2013].

FPC books now on Nav 2017 and spent some time last week adding more key fields / data to the My Customer page so I can now see for the customers I want to see (the active ones)  balance outstanding, quotes, invoices not yet posted and any outstanding sales order. All useful for a quick view of the business. Also means all quotes are now on Nav 2017 and we use the full email functionality in Nav 2017. Especially like email templates associated with reports but not so fond of how difficult it is to find whether reports use Word by default or layouts. By the way we provide training on Word report and email templates and how to make changes.

That's all folks. Stay cool!


Monday 12 June 2017

Week ending 9/6/17

Another non chargeable week but again plenty of fixed price first line support activity and a few quotes went out as well. So more 'noise' which is hopeful.
We did help install Nav 2017 GB demo for a new client. Not something we usually do but we were happy to help. All done and working.
First line support queries resolved included fix to pallet report re location change [Nav 2009 RTC], confirmed Visio for Nav table structure and links [Nav 2013], confirmed 'out of the box' functionality for creating POs via planning worksheet [Nav 2016], confirmed general posting setup changes required to resolve error message on journal posting [Nav 2013], confirmed best way to resolve shipped not invoiced sales order to get rid of [Nav 2013r2], confirmed sales order process in Nav same in US and UK [Nav 2013r2] and confirmed brief overview of how to use Jet Express [Nav 2013].

Quotes submitted for amendment to bespoke tables for enhanced functionality [Nav 2009 RTC], expansion of warehouse reclass journal excel load report for location field [Nav 2009 RTC] and changes to sales report document [Nav 2013r2]. All awaiting approval. Fingers crossed.

Still reviewing requirements for CHAPS export for client. Mapped fields from Nav to CHAPS file and awaiting confirmation ok. Then we will submit a quote. [Nav 2013r2].

Emailed all current clients with option to enhance fixed price first line support with new service which now includes half day on site as part of the service (details at https://www.dynamicsnavukhelp.co.uk/services/support/enhanced-first-line-support/) if the client is already paying for fixed price first line support or if not confirming the fixed price support service and options available (details at https://www.dynamicsnavukhelp.co.uk/services/support/first-line-support/). Some immediate responses ('no right now but will look at in the future') but will have to wait and see what reactions we get in the next week or so.

Also as a result of the email made some significant changes to web pages and significantly updated Bing Ads (less adverts, better links, specific time of day,no change to daily budget) and minor changes to Google Ads. So again we will have to wait and see.
That's it for this week folks.

Monday 5 June 2017

Week ending 2/6/17

Another week for no chargeable time re developments, configurations, data migration or remote training at all last week. Looked like we would start a BACS export development for a client but the requirement was expanded to include a CHAPS export which looked very complex. Waiting for more details. [Nav 2013r2]. No other work in the pipeline at the moment.

Had a meeting last week to discuss a collaboration opportunity with another similar size business.
Will see how this progresses but as a result have added on site services back to the web pages so on site attendance for support / training now available once more and added a new enhanced fixed price first line support service which costs marginally more than fixed price support but in addition includes free on site attendance for a morning once a quarter. More details here.

First line support provided last week included: confirmed comments added to unposted picks retained when picks posted [Nav 2009 RTC],  resolved permissions issue for an end user [Nav 2013r2], did not manage to resolve random application crashes for a client but suggested may be windows / hardware related and not Dynamics Nav app [Nav 2013], resolved windows login invalid password issue [Nav 2009 Classic], resolved A4 document fit change down to new local printer and its printer settings [Nav 2013] and resolved Jet Express connection error [Nav 2013r2].

Bar that very quiet on the Dynamics Nav front.

That's all for this week folks.

Tuesday 30 May 2017

Week ending 26/5/17

No chargeable time re developments, configurations, data migration or remote training at all last week. Another first but not in a good way.
Very quiet also on first line support calls or emails. Confirmed posted sales invoice may be viewed from Value Entries not Item Ledger Entry if sales order shipped. [2009 RTC]. Completed some minor changes to athe put way report. [Nav 2009 RTC]. Confirmed location and settings required to run a UK style Aged at the detail level (invoice details) in the clients US database. I loaded and converted UK Aged Debt style report into their US database last year. [Nav 2013r2].
Investigated iXBRL options out of Nav 2009 Classic. These are xmls but found no standard xml schema available for Companies House submissions so responded to client enquiry by confirming we can quote for but better off using a 3rd party tool like Ftax iXBRL.

So a quiet week but....
We did finally receive confirmation of requirements of new BACS export report (PO approved 2 months ago) which we will start this week [Nav 2013r2]. Slight change of requirement so currently confirming what extra is required so we will requote for approval.
Also pulled together a quote for a UK style customer statement. The out of the box version is awful in that it insists on a start and end date and will list the transactions (all) historically. So useless. The UK requirement is more of an aged debt style report (open items only at time of running the report) but in the customer statement layout. Re creating these style of document reports from scratch a nightmare and expensive from a client perspective. So we have come up with a nice clean fix to the existing customer statement report. [Nav 2013r2].
Finally another quote submitted for amendments to a PO import (via dataport) for a client. Amendments are the inclusion of VAT codes and values in the csv file and getting Nav to deal with it. [Nav 2009 Classic].
That's all for this week folks!

Monday 22 May 2017

Week ending 19/5/17

Quiet week developments wise, busy week re first line support.
Developments completed last week included a new bank rec report that is generated (printed) at the same time as the bank rec is posted. [Nav 2013r2] and minor fixes to the VAT Day Book report. [Nav 2013r2].

Support calls resolved included:
Office 365 smtp testing (follow on from previous testing where we provided our Office 365 account details to our client to confirm what we had working on a local will work on their network and the issue is their Network permission settings),
Confirmed PO dataport import could cope with VAT details if required but code / field changes needed so we could quote for [Nav 2009 Classic].
Confirmed DD functionality in Nav [Nav 2013r2] and text change to service invoice to confirm change of DD amount possible.
Confirmed that for a sales return order the external document number on the order is replaced by the vendor shipment number when the warehouse receipt is posted [Nav 2009 RTC].
Confirmed reason for error message re VAT Prod Posting Group on creating an invoice and how to resolve. [Nav 2013].
Completed a remote training session for a financial controller focusing on year end closes, navigation / drill down and reporting from Nav using accounts schedules. [Nav 2013].

Couple of above responses by us included an option to fix via development and offering to quote for.

Prospects a little better - one client has paid a long overdue bill so no doubt they need more work doing. But this time we will want part payment up front. We are not finance provider!
Quite a few calls from existing clients Friday afternoon which may (or may not) lead to more work. And of course our offers to quote for some changes above may result in some quotes.
So we will have to wait and see.

Monday 15 May 2017

Week ending 12/5/17

A little busier last week. We have been busier but we have also been a lot quieter.

On the first line support side for last week, we:
Confirmed logic rule re user posting date range between G/L set up and User Setup - so which takes priority. [Nav 2016].
Fixed and balanced off accounts schedule following recent upgrade which included a change of dimension code and structure. [Nav 2017].
Further investigated Office 365 smtp, tested, confirmed issues with specific emails (spam filtering) and solution. [Nav 2016].Works really well and love the page actions to configure smtp server for Office 365 and test. Only issue was sent emails were not being received which was down to email service provider filtering.
Interesting issue with a report. Changes made in layout not reflected in RTC. Found report would not compile. Fixed error, compiled and now all working. Don't you just love Nav 2009 RTC?
Confirmed process for creating a fiscal year and made some recommendations re current years on a client's live database. All to pot! [Nav 2013].
Made changes to user's assigned permissions after confirmed error message. Later in the week assigned appropriate role to user after confirmation by client. [Nav 2013r2].
Confirmed name and address list in row and column format not available from Nav. Label report is but this is no good for Word mail merge. [Nav 2013].

Developments completed last week included:
Adding new fields to unposted pick header table. [Nav 2009 RTC].
Adding the same new fields to the posted pick header table. [Nav 2009 RTC]
Added drill down option off page for flowfield field. [Nav 2009 RTC]
That's all for this week.

Monday 8 May 2017

Week ending 5/5/17

Work completed last week included:
Minor amendments to proposed role centres. Now just waiting for the installation of language packs to finalise, assign to users and create appropriate permission groups. [Nav 2017]. 
All document changes for new logo completed and delivered. [Nav 2013r2].
Fixed field width issue on pick list report. [Nav 2009 RTC].

Developments signed off last week which will be done this week included a number of new fields for the pick list table [Nav 2009 RTC] some with rules others without.

In the 'that's interesting' category for last week was the discovery of the Print Company details feature on a US Nav database. Changed the default setting to true so always shows. Believe or not this caused us some initial issues until we spotted this field that does not exist on the UK database. [Nav 2013r2].
Bar that another quiet week.
That's all for now folks!

Tuesday 2 May 2017

Week ending 28/4/17

Well a quiet week last week for me as I was on holiday.
But the business carried on as usual managed by the FPC team.
Quoted for report logo changes for 10 reports after logo for business significantly changed. This was approved and the work started last week and completed this morning. [Nav 2013r2]. This was the only development last week.
We also received a further enquiry from a potential client I visited last year in Wembley. So waiting to see if we can help this time. Client had a MS Partner issue last time we met.
Interesting (for that read annoying) issue on service management invoice created by Nav after amendment to service items which created 1 credit line only on an invoice header. So it will not post. Trying to fix the back door route (as not posted) stopped by existence of service ledger entries created by Nav. As these are posted, normal permissions not sufficient. So the only solution from us would be a new codeunit to allow deletion of service ledger entries. But the codeunit would need to be added to the Nav licence which can only be done by the MS Partner. So suggested client contact MS Partner for a better solution. [Nav 2013r2].
Nothing came of remote training enquiry last week. Shame but them's the breaks.
Finally the £100 off promotion for April 2017 was reasonably successful although the jury is out on whether we got the work as a result of the discount or the work needed doing anyway. Net discount for the month £700.
That's all folks.

Monday 24 April 2017

Week ending 21/4/17

A very quiet week for us.
Only 2 developments completed last week: one was a document report conversion from Nav 2009 RTC to Nav 2015 and the other adding 4 new fields to the warehouse activity table (all manual) [Nav 2009 RTC].
First line support issues resolved last week included fixing a number of reports following change of default location and fixing some bugs [Nav 2009 RTC], confirmed how to avoid journal number renumbering on payment journals (use specific number series and assign to batches) [Nav 2013], confirmed how to create page to allow bin deletion (bin empty) [Nav 2009 RTC], confirmed process for resolving application errors and writing off 1ps as well as potential use of payment tolerance for 1p differences. Also confirmed process for importing budgets and how to apply budget filters to show current budget only. [Nav 2013r2].
Still have an interesting issue re Nav 2009 Classic with a windows login pass through with error message invalid user password. Not yet fixed but believe it is an issue in SQL server not Nav.
We had a a remote training enquiry which may become an order for the end of this week for 2 hours remote training on creating reports in Nav. Version of Nav to be confirmed.
That's it for this week.


Tuesday 18 April 2017

Week ending 14/4/17

Hope you all had a great Easter! Quieter week but it was Easter.
Quoted for report conversions work approved and work started as per below. [Nav 2015].
Work completed last week included:
Developments:
First 2 reports conversion (from Nav 2009 RTC) completed and delivered. More to follow next week. [Nav 2015].
Ad hoc support:
confirmed fix for blocked dimension error message. Confirmed how to change fixed asset dimensions quickly. Completed first draft 2 new role centres and sent to client for comment / amendment. [Nav 2016].
Completed step by step process based instructions on how to create a list of customers / items where there were sales in last 12 months. [Nav 2009 application, v4 database].
Confirmed best way to find last sales date from Nav for items / customers. [Nav 2009 application, v4 database].
First line support included minor changes to pick lists to show only non zero lines picks. [Nav 2009 RTC]. Confirmed how to correct general journal that included a fixed asset. [Nav 2013r2] .

That's all folks.

Monday 10 April 2017

Week ending 7/4/17

A busy week last week - on chargeable work for a change and again on first line support.
First line support issues this week included mysterious error re new user (invalid password for windows login), gen bus posting group issue (EC purchases taken to UK as pay to vendor UK but buy from vendor EC), confirmed changes required to Nav configuration following location rename and confirmed process to post a zero value invoice from a sales order.
Developments completed last week included more changes to a previously developed report (more columns on the excel export) [Nav 2009 application, v4 database], add a new column to a page [Nav 2016] and SEPA file review and recommendation [Nav 2016] - this will continue re changes required this week.
Data migration included conversion and load of customer records to recently created new company [Nav 2016].
Other work from last week included Office 365 SMTP email test (looked ok from a Nav perspective but never received the email) [Nav 2016] and data extract (sales prices and discounts, purchase prices) for client moving to another application from Nav.
This week scheduled work includes 2 new bespoke role centres (and relevant permissions) [Nav 2016], SEPA file development work and a tweak to previously developed BACS export report [Nav 2009 RTC] as well as final test re cheque remittance report and potential work as noted next.
And this week we have a potential big job on converting Nav 2009 reports to Nav 2015. We need to restore a current copy of the live database and get more details from the client as to which reports needs converting and when the converted reports are required by. And also check we can do the job required in time.
Don't forget we are offering £100 off our day rates (T's and Cs apply) for April 2017 only.
Finally Easter this week end. Have a good one!

Monday 3 April 2017

Week ending 31/3/17

Much better week for chargeable work last week and still busy on first line support.

Work completed last week:
Configuration of a new company completed and delivered. [Nav 2016].
Ongoing support to client following data loss. [Nav 2016].
Completed BACS export report and delivered. [Nav 2009 RTC].
Completed page changes required for G/L entries and general journals. Client requested no change to profiles which means no users can make simple changes re column order and structures for pages. Hence we complete these changes. [Nav 2016].
Add more free stock by specific location to item list. [Nav 2009 RTC].
Moved permissions related function to another codeunit to allow changes to another codeunit by client using their own licence. [Nav 2016]

First line support tasks completed last week:
Confirmed issue and solution for excel paste rows into excel down to column order. Field validation being called which wipes the dimension code. Simple solution to change column order on page so that dimension code last. [Nav 2016]
Resolved some issues with cheque remittance report but still have remaining issue re cheque number count and physical cheque number where number of applications run to a large number of pages. [Nav 2009 Classic]. Resolving today.
Resolved bin contents issues compared to item list. As bin contents run from warehouse entry table (sum of entries), solution usually create bin code that warehouse entry table has. [Nav 2009 RTC].
Renamed location code as requested. [Nav 2009 RTC].
Did not manage to resolve user id population in Nav that does not exist. Not clear where coming from but suspect web service. [Nav 2009 RTC].
Fixed a number of reports following rename of location code. In the reports location code held as a text constant. [Nav 2009 RTC].
Confirmed process to create a manual vendor payment without applying. [Nav 2016].
Confirmed how to show old VAT statement where statement closed via Calc and Post VT Settlement. [Nav 2013r2].
Answered queries on potential EDI development to receive customer POs to create as SOs and send back details of shipments. [Nav 2009 RTC].
Confirmed options for loading excel data into Nav [Nav 2009 RTC]. Basically xmlports - or upgrade to latest version or develop.
Confirmed need to create warehouse employee for each location so that when you do not get a blank put away / pick when created from a warehouse receipt / shipment. [Nav 2009 RTC].
Provided assistance for Nav client install following a change of PC for a user. Not our area of expertise. But got it working. [Nav 2013r2].

And sent out to our customers an April 2017 only promotion  - £100 off day rates for any service charged by the day excluding on site support. More details at https://www.dynamicsnavukhelp.co.uk/offers/https://www.dynamicsnavukhelp.co.uk/offers/. Applies to new customers as well.
That's all for this week folks.

Monday 27 March 2017

Week ending 24/3/17

Well a very interesting week last week. Heavily involved in assisting a client re lost data which took up a significant amount of the week for us. This has put a previously approved development request on hold for a few weeks.
Support queries included:

Weird cheque remittance report behaviour which is throwing cheque numbers out by a significant factor. Resolved late Friday last week so will deliver to client today for user testing. Caused by calculation of remittance lines per remittance report and therefore number of pages required for same cheque. [Nav 2009 Classic].
Resolved US sales tax set up issue client. [Nav 2013r2].
Sent step by step process based instructions on stock / items and back to back ordering (Special Orders). [Nav 2013r2]. Also confirmed how document approval delegation works. [Nav 2013r2].

Successfully restored 2 databases to a local PC here ready ready for developments once quotes approved. [Nav 2009 Classic, Nav 2013r2].

Development completed last week for BACS report export [Nav 2013r2].

Bar that completed the first remote training session on SOP, POP and back to back orders (special). [Nav 2013r2].
Quote for a new company signed off. Work will be completed this week. [Nav 2016].
First on site visit may take place this week [Nav 2016] but client will need to clear (pay) old invoice before this will happen. Do not often have to play hard ball with our clients but where needs must....
Anyway that is all folks.


Monday 20 March 2017

Week ending 17/3/17

Another quiet week last week for chargeable work but busy for fixed price first line support and we have received a number of client development requests last week which we will complete this week. More details on these further down the blog.
First line support activities included confirming how to assign default calendar to a company to resolve recurring journal error [nav2013r2], confirmed reason for Gen Prod Posting error on a journal and how to resolve (assign default to GL code) [Nav 2013] and confirmed default location code by customer already in Nav and queried requirements for restricting some views for warehouse employees. [Nav 2009 RTC].
We did do some chargeable work but this was a question and answer session via telephone and TeamViewer re the results of client transaction tests. [Nav 2016].
First bite for our new remote training service - client booked 2 hours this week.
We also submitted quotes for development requests arising from Q&A session above which have not yet been approved. Also confirmed what change would be required to display amount of settlement discount on posted sales invoice. [Nav 2016].
We now have the database backup (full sql backup) to development BACS extract report for client so we will complete this work (quote approved and PO number confirmed) this week. Also received database backups for more BACS reports required for same client but awaiting details of what is required and then we will quote for. [both Nav 2013r2] We are also due another database backup [Nav 2009 Classic] to complete report changes though we need to chase up approval of quotes pre start.
Received a request for a quote for a new company on the client's existing database. Queried whether quote needs to include customer and vendor masters as well as open transactions. Awaiting response then we will quote for. [Nav 2016].
And finally (yes this is going to be a busy week) we have received a client request to roll out a previous development re posting and emailing sales documents with an option to email an A4 version of the posted sales invoice whilst printing a continuous stationery version of the same invoice as well as emailing customer statements (not using standard Nav but a previously developed bespoke client statement). [Nav 2016].


Monday 13 March 2017

Week ending 10/3/17

A non chargeable week again. But again active on first line support as follows:
Amended rolling contract billing dates for quarterly and annual contracts. [Nav v4].
Resolved warehousing issues for a new warehouse location for bin and bin contents creation. Fixed errors on bin contents re bin contents type. Never resolved data migration issue re bin creation. Presume this is a 'feature'. [Nav 2009 RTC].
Confirmed process for fixed asset additions and sent on step by step processed based instructions with supporting screen shots to client to confirm how to create a fixed asset record. [Nav 2013r2].
Agreed terminology with client re live, test and local test databases.
Sent links to clients re report changes via MS Word. Also confirmed to same client rules re replenishment. [Nav 2016].
Submitted 2 development quotes for approval but client now decided to upgrade from 2016 to 2017 so no development changes allowed for now. [Nav 2016W1].

On the business front and given our lack of resource for on site support or training, we have created a new remote training service to offer to our current (and new) clients. Also working on an offer for day rates for specific services this week to start April 2017 so watch this space.
That's it for this week folks.

Monday 6 March 2017

Week ending 3/3/17

A first for the business since we started. No chargeable work at all last week but very busy with first line support calls and sent some quotes to clients for approval as well.
First line support calls included:
Amending VAT statement for new VAT Prod Posting Group after identifying difference on VAT statement to GL reflected missing VPPG. [Nav 2013r2].
Proposed new approach to rapidstart configuration for a new company after bespoke auto synching on item masters between companies wiped item details. Awaiting client feedback. Will start work if they approve approach. [Nav 2016 W1].
Confirmed changes required to GL posting matrix following user testing to get sales types to the correct sales GL code. Suggested other changes re balance sheet GL codes and posting groups to reflect reporting required. [Nav 2016].
Responded to very odd issue re item journal amount not reflecting quantity and unit cost. Suggested TeamViewer best approach but suspect other fields on line may be cause of the issue. [Nav 2009 RTC].
Confirmed best way to view and change bin rankings. [Nav 2009 RTC].
Confirmed approach after client user deleted posted bank statement. Basically we cannot restore posted bank statement and we cannot re-open closed bank ledger entries. Well we can but this would involve creating a bespoke codeunit and getting this added to the client's Nav licence so painful. Approach is leave as is with a missing bank statement but next bank statement will work. And also confirmed not to delete bank statements. [Nav 2013].
Confirmed no start date in addition to end date for Suggest Payments option off payment journal. Offered to quote for but no response from client as yet. [Nav v4].
Amended Goods In development recently delivered to remove some rules pre registering. [Nav 2009 RTC].
Confirmed auto item journal adjustment to bring stock back in after creating and posting a sales invoice for stock was not completed by Nav but a user. Do not get the same issue on local Nav database. [Nav 2009 RTC].
Completed set of change log across 2 databases and multiple companies for client as requested. [Nav 2017].
Quote sent off to add warehouse entry registered user and date to register picks and put aways list.
Quote confirmed and awaiting approval for more US sales tax analysis. [Nav 2013r2].
Re client outstanding work we are still waiting for Nav backups for approved quotes so we can get on with the developments. [Nav 2009, Nav 2013r2].

Monday 27 February 2017

Week ending 24/2/17

A quiet week upon which to reflect on what is next for the business. More news on that is a few weeks.
Work completed this week:
Investigated and reported on production costing issue and recommended immediate next steps. [Nav 2009 application, v4 database].
Added a new flowfield to bin table and relevant page. [Nav 2009 RTC].
Liaise with new ERP application providers (client moving away from Nav) to confirm table numbers and names for come key data. [Nav 2009 application, v4 database].
Sent step by step instructions on VAT statements and closing VAT periods. [Nav 2016].
That's it for this week.

Monday 20 February 2017

2 weeks ending 17/2/17

All sorts of issues arising in the last 2 weeks so that had kep us very busy. So apologies no blog last week.
Work completed in the last 2 weeks:
Another on site visit to support Nav 2016 implementation. Primarily focused on Finance department training. Misc support for a Nav 2016 go live in January including permission mods, step by step instructions. Development change re auto emailing posted invoice [Nav 2016] not using standard Nav. On site support visit focusing on assignment of permissions, review of profiles etc. [Nav 2013r2]. Created csv type xms for client for exporting GL entries and register data for user defined dates. [Nav 2017]. Tested and approved developments for a client completed by Solution Centre. [Nav 2017].
So that's it for this week.

Monday 6 February 2017

Week ending 3/2/17

Another week goes by.
Work completed last week included completing the Goods In development and delivered to client [Nav 2009 RTC], changes to Nav 2-17 role centres, completing soft planning production development (and delivering with step by step instructions) [Nav 2016], fixing (actually a work around) currency factor issue on credit memo bespoke development [Nav 2016], completing final alignment changes to cheque remittance report for pre printed stationery [Nav 2009 Classic] and an on site support client visit [Nav 2013r2].
Plans for this week include 2 client visits - 1 for on site training [Nav 2016] and the other for on site support [Nav 2016]. The remainder of the week will focus on the new company creation on a PL database which is taking much longer than expected due to database synch issues and the PL add on.
That's it for this week.

Monday 30 January 2017

Week ending 27/1/17

Work completed last week included
2 client on site visits - both Nav 2016 but one was to discuss requirements for enhancements and the other was to help with implementation and go live.
Completed work on 'Soft' planning development [Nav 2016]. More enhancements required.
Continued with work on Goods In. Development complete so just need to complete final testing today and then deliver.
New company created in Nav 2016. Needs configuration and transaction testing this week.
Plans for this week are:
Complete Goods In development and deliver to client. [Nav 2009RTC].
Complete changes to soft production plan and send step by step instructions on how to use in Nav 2016.
Complete initial new company configuration and test. If ok create another new company. Circulate vendors, customers and items from existing businesses and request client confirmation of which of each should be in the 2 new businesses. Create consolidation companies (2) and test. [Nav 2016].
1 on site client to demo back to back ordering and provide on site training for a new member of staff. [Nav 2013r2].
No other client visits this week but busy nonetheless.
That's all folks.

Monday 23 January 2017

Week ending 20/1/17

Another busy week last week with only 1 client on site visit.
Attended client site to draft up requirements. Following visit detailed requirements, proposed solution and quotes. Some 22 items. 2 approved over the week end so we will start these this week.
On attendance support required for Nav 2017 go live postponed as go live going really well.
Completed user permission changes as requested for Nav 2017 go live.
Provided assistance as required for loading opening vendor and customer balances for another Nav 2016 go live.
Provided on going first line support to client. [Nav 2013r2]. Sent an SLA for fixed price support to the same client
Changed US sales tax pages for new year - the pages detail sales and sales tax by month from 2015. [Nav 2013r2].
Completed initial transaction testing to check configuration for a Nav 2016 implementation. Also completed ship to address data load.
Started Goods In development. Will be completed this week / next week. [Nav 2009 RTC].
As I say a busy week.
Plans for this week:
2 on site client visits (1 ongoing support, discussion of requirements and one further support for Nav 2016 implementation), complete Goods In development [Nav 2009 RTC], create new companies as requested [Nav 2016 PL], fix cheque remittance report for latest changes [Nav 2009 Classic]. So busy week.
That's all folks.

Tuesday 17 January 2017

Week ending 13/1/17

Apologies for delay in the blog. Out at a new client site yesterday providing Nav 2016 support.
Anyway, work completed last week:
1 day on site support for Nav 2016 implementation to plan go live for 1st Feb and identify tasks that need to be done.
Potential new client visit to discuss how we can help. Now a client and hence yesterday's on site visit.
Complete minor development to switch off stock outs if end user does not want them when creating a sales order.
On site support to discuss next stages re Nav 2013r2 support following changes to key client personnel. In London and I travel by train. Managed to leave my ipad on the train which is a first. But thanks to Charlotte Sullivan from Virgin Trains I got it back. I am a dingbat!
Completed work on permission sets for Nav 2016 implementation which are being tested this week following the go live. If you have done this before you will be aware that we expect some error messages to show up for users and when they do we will resolve. At least the users do not start as super users.
Other developments completed included adding location code to a PO dataport.
Plans for this week:
1 day on site support for a new client on Nav 2016 (recent upgrade from Nav 2015).
1 day post go live support on Nav 2016.
Draft up and send list of work requested from new client with quotes by task for approval and then we can schedule the work.
Anyway that's all for this week folks.



Monday 9 January 2017

Week ending 6/1/17

Last week's work included:
Code fixes following upgrade from Nav 2013 to Nav 2016 (client managed their own application and data upgrade, we are just providing support as required) following go live last week Dec 2016.
Assign permission sets to users and create bespoke profiles / role centres for Nav 2016 go live mid Jan 2017 (client using minimal functionality in Dynamics Nav 2016 so out of the box profiles not appropriate).
Update Customer / Item sales report to include latest sales price for customer / item combination from sales prices lists table. [Nav application 2009 database v4].
New page developed to show FA list with depreciation start and end dates.
Updated raw materials requirements page to allow user selected line colours and soft planning (impact on raw material stock if changes made to production without raising a production order) [Nav 2016].
Plans for this week are mainly client visits.
That's it for this week.


Tuesday 3 January 2017

Period ending 30/12/16

Happy new year!
Obviously it has been a few weeks since the last blog (the time of year you know) but we were working last week so still worth doing one today.
Work completed last week was on a Nav 2016 go live this month re data migration and minor configuration changes and a check against an Excel journal template created by the client for copying and pasting into Dynamics Nav. That was it!
Plans for this week include no client visits, sorting profiles and permissions for users [Nav 2016] and uploading stock take results for client and posting [Nav app 2009 database v4]. So potentially a quiet week.
Next week there are 2 client on site support visits (one for a Nav 2016 go live in Feb 2017) and a potential client meeting locally. The week after that is a few days on site support following another client go live (Nav 2017).
So January is looking busy!
That's all folks.