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 31 July 2017
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!
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.
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!
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.
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.
Subscribe to:
Posts (Atom)
