In Touch with Dynamics (GP)

Management reporter not warning me to save.

2011-08-25T16:32:00.000+01:00

Hi Folks

Quick tip for MR, unlike FRX it will not always warn you to save changes when logining out, there is a Tick box under tools options which alows you to set MR to warn you.

The tick box is " Display confirmation before exiting Management reporter"

Emailing POs using new GP2010 word templates

2011-08-24T15:23:00.000+01:00

Hi Folks

Below are a few things to keep in mind when upgrading reports to Dynamics GP 2010 if you want them to work with the templates and email functionality (Also check out previous posts for required fields).

To ensure that Purchase Orders can be emailed out of GP2010 using the new word templates, the GP report in report writer must contain the following:

The purchase order number from the PO Document list table
Section additional header 1 based on the above field
Section additional footer 1 based on the above field

The word template will work OK without the above, but it will not email.

Most likely to be a problem In old upgraded reports from versions prior to Dynamics GP 2010

Andy Hall

Management reporter migration wizard (FRx)

2011-08-08T14:51:00.000+01:00

Hi folks, another quick Management reporter tip.

We have now done a fair few Management reporter upgrades/migrations from FRx. originally we had a few issues with the migration tool. However in the latest release (sp2) this now functions a lot better. However it will not bring across account sets or security. these will need to be re added manually.

any questions andrew.hall@touchstone.co.uk

Management reporter and segment names

2011-08-08T14:45:00.000+01:00

Hi folks its been very busy here of late and so the blog has taken a back seat ( if you want to know why we have been so busy type "Calyx touchstone" into bing and see what you get).

Anyway there are a few tips and discoveries to catch up on,

If the account segments in Dynamics GP aren’t named (so called segment1, 2, 3, etc) and you write your reports in MR with this format, if and when at a later date you decide to name your segments to something else (location, division etc), the reports will come back with no data.

To get round this you can do an edit/ replace on segment1 (2,3) with whatever your new segment descriptions are and your Management reporter reports will then function again, these do not update dynamically in MR when you change them in GP.

any questions please contact andrew.hall@touchstone.co.uk

How to create 32 bit ODBC data sources for Dynamics GP from a 64 bit server.

2011-04-26T17:21:00.001+01:00

Hi folks , this is a real quick handy hint. As you are probably no doubt aware Dynamics GP can not see 64 bit ODBC although it is compatable with 64 bit operating systems (versions 10 and 2010 only, service pack specific).

The 32 bit drivers are still on the server however if you create a datasource through ODBC settings it will create a 64 bit one by default.

To access the 32 bit drivers:

1. Browse out to %systemdrive%\Windows\SysWoW64\odbcad32.exe

2. Created short cut on desk top to odbcad32.exe

3. Created 32 bit odbc using odbcad32.exe

You will then have 32 bit ODBC datasources.

if you have any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP Bank Management - Checkbook [checkbook id] is already in user by user [username].

2011-04-26T11:59:00.000+01:00

Hi folks I have been quiet for a while as we have been exceptionally busy here a Touchstone and something had to give somewhere and that was the blog I am afraid.

Anyway I have just spent a rather frustrating half an hour trying to resolve a support case, where I could find no mention of the fix under partnersource or elsewhere on line despite this being a standard error message. Therefore I thought I would post this out there to save everyone else the frustration.

The error message is “Checkbook [checkbook id] is already in user by user [username]” or if you’re in the UK “Chequebook [chequebook id] is already in user by user [username]”.

This message was occurring when the user had crashed out of a reconcile and then tried to re access the reconcile window Transactions>Financial>Bank Management>Reconcile.

We had tried Clearing the Bank Management ACTIVITY under routines>financial>Bank Management but we still got the message.

We also tried clearing the DEX_LOCK and DEX_SESSIONS from the tempdb by running delete statements against both, but we still got the message.

We had checked the Contents of the CB100006 as suggested in an article by VAIDY however there was nothing here either.

http://community.dynamics.com/product/gp/gptechnical/b/gplearn/archive/2010/04/12/cbm-checkbook-91-checkbook-id-93-is-already-in-user-by-user-91-username-93.aspx

In the end though we needed to remove a record from the CBEU1020 CE ACTIVITY table.

select * CBEU1020 returned the locked record.

Then we ran a delete statement (as there was only one record in there)

Delete CBEU1020

And the issue was resolved.

If you have any questions please direct them towards the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Making the best of what you have got with Dynamics GP

2011-03-15T09:51:00.000Z

In the current financial environment we are seeing a lot of cost cutting, amalgamation of roles and other physical signs that people are trying to do more with less. However most people seem to pass over their Dynamics GP finance system and continue using it the way they have always used it since it was implemented (In some cases this is over 10 years ago and version 5.5).

On the whole people seem to worry about change especially in something as business critical as your finance system however Dynamics GP has come a long way in a short time and there is undoubtedly functionality within your system that you’re not using. This unused functionality may be the key to further cost savings.

Lets take a look at some of these types of functionality that are generally over looked, are they in your current version of Dynamic GP at present not being used or would a simple and cheap upgrade or third party add on provide this functionality with a quick ROI and attached cost savings.

eMail

Top of my list is email, does your Dynamics GP have the ability to email out documents?

The ability to email out statements has been in Dynamics GP for some time, however in Dynamics GP 2010 there are 39 other reports that can be emailed out using word templates including remittance advice and POs. Prior to Dynamics GP 2010 you would need a small add on called email Pro from Professional Advantage to email out Remittance advice and Pos and Sales orders.

There are several savings associated with this:

1. No Paper (you don’t need to purchase as much)

2. No postage

3. No envelope

4. Staff time stuffing and sealing envelopes

Its quite common to send out large billing runs by post or remittance advice for BACS payment runs, Think of the amount of time and money that could be saved if these paper based processes could be transferred to email.

BACS/EFT

Closely akin to the email option again time and money could be saved with electronic payment runs rather than printing cheques and stuffing envelopes.

Document Formats and templates

If you still need to send out paper communications, Dynamics GP has always allowed you to setup headers and templates for your documents which can include Logos and other images, however prior to Dynamics GP2010 there have been restrictions on bit map size for logo’s in report writer. In Dynamics GP2010 the new word templates allow for much larger and complex logo’s. These could be utilised and no more expensive headed paper with your company logo is required.

Procurement

Take a look at your procurement practises; are you using multiple supplies for the same items?

Are you purchasing them at wildly varying prices?

Look at your Dynamics GP what kind of reporting can you get on these purchases to help you make informed decisions? Smartlists and the new excel based reporting is ideal for tracking top 10 suppliers and items.

Tighter controls in place would allow you to make deals with specific suppliers. Dynamics GP deals effectively with these however you may want to put an authorisation process in place against budgets etc. and have an online requisition process. To do this you may want to look at a procurement system. ROI on these is generally very good. And they come in several sizes such as entry level systems like Nolan’s eRequest and Mid range solutions such as Complete right up to large solutions such as Proactis. All of these will integrate and work with Dynamics GP.

Mapping

Dynamics GP these days will utilise online mapping software like Bing maps. These can be used to help you group and assign client/customers geographically; this could help with travelling or shipping expenses.

Stream line processes

There maybe other processes within your Dynamics GP systems that you are doing the way you have always done, talk to your solution provider there may well be quicker and better ways of doing them now. A prime example is the Edit cheques batch window added in version 9 which allows you to see all your outstanding creditors and transactions in one window making it a lot easier to add transactions to a payment run. We still see a lot of people using edit cheques simply because that’s the way they have always done it. Another prime example is renaming columns in smartlists , most people don’t realise you can do it and it saves you a lot of fiddling after you have exported to excel.

Reporting

Better reporting will help you make more informed decisions and spot trends etc, as already mentioned this may be of particular help with procurement however also think about how you deliver those reports. A lot of finance departments I know are constantly inundated for requests for this report or that report placing a large drain on time and resources (that could be used elsewhere). If you have a company intranet can these reports be published on the intranet in a portal or dashboard and thus providing a self service reporting area freeing the finance team as well as providing instant access to relevant data. Frx has an HTML output option ideal for publishing on the web or you could deploy the out of the box SQL reporting services reports accessible of an IIS web site or sharepoint.

So in summary there are a fair few things you could look at with your existing Dynamics GP system that may well provide some measure of cost saving and allow you to do more with less. My advice would be talk to your system provider about the functionality in the Dynamics GP system and how you currently process; you may be pleasantly surprised by the results.

Andy Hall Helpdesk Manager TouchstoneGP andrew.hall@touchstone.co.uk

Our man in Fargo

2011-03-01T16:50:00.001Z

Hi folks

Adam Hamlington our dynamics GP product Manager is at the Microsoft Dynamics Tech conference in Fargo. You can follow the latest updates as Adam is tweeting on the TouchstoneGP twitter account direct from the conference.

So far announcements have been made regarding drill down into GP functionality in management reporter feature pack 2 and a word template generator due in GP2010 R2 to convert any report writer report into the new word template formats.

You can follow Adam's Tweeting on the below link.

http://twitter.com/TouchstoneGP

How to reprint a remittance advice in Dynamics GP 2010 after a payment has been posted

2011-02-17T14:37:00.000Z

Hi folks
This is one we get on the helpdesk a lot, how do I reprint my remittance? Well if you have fully posted the payment the simple answer is you can't. however with the new email functionality in Dynamics GP 2010 you can, with a small work around.

Simply set the BCC email adress to a generic mail box that everyone in finance has access to. This way when ever a remittance advice is emailed out it will also go to this addresses inbox. then if you need to re print it you simply go to the generic inbox and forward or print. This gets round the issue of the sent items being in indervidual outlook accounts for each staff member.

Andy Hall Helpdesk Manager Touchstone GP

andrew.hall@touchstone.co.uk

FRx Management Reporter migration Wizard and Office versions 64 bit v 32 bit

2011-02-17T09:46:00.000Z

Hi folks, here is a situation we have come across with the Migration wizard for FRx Management reporter for Dynamics GP 2010.

Simply stated the issue is this:

The old FRx databases are Microsoft Office Access databases and so the migration wizard needs certain parts of office connectivity to be able to read and convert the old spec sets into the new FRx Management reporter for Dynamics GP 2010 formats (which are now stored in SQL tables).

FRx Management reporter for Dynamics GP 2010. will only install the components for the operating system it is sat on, so if you are 64bit , it will use the 64 bit Microsoft Office 2010 Access components and if you are 32 bit it will use the 32 bit Microsoft Office 2010 Access components. not a problem so far I hear you cry.

Well now factor in the fact that the new word office template email functionality for Dynamics GP 2010 does not work on the 64 bit version of Microsoft Office 2010 and to get round this a lot of partners are installing the 32 bit version of Microsoft Office 2010 onto 64 bit operating systems in order to use the email functionality in Dynamics GP 2010. Couple this with the fact that if you have FRx Management reporter for Dynamics GP 2010 on a 64 bit operating system it will only use the 64 bit Office components, add the fact that you can not have 64bit office components on a machine that already has 32 bit office components and you have a problem. The Migration wizard will not be able to read the Access database.

So there you have the issue , of course it is easily solved simply do the migration on a machine with all 64 bit components (one you are not intending to use the email functionality from) and you will avoid this issue.

This is definitely a case of forewarned is forearmed.

Andy Hall Helpdesk Manager Touchstone GP

andrew.hall@touchstone.co.uk

New support tools...The Smart Phone

2011-02-11T09:46:00.000Z

We have started to see a new trend on the helpdesk, screen shots of error messages are being replaced by pictures taken with users smart phones and emailed to the helpdesk. It would seem that some clients find this easier and more convenient.
However this has started a discussion on the helpdesk and as prone to flights of fantasy as we normally are this idea actually seems to have merit.
How about a support app for your windows 7 or iphone that could take screen shots package them up and send them to your service supplier's helpdesk (where if they are using Dynamics CRM ) it could be automatically picked up and turned into a support case.
We believe there would be a lot of mileage in this, as it is we now have a sweepstake running on when we receive the first avi clip of an entire process culminating with the error.

If anyone does write the app we would be interested.

Andy Hall Helpdesk Manager Touchstone GP

andrew.hall@touchstone.co.uk

The Top 100 Most Influential People in Microsoft Dynamics 2011 Launch

2011-02-08T13:09:00.000Z

For those of you who are not already aware the Dynamicsworld web site run a top 100 of the most influential people within the Dynamics community every year. Nominations are now open for this year and you can see who has already been nominated on the below link:

http://www.dynamicsworld.co.uk/2011-Top-100-Nominations.php

Of course Mark Polino has already been nominated but if there is anyone not on the list that you feel should be (and meets the criteria) you can nominate them by sending an email to : nominations@dynamicsworld.co.uk

Tips,Tricks and Technology for Dynamics GP (Wine to)

2011-02-03T16:59:00.000Z

Just before Christmas the helpdesk team ran a successful Dynamics GP "Tips, Tricks and Technology" session at our Triton square offices in London. This was a free event and similar in format to Mark Polino's (Of Dynamics Accounting.net fame) "50 Tip" sessions run at the dynamics convergence events in the U.S. we also had a Technology update and finished with Drinks in the wine Bar opposite our offices.

This has proved so popular that we are going to do it again, this time on the 17th of March. There will be a different set of tips and tricks and a session devoted to year end (as its that time of year).

There will be a technology update from our team members that are attending the Dynamics technical conference in Fargo so a useful insight into what is coming this year and of course there will be drinks again afterwards.

The helpdesk team and some of the consultants will be there to answer your questions (but if leaving them till the drinks afterwards, get in early as I would not take advice on my finance system from a man on his 4th glass of Rioja).

You can follow this link to register or this one to the micro site for more information and to sign up for this event.

Alternatively you can contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Quick Excel Tip to roll down formulas in Dynamics GP excel reports

2011-01-21T17:29:00.000Z

I don’t know about you folks but it used to seriously frustrate me when you got a data set out of Dynamics GP into an excel report, created lots of funky formulas in your columns, then refreshed your data and got extra rows returned and your formulas did not copy down.

With the advent of the excel based reporting and other dynamically updating excel reports in Dynamics GP you come across this more and more.

Well there is a simple tick box in excel which will solve all your problems.

Goto the DATA tab on the tool ribbon in excel.

On the connections section next to the refresh All option you should have connections and under that properties.

Now properties may be greyed out., if it is click your cursor into one of the cells on the report which contains returned data. Properties should now be enabled.

Select properties and this should open the external Data Range Properties Window.

At the bottom of this is a tick box for “Fill down formulas in columns adjacent to data”

Tick this box.

Now when you refresh your data if extra rows are returned your formulas will automatically copy down.

Any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP 2010 word templates (more required fields SOP Blank History Invoice)

2011-01-12T11:59:00.000Z

Regular readers will now we put up a post in October 2010 detailing which vendorid field was required to allow the word template version of the remittance advice to email correctly.

http://intouchdynamicsgp.blogspot.com/2010/10/dynamics-gp-2010-word-templates-and.html

Well we have found another such required field, this time in the SOP Blank History Invoice.

SOP Blank History Invoice only works if the SOP Number from SOP Transaction Amounts History is the key break field on H1 and F1 in the Dynamics GP report. In other words “SOP Number" needs to come from the SOP HDR History table instead of the SOP LINE History table.

We are generally finding these sort of issues where a report has been modified in a prior version and then upgraded to 2010.

Here are the steps to change this:

1. Open up Report Writer and change Header Dummy 1 to use the Sales Transaction Amounts History table. Make sure the field SOP Number is selected as the break field.

2. Change Footer "Back Order" to use the Sales Transaction Amounts History table. Make sure the field SOP Number is selected as the break field.

3. Save the report.

4. Go back into GP and print the report to Standard > File > XML File. Make sure you select XML file in the file name window as well. Generate the XML File.

5. Reports>Template Maintenance. Pull up their template and click Modify. In Word, go to Field List and choose Remove Source.

6. Then choose Add Source and point it to your XML file from step 4.

7. Save the template.

8. Go back to GP and click the Green plus sign and point it to the newly saved template from step 7. Replace the template.

9. Now go email the report and it should work.

Any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Expert views

2010-12-22T09:38:00.000Z

The National Computing Centre (NCC) is the single largest corporate membership body in the UK IT sector and promotes the effective deployment of IT to maximise the competitiveness of its members' business, serving the corporate, vendor and government communities. You may already be familiar with its IT & business information website, the Evaluation Centre (http://www.evaluationcentre.com/ ) and its magazine, Conspectus (http://www.conspectus.com/ ). They publish advice and information on a range of subjects.

I have now been asked by the NCC to write a series of articles for their expert views section of the evaluation centre website, in the role of their resident Accounting & Financial reporting Software expert (don’t worry it’s not a new job I am still at Touchstone resolving GP issues).

The first Article is now up on the site and deals with the forthcoming iXBRL requirement for HMRC within the UK. You do need to sign up to read it but it is free.

The below link will take you straight to the Expert view articles:

http://www.evaluationcentre.com/accounting_software_financial_reporting_software/strategy/expert_view.go

I would also like to take this opportunity to wish you all a Merry Christmas and a happy new year

Andy Hall
Helpdesk Manager TouchstoneGP

andrew.hall@touchstone.co.uk

Dynamics GP 12 tips of Christmas

2010-12-16T16:39:00.000Z

On the first day of Christmas my true love gave to me a brand new Financial Year

Tools> setup > company > Financial periods

In the year box enter your new year, check the first and last days, add the number of periods you require then select calculate, then ok , and voila you have a new year.

On the Second day of Christmas my true love gave to me A smartlist to check my account posting types.

Open smartlists goto financial and accounts. You will notice posting type is brought in by default. You can now set up search criteria based on your account structure to return accounts within the balance sheet range that do not have a posting type of balance sheet. In this way you can check the account posting types before yearend , the number one cause of year end issues being an incorrect posting type.

http://intouchdynamicsgp.blogspot.com/2009/09/no-1-cause-of-year-end-issues.html

On the third day of Christmas my true love gave to me a link to the online manuals ( so I could do her job while she was off living it up over the festive period)

Help> printable manuals

Here you will find manuals for most modules with instructions on how to complete most processes on the system.

On the fourth day of Christmas my true love gave to me advice on how to change to 20% tax in January.

See the below blog article for instructions

http://intouchdynamicsgp.blogspot.com/2010/09/all-change-on-20-tax-again-january-2011.html

On the fifth day of Christmas my true love gave to me a full backup before my Year end

Once you hit that process button for year end there is no undo, so you need to make sure you have a full backup before hand (just in case)

http://intouchdynamicsgp.blogspot.com/2009/09/what-should-i-back-up.html

On the sixth day of Christmas my true love gave to me a hard copy of my year end report.

There are no reprint options for the year end reports so , always print a hard copy or print to file, either way make sure you retain a copy.

http://intouchdynamicsgp.blogspot.com/2010/03/year-end-comes-before-2010-year-end.html

On the seventh day of Christmas my true love gave to me a customer list extracted from smartlist to send seasonal greetings (via a word mail merge).

Smartlists

Goto sales and customer addresses

Here you can output a list of your customer addresses to excel, once in excel this could be used to provide envelope addresses or contact details in a word mail merge document to send seasons greetings to all your customers.

On the eight day of Christmas my true love gave to me strict instructions not use GP (During or immediately after the office party whilst possibly under the influence)

Nuff said, don’t drink and post journals.

On the ninth day of Christmas my true love gave to me the support debugging tool (to change company background colours to something festive)

This is a great tool and on a serious note with the new floating GP windows its often difficult to tell which company your in if you have multiple companies open at a time on one machine. So why not colour code them , could save a lot of trouble with miss posted journals etc.

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2009/08/07/support-debugging-tool.aspx

On the tenth day of Christmas my true love sent to me a budget for a Dynamics GP2010 upgrade (because its worth it).

Everyone should be asking Santa for this.

On the eleventh day of Christmas my true love gave to me a free download of Power pivot

For those that don’t know this is an incredibly powerful free add in to excel 2010, when combined with the other excel functionality in Dynamics GP this becomes a must have.

http://powerpivot.com/download.aspx

http://powerpivot.com/index.aspx

On the twelfth day of Christmas my true love gave to me a link to the Microsoft partner network festive game (to keep the IT dept interested, so they don’t decide to upgrade the network over the festive period without checking for compatibility with Dynamics GP first).

You laugh , it has happened to us two years on the trot on the helpdesk, sheepish calls from clients who suddenly find issues with frx and other functionality because IT decided to use the quite time to upgrade operating systems or servers and did not check for compatibility first. Please, please, please, please, check with your helpdesk before updating operating systems.

http://festivegame.cloudapp.net/?CR_CC=200018091

If you have any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Merry Christmas

Forecaster 7 and the amazing expanding Z_RAW table

2010-12-01T16:11:00.000Z

It’s been a while since I blogged simply because we are so busy at the moment. GP2010 is flying off the shelves in a very satisfactory way.

An odd issue with Forecaster 7 came to light the other day so I thought it best to set aside some time to create an article.

It all centres on the Z_RAW sql table which holds the data against cost code and account by period. The issue is caused by the way the data is stored. Every time you create a new period in forecaster it creates a new column against that cost code/account combination in the Z_RAW table.

Now because data is held against period, if you want to run previous input sets and reports as well as current ones you are going to need to keep creating new periods rather than re using the same ones.

So if you have 12 periods (Not unusual) and you want to do Quarterly Forecasts you will need to create 4 sets of the 4 periods which works out at 48 separate periods , so that is 48 extra columns added to the Z_RAW table.

There is a 1024 column limit on a non wide SQL table and a 1000 column limit when using replication. So using the above example it is going to take you 20 years till you reach the limit of the SQL table (That’s not so bad, I hear you cry). Well we have several clients who like to report on a weekly period structure, so the standard structure is 52 periods and if using the quarterly format that’s 208 extra periods a year. This means you reach the table limits in 4 and half years. If you throw in a 12 period frame work as well you reach that limit in just under 4 years.

The long and the short of it is, it’s not an issue if you know about it in advance as you can plan ahead and remove old data but if you don’t know about it, it could catch you out.

Forewarned is forearmed with forecaster.

If you have any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP Fully applied payments stuck in Open

2010-10-21T10:31:00.001+01:00

I was on the Microsoft forums recently helping to resolve the above issue for a partner in the UK. Ordinarily fully applied payables documents automatically move to history, however every now and then they don’t and they need a little nudge.

During the course of this forum post the standard process for forcing this move did not work and Jon (another Touchstone consultant) was able to offer other alternatives and I was also able to dig out an old script from our sql archives from version 6 days (may need the odd tweak for 2010).

As such a wealth of advice came out I thought it was worth documenting hear.

Standard Process;

The standard process is to rebuild the PM master keys (Delete PM00400) and the run checklinks on the payables transaction and transaction history logical groups to rebuild the PM00400 table. It is worth noting that you can lose some drill down ability doing this. Make sure you do a back up first.

This should do the job 9 times out of 10.

Remittance process:

Jon (Our Tame Dex Developer) has discovered that in some cases the transactions do not move if you have records in the PM20100 and they have a KEYSOURC of REMITTANCE. The assumption is that checklinks wont move them until the remittance is printed.

Jon has found that if you delete the records from the PM20100 and then run the standard process the records move.

The Move routine:

Jon has also found that you can run the move routine indervidually with the following SQL code.

declare @FuncCurr varchar(15)

declare @ErrorState int

select @FuncCurr = FUNLCURR from MC40000

create table #CNTRLNUMTEMP

(

CNTRLNUM VARCHAR(21) NOT NULL,

DOCTYPE SMALLINT NOT NULL,

VENDORID VARCHAR(15) NOT NULL

)

exec pmclmovefullyapplied

'sa', @FuncCurr, 'PM_Transaction_OPEN', '%1', @ErrorState output

select * from SY03400

delete SY03400

SQL Script to move open to history:

If all of this fails i have in my archive a SQL script to move open to History. This was written for version 6 originally so may need some tweaking for 2010.

/*

** Procedure Name: PM move open to history for R6

**

** Description:

**

** Script is for R6 PM transactions that show fully applied and are still in the open table.

**

** Important:

** There are numerous places where the Voucher Number, Document Type, Control Number, or Vendor ID

** must be provided. To find these locations do a search on 00000000000000001. Replace 00000000000000001

** with the voucher number you want to move to history.

** Also do a search on '??????????' and replace this with the Vendor Id of the voucher.

** If the invoice needs to be moved then change DOCTYPE to 1 and CTRLTYP to 0.

** If the payment needs to be moved then change DOCTYPE to 6 and CTRLTYP to 1.

** For the Distribution section, the History has a DOCTYPE but the Work does not. The script is

** hardcoded for invoices. If the document is a payment, in the line following the 'select' in

** PM30600's insert statement, replace the 1 with 6.

**

** This script does not update reprint information (the PM80000's tables).

**

**

** Database:

**

** Any

**

**

** Tables:

**

** SQL Table Access Method

** --------------------- -------------

** PM30200 Read/Write

** PM20000 Read/Write

** PM00400 Read

** PM30300 Read/Write

** PM10200 Read/Write

** PM30600 Read/Write

** PM10100 Read/Write

** PM10500 Read/Write

** PM30700 Read/Write

**

**

******************************************************************************************

*/

begin

insert into PM30200 (VCHRNMBR,VENDORID,DOCTYPE,DOCDATE,DOCNUMBR,DOCAMNT,

CURTRXAM,DISTKNAM,DISCAMNT,DSCDLRAM,BACHNUMB,TRXSORCE,

BCHSOURC,DISCDATE,DUEDATE,PORDNMBR,TEN99AMNT,WROFAMNT,

DISAMTAV,TRXDSCRN,UN1099AM,BKTPURAM,BKTFRTAM,BKTMSCAM,

VOIDED,HOLD,CHEKBKID,DINVPDOF,PPSAMDED,PPSTAXRT,

PGRAMSBJ,GSTDSAMT,POSTEDDT,PTDUSRID,MODIFDT,MDFUSRID,

PYENTTYP,CARDNAME,PRCHAMNT,TRDISAMT,MSCCHAMT,FRTAMNT,

TAXAMNT,TTLPYMTS,CURNCYID,PYMTRMID,SHIPMTHD,TAXSCHID,

PCHSCHID,FRTSCHID,MSCSCHID,PSTGDATE,DISAVTKN,CNTRLTYP,

NOTEINDX,PRCTDISC,RETNAGAM,ICTRX,Tax_Date,PRCHDATE,

CORRCTN,SIMPLIFD,APLYWITH,Electronic,ECTRX,

DocPrinted,TaxInvReqd,VNDCHKNM)

select

VCHRNMBR,VENDORID,DOCTYPE,DOCDATE,DOCNUMBR,DOCAMNT,

CURTRXAM,DISTKNAM,DISCAMNT,DSCDLRAM,BACHNUMB,TRXSORCE,

BCHSOURC,DISCDATE,DUEDATE,PORDNMBR,TEN99AMNT,WROFAMNT,

DISAMTAV,TRXDSCRN,UN1099AM,BKTPURAM,BKTFRTAM,BKTMSCAM,

VOIDED,HOLD,CHEKBKID,DINVPDOF,PPSAMDED,PPSTAXRT,

PGRAMSBJ,GSTDSAMT,POSTEDDT,PTDUSRID,MODIFDT,MDFUSRID,

PYENTTYP,CARDNAME,PRCHAMNT,TRDISAMT,MSCCHAMT,FRTAMNT,

TAXAMNT,TTLPYMTS,CURNCYID,PYMTRMID,SHIPMTHD,TAXSCHID,

PCHSCHID,FRTSCHID,MSCSCHID,PSTGDATE,DISAVTKN,CNTRLTYP,

NOTEINDX,PRCTDISC,RETNAGAM,ICTRX,Tax_Date,PRCHDATE,

CORRCTN,SIMPLIFD,APLYWITH,Electronic,ECTRX,

DocPrinted,TaxInvReqd,VNDCHKNM

from PM20000

where DOCTYPE = 1

and VCHRNMBR = '00000000000000001'

and VENDORID = '??????????'

delete PM20000

where VCHRNMBR = '00000000000000001'

and DOCTYPE = 1

and VENDORID = '??????????'

print 'Your insert into PM30200 is complete. Now continue with update of the PM00400 table.'

/*This script will update the PM00400 table and flag the document from Open to History */

/*The CTRLNUM is the voucher number. The CNTRLTYP is 0 for invoice and 1 for payment */

update PM00400 set DCSTATUS = 3

where CNTRLNUM = '00000000000000001' and VENDORID= '??????????' and DCSTATUS = 2 and CNTRLTYP = 0

print 'Your update on PM00400 is complete. Now continue with insert on the PM30300 table'

end

/* This script will move the apply records from Apply to Work Open to Apply to History and then

** delete the PM10200 records. The apply to Voucher Number must be provided, which is the

** invoice voucher number.

*/

begin

insert PM30300

(VENDORID,DOCDATE,DATE1,GLPOSTDT,TIME1,VCHRNMBR,

DOCTYPE,APFRDCNM,ApplyFromGLPostDate,FROMCURR, APFRMAPLYAMT, APFRMDISCTAKEN,

APFRMDISCAVAIL,APFRMWROFAMT,ActualApplyToAmount,ActualDiscTakenAmount,ActualDiscAvailTaken, ActualWriteOffAmount,

APFRMEXRATE,APFRMDENRATE,APFRMRTCLCMETH,APFRMMCTRXSTT,APTVCHNM, APTODCTY,

APTODCNM,APTODCDT,ApplyToGLPostDate,CURNCYID,CURRNIDX,APPLDAMT,

DISTKNAM,DISAVTKN,WROFAMNT,ORAPPAMT,ORDISTKN, ORDATKN,

ORWROFAM,APTOEXRATE,APTODENRATE,APTORTCLCMETH,APTOMCTRXSTT,PPSAMDED,

GSTDSAMT,TAXDTLID,POSTED,TEN99AMNT,RLGANLOS,APYFRMRNDAMT,

APYTORNDAMT,APYTORNDDISC,OAPYFRMRNDAMT,OAPYTORNDAMT,OAPYTORNDDISC,Settled_Gain_CreditCurrT,

Settled_Loss_CreditCurrT,Settled_Gain_DebitCurrTr,Settled_Loss_DebitCurrTr,Settled_Gain_DebitDiscAv,

Settled_Loss_DebitDiscAv)

select

VENDORID,DOCDATE,DATE1,GLPOSTDT,TIME1,VCHRNMBR,

DOCTYPE,APFRDCNM,ApplyFromGLPostDate,FROMCURR, APFRMAPLYAMT, APFRMDISCTAKEN,

APFRMDISCAVAIL,APFRMWROFAMT,ActualApplyToAmount,ActualDiscTakenAmount,ActualDiscAvailTaken, ActualWriteOffAmount,

APFRMEXRATE,APFRMDENRATE,APFRMRTCLCMETH,APFRMMCTRXSTT,APTVCHNM, APTODCTY,

APTODCNM,APTODCDT,ApplyToGLPostDate,CURNCYID,CURRNIDX,APPLDAMT,

DISTKNAM,DISAVTKN,WROFAMNT,ORAPPAMT,ORDISTKN, ORDATKN,

ORWROFAM,APTOEXRATE,APTODENRATE,APTORTCLCMETH,APTOMCTRXSTT,PPSAMDED,

GSTDSAMT,TAXDTLID,POSTED,TEN99AMNT,RLGANLOS,APYFRMRNDAMT,

APYTORNDAMT,APYTORNDDISC,OAPYFRMRNDAMT,OAPYTORNDAMT,OAPYTORNDDISC,Settled_Gain_CreditCurrT,

Settled_Loss_CreditCurrT,Settled_Gain_DebitCurrTr,Settled_Loss_DebitCurrTr,Settled_Gain_DebitDiscAv,

Settled_Loss_DebitDiscAv

from PM10200

where APTVCHNM = '00000000000000001'

and APTODCTY = 1

and VENDORID = '??????????'

delete PM10200

where APTVCHNM = '00000000000000001'

and APTODCTY = 1

and VENDORID = '??????????'

print 'Your update on PM30300 is complete. Now continuing with insert on the PM30600 table'

end

/* This script will move the distribution records from the Distribution Work Open to Hist and

** then deletes the PM10100 records. The Voucher Number must be provided. The CNTRLTYP is 0

** for invoice and 1 for payment.

*/

begin

insert into PM30600

(DOCTYPE,VCHRNMBR,DSTSQNUM,CNTRLTYP,CRDTAMNT,DEBITAMT,

DSTINDX,DISTTYPE,CHANGED,USERID,PSTGSTUS,VENDORID,

TRXSORCE,PSTGDATE,CURNCYID,CURRNIDX,ORCRDAMT,ORDBTAMT,

APTVCHNM,APTODCTY,SPCLDIST,DistRef)

select

1,VCHRNMBR,DSTSQNUM,CNTRLTYP,CRDTAMNT,DEBITAMT,

DSTINDX,DISTTYPE,CHANGED,USERID,PSTGSTUS,VENDORID,

TRXSORCE,PSTGDATE,CURNCYID,CURRNIDX,ORCRDAMT,ORDBTAMT,

APTVCHNM,APTODCTY,SPCLDIST,DistRef

from

PM10100

where VCHRNMBR = '00000000000000001'

and VENDORID = '??????????'

and CNTRLTYP = 0

delete PM10100

where VCHRNMBR = '00000000000000001'

and VENDORID = '??????????'

and CNTRLTYP = 0

print 'Your update on PM30600 is complete. Now continuing with insert on the PM30700 table'

end

/* This script will move the Tax records from Tax Work to Tax History and then deletes the

** PM10500 records. The apply to Voucher Number must be provided.

*/

begin

insert PM30700

(VENDORID,VCHRNMBR,DOCTYPE,BACHNUMB,TAXDTLID,BKOUTTAX,

TAXAMNT,ORTAXAMT,PCTAXAMT,ORPURTAX,FRTTXAMT,ORFRTTAX,

MSCTXAMT,ORMSCTAX,ACTINDX,TRXSORCE,TDTTXPUR,ORTXBPUR,

TXDTTPUR,ORTOTPUR,CURRNIDX)

select

VENDORID,VCHRNMBR,DOCTYPE,BACHNUMB,TAXDTLID,BKOUTTAX,

TAXAMNT,ORTAXAMT,PCTAXAMT,ORPURTAX,FRTTXAMT,ORFRTTAX,

MSCTXAMT,ORMSCTAX,ACTINDX,TRXSORCE,TDTTXPUR,ORTXBPUR,

TXDTTPUR,ORTOTPUR,CURRNIDX

from PM10500

where VCHRNMBR = '00000000000000001'

and DOCTYPE = 1

and VENDORID = '??????????'

delete PM10500

where VCHRNMBR = '00000000000000001'

and DOCTYPE = 1

and VENDORID = '??????????'

print 'Your update on PM30700 is complete. Move process is complete.'

end

any questions please contact helpdesk@touchstone.co.uk or myself Andrew.hall@touchstone.co.uk or our tame dex developer jonathan.eastman@touchstone.co.uk

Dynamics GP and switching it off and on again (that fixes everything..doesn’t it?)

2010-10-18T10:50:00.000+01:00

I got a joke email this morning entitled “Interesting Statistics”. One of the statistics was the likelihood of a computer issue being solved by switching it off and on again. I smiled at this thinking “how true” and then I realised that this can be a potentially problematic attitude to have with Dynamics GP, after all we are dealing with transactional data which does change status and transfer between tables on a regular basis. An interruption to this process can cause issues.

So here is my guide to switching it off and on again.

First things first, is it still doing something?

• Check the process monitor, Microsoft Dynamics GP button and process monitor. Here you can see if there are any processes queued up on your machine. You can take an informed decision as to whether that process is transactional in nature. Some processes can be suspended or even removed. Note the system will not allow you to remove certain processes.

• Check the Task manager on your work station. See if there are other processes running that can free up memory, make sure you are not maxed out on CPU usage. Check the amount of available ram as opposed to page file usage. Page files are actually on your hard disk as opposed to ram (on a chip) and so are naturally slower.

If you really have no choice, crash out.

This is not as drastic as it seems. Since Dynamics GP version 6 we have had batch recovery, this will catch a lot of interruptions etc, and allow you to continue posting. You should get a nice friendly message when you re enter Dynamics GP that there is a batch awaiting you in batch recovery.

Also remember if you crash out your user will be locked in. In versions 9 and above of Dynamics GP you will be able to delete your own activity at login and log back in , if you are on an earlier version you will need to get your system administrator to remove your activity.

Some times it may become necessary to stop and start SQL, this is the relational database behind Dynamics GP. This is usually done to clear down sql temporary tables etc and should never be done with users still in the system (and a viable backup).

However this is the important thing, don’t crash out or reboot or stop and start without seeking advice from your helpdesk/reseller first. It may seem silly, it may be something that you don’t feel you should bother us with, but at the end of the day we would rather be safe than sorry.

If you have any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP 2010 word templates and required fields to allow emailing or why won’t my modified word template email.

2010-10-14T14:59:00.000+01:00

Hi folks this is one we have discovered the hard way. This issue only occurs when you use a modified report as the basis for a word template. In our case it was the remittance advice.

We modified the word template as per the instructions at the end of the Dynamics (GP) 2010 report writer manual. The template was pickup up fine and brought to screen and displayed properly when running the report. The word document could be printed etc. but it would not email.

We talked to Microsoft about this and they advised us that they had had several cases recently where certain fields missing from certain parts of the template had prevented the application identifying the vendor.

Using this as a starting point vendor ID was the obvious place to start looking , however we did have VendorID on the report.

What we discovered was this.

The report writer report needs the VENDORID field from pmRemittancetmp table to be placed anywhere in the report.

Our report used the VENDORID from PM Payment Work in the RH section, we replaced it and all then emailed correctly.

So you need to be careful when modifying reports that you intend to use in a word template, one vendorid is not as good as another. We can also surmise that this is true for many of the other reports.

As and when we find out what the other key fields are on the other reports we will update this blog, in the mean time if you discover any feel free to update the comments.

Any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

How to avoid blank address lines in Dynamics GP report writer.

2010-10-12T15:40:00.001+01:00

This is one that is cropping up more and more with the advent of electronic mail reading systems. We have had several calls on the helpdesk from clients who have had mailings returned because of blank lines in the address which is stopping the electronic systems used by the post office reading the address correctly.

The issue is caused by the fact that not all customer or creditor addresses are long enough to use all the address fields. This means that there can be blank lines between the last address line used and the post code (Zip code for our cousins across the pond).

You can get round this using calculated fields.

Step1: create a new calculated field in report writer (I am using the RM statement on blank paper).

Step2 : Set the result type to string.

Step3: Select the function tab and then ‘user-defined’ and the function of ‘rw_selectAddrLine’ and insert.

Step 4: Now select the ‘constant’ tab and integer as type and the constant of 1… (this means the first address line. when you do a cal field for address line 2, 3, 4 etc.. the integer value will change accordingly to 1, 2, 3, etc.). Then select add.

Step 5: Next you must select all the address lines and add them.

From this example (RM statement) the resource is ‘rm statement header temp’

Then select address 1, 2, 3 city, state, zip and insert them all one by one

Step 6: Then once all the address lines have been added go to the Constant tab and select the type as ‘string’ and leave the constant blank and click insert

You will notice it inserts ‘’ you must insert 3 of these symbols..

The reason being you need to have 10 conditions..

So we selected the integer as ‘1’ in the beginning and then 6 address lines so we need 3 blank strings to get our total of 10.

Step 7: Now repeat steps 1 to 6 for each of the address lines (the above is the calc field for address line 1) you must create 5 further fields for address line 2,3 4 etc.. and remember the constant integer changes according to the number of the address line you are doing.. 1,2,3 etc..

Step 8: deploy the calculated field address lines in the report one underneath the other. The rw_selectAddrLine’ function will then take care of any blank lines when you run the report selecting the line if populated but if not picking the next populated line.

If you have any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

How to Reconcile RM to GL in Dynamics GP using smartlists.

2010-10-12T10:53:00.002+01:00

If you are not on version 10 or 2010 of Dynamics GP then you won’t have the GL reconcile tool. This article is intended to give advice on how to reconcile without this using the functionality in Excel.

If you were in balance last month, then you can create a report for the receivables transactions based on the system date range and then create a report for GL (account transactions) for the system date range. This way, you can compare when the information was physically entered in the system (even with a different document date between modules). If one of the modules has the transaction posted and the other is missing, you can determine if the transactions were posted with a different date in GL than in receivables.

Within Smsrtlists, open up the receivables transaction option. Add the column Posted Date. This column stores the date from your computer of when the document was physically entered in receivables. Even if the document date was for the previous year, the posted date stores the date of when you physically entered it. You can compare the posted date to the posting date (holds the document date) or the document date as well. You can narrow your search by entering this months posted date since you were in balance last month. This will tell you all of the transactions that were entered in receivables since then and you can compare your GL report to that and see if one module is missing the transaction, has a different document date, or a wrong amount as well(possibly the batch was edited in GL before it was posted).

Next, you will want to open the account transaction option within Smartlists. Add the columns Originating Posted Date and Originating Document Number. This stores the posted date (system date) from the originating module. Even if you change the batch date, this stores the date of when it was entered. You can compare the originating posted date to the trx date (document date) in account transactions as well to see if they vary from what your receivables transaction report returns. You may also want to add the Originating Document Number and Originating Master ID (debtor id) to this report, that way you can tick transactions off by using the document number instead of looking for amounts.

These reports will give you a good guideline on trying to narrow down when something was entered, but there could be other possibilities that could be a cause such as a posting interruption (but this may have updated one module and not the other so you can compare what's missing), receivables history was removed (which only effects receivables and not GL).

At this point you can actually use excel functionality to make life easier. If both sheets (RM and GL) are placed in the same excel work book , you can then create an extra column returning a result based on a vlookup between the two sheets , based on originating document number on the GL and document number on the RM , this will do a lot of the hard work for you. You then only need to investigate those transactions not matched up by the Vlookup.

If you have any questions on this please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

How to free a marked batch without SQL in Dynamics GP

2010-10-07T10:39:00.002+01:00

We have just had a call on the helpdesk where the client said “ I have one of those stuck batches, can you stream in and free it in SQL?”.

It occurred to me that we have all become so use to freeing batches marked for posting in Dynamics GP by diving straight into SQL that we have forgotten the lessons we learned back in version 5 when the product was eEnterprise or Dynamics and the manufacturer was Great Plains.

Back then when Dynamics GP was young, the fastest dial up was a 64k modem and we used frustratingly slow software like PC Anywhere to remote access client sites, so we tried to do as much through the front end, over the phone as possible before taking the sql option.

One of these little tricks was master posting. If a receivables batch was showing as marked for posting, but no one had and so could not be accessed, the first stop would be master posting under routines. Here it would usually be showing as available despite showing as marked under receivables batches. To free it up all you needed to do was mark it for posting in master posting and then unmark it. Go back into receivables batches and there it was ready to post.

Well I just tried this on a Dynamics GP version 10 install and guess what, it still works.

So there you have it, how to free up a batch marked for posting without diving into SQL.

If you have any question please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Creating new companies in Dynamics GP, what tables should I copy?

2010-10-01T15:38:00.000+01:00

Well the simple answer is don’t, most people don’t realize that you no longer need to DTS setup information into a new company from table to table or even import chart of accounts with integration manager.

We get asked this one a lot on the helpdesk as creating a new company is not something most systems administrators do regularly.

There is a copy company setup tool which will do this for you, simply tick what you want it to copy across. Versions 9 and 10 can be downloaded from automated solutions on the following link

https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={04AF87A8-8FD9-4BE5-9140-7B34BB2DA5C0}&NRORIGINALURL=/customersource/support/selfsupport/automatedsolutions&NRCACHEHINT=Guest&wa=wsignin1.0

and version 2010 is included in the PSTL tool kit.

It is a lot simpler than using DTS, a word of warning though , be careful when copying company or system specific information you can create redundant entries in tables.

For further advice contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

The Clock is ticking for Dynamics GP version 9

2010-09-27T10:40:00.000+01:00

This post is by way of a quick reminder that as of 11th January 2011, Microsoft will no longer be supporting Dynamics GP version 9. Therefore if you wish to stay on a manufacturer supported version of Dynamics GP and you are on version 9, you now have three months to plan, test and complete an upgrade to one of the supported versions.

A lot of clients have been holding off upgrading to Dynamics GP 2010 until service pack 1 was released. This was released last week and we have now installed it in our in house test environment.

Also Service pack 1 for Management Reporter (2010 FRx replacement) is now also available which will allow successful installation on UK regional settings.

If your interested in upgrading to Dynamics GP 2010 please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

For further information on support life cycles of Microsoft products use the below link.

http://support.microsoft.com/gp/lifeselectindex#D

All Change on 20% Tax Again January 2011

2010-09-20T14:00:00.002+01:00

Tax Changes in Dynamics (GP)

This is a quick re working of the advice we put together last time the VAT changed from 17.5 to 15% and then again from 15% back to 17.5%. This change is happening in January 2011 so now would be a good time to start thinking about how this might affect your systems. The changes in VAT where originally set out in the Chancellors emergency budget 2010 (The full details are in the HMRC link at the end of this article). Because of the nature of Tax calculations in Dynamics (GP) this article is intended purely as a Guide and you will need to choose the appropriate actions for your circumstances.

Note: We have kept these notes fairly generic as we have clients on several different versions, however in version 10 and 2010 where we give a path to Setup>company etc these are found under Tools> setup > Company

Tax Details

We advise that everyone will need to set up a new set of tax details to replace the 17.5% details currently used. We recommend that you did not simply change the rate on your existing detail as this could cause you reporting problems and issues when trying to post back.

To set up a new Tax detail you need to go to Setup>Company>Tax details

You needed to set up a minimum of two details, one for sales and one for purchasing. This needed to be done in each of your companies.

Tax Schedule

Here you have Two choices.

Option 1: We advise that you could retain the existing Tax schedule and simply remove the 17.5% detail from this schedule. Then add the new 20% detail to the schedule and to the ALL Sales and ALL purchasing schedules that you have setup on the company. Schedules can be accessed from setup>Company>Tax Schedules. This has the advantage of not then needing to change any setup on classes , debtors, creditors , items or projects. Simply put where ever the old 17.5% detail appears in a schedule on its own (No other details)you will need to replace it with the 20% detail and wherever it appears with other details you will need to add in the 20% detail.

Option 2: is to setup two new Tax schedule (one sales one purchasing). Again this is done through setup>company>Tax schedules. Once these have been crested you will also need to add the 20% Tax detail to the existing All sales and All Purchasing tax schedules. However if you create a new schedule you will need to change all the card records within dynamics that have a schedule attached. These are Debtor maintenance, Creditor Maintenance, Item maintenance, Cards project categories, SOP setup options default tax schedules , and the appropriate Classes for all of the above , this will also need to be done in each company.

VAT Reporting and Vat input and Output codes

If you are using the standard Vat reporting within Dynamics (GP) this all works off of Tax detail ID so if you have created a new detail there should be no issues. However some of our clients are reporting directly off of the GL account code. If this is the case you will need to setup two new GL accounts for the new tax rate (input and output accounts) and add these accounts into the new details you have created.

Setup new accounts under cards >Financial>Accounts remember it will need to be a balance sheet account.

The Account can be associated with the Tax detail Setup>Company>Tax detail id.

You may wish to do this even if not reporting directly of the GL.

Sales Order Processing

SOP will cause some issues as any outstanding transactions created this week will retain their 17.5% tax detail when transferred to invoice (This is not a problem for POP as this recalculates). The Tax setup options for SOP are on the options Tab of the Sales Order setup window found under Setup>Sales> Sales order processing. To get round this issue you will need to go back and change the tax on the order to the new rate before transferring to invoice.

For a method of recalculating the tax on SOP Transactions, have a look at David Musgrave's blog as there is now functionality in the support debugging tool which will allow you to do this.

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2010/09/21/changing-sop-tax-rates-using-the-support-debugging-tool.aspx

Nolan’s Advanced VAT

We have spoken to Nolan’s and they are issuing no specific advise however like us they are advising to create new details rather than update existing ones. These are found in the same place as the standard Tax details as these are alternate windows.

Note: if using Nolan’s advanced VAT you can set an account to be Taxable, in which case a tax schedule is held against the account as well as an individual Tax ID , these will need to be changed as well where they are using the 17.5% tax detail. These are accessed under cards>financial>Account .

Project Accounting

Depending on how your projects are setup , you may need to change the tax schedules on Cards> Projects> cost category.

Further Advice from the Government

For further detailed information and HMRC guidance about the original change, please visit the HMRC Website at http://www.hmrc.gov.uk/vat/forms-rates/rates/rate-rise-guidance.pdf

No advice has been issued by Microsoft at this time , but when they do we will update you.

If you have any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Calling all Dynamics GP users in the UK. YOUR PRODUCT NEEDS YOU

2010-07-08T14:42:00.000+01:00

As most UK users will be aware HMRC are changing the company tax reporting requirements as of the 1st of April 2011. All reports will need to be submitted online in iXBRL format.

Management reporter is half way there and can import the XBRL tags from HMRC and can output in XBRL however we need an iXBRL out put option.

We have placed a suggestion on the Microsoft Connect site. For those of you who do not know you can place product suggestions here and vote for them , those that get the most votes get sent to the development teams to be assessed and possibly included in future releases or feature packs.

So please take five minutes out of your day to go and vote for our suggestion which will ultimately benefit all UK Dynamics GP users.

The link to the site is https://connect.microsoft.com/dynamicssuggestions

If you can enter your details and then go to the Management Reporter for Dynamics ERP section

There you will find a suggestion entitled "iXBRL Reporting output required in Managment Reporter for HMRC online tax reports in UK - by Andyha11"

Please open this suggestion and then click on the green voting arrow (pointing upwards) to register your vote.

Thank you for your help with this, we can use the power of the Dynamics GP online community to get Microsoft to add the functionality we need into the product (after all that’s what it’s there for)

Thank you andrew.hall@touchstone.co.uk

Dynamics GP2010 and Word 2010 template documents Tips for Modifications

2010-06-30T16:19:00.000+01:00

We have done several Dynamics GP2010 upgrades now and I have had occasion to modify several of these templates. The manual for this functionality is actually part of the report writer manual for dynamics GP 2010 however it is not as simple as it seems.

Below are several tips to make life easier.

1. Do not use logos in the base report writer report. If you have a logo any modified fields will not come across to the word template.

2. Do not modify the existing Microsoft templates. Its hard to tell whether a table is nested within another table on the templates and it is vital to know this to be able to accurately place the required word bookmarks that determine how the template behaves. It is a lot easier to create your own template from scratch as you will know for certain how the word tables are structured on the format.

3. Avoid placing images in the header or footer that are not within a single cell table.

4. Print the base report writer report to an XML data file. You can then use this as a import file for the dynamics GP datasource for the word document should fields go missing.

5. Avoid the use of multiple additional headers and footers on the base report writer document (this can get messy) keep to Report headers, Body and report footer as much as possible.

6. Keep it simple

Any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP 2010 web services and Business Portal 5 installation

2010-05-13T15:02:00.002+01:00

Hi folks

I have spent the morning configuring sharepoint services, Dynamics GP 2010 web services etc. to install Business Portal 5.

One of the pre requisites is that Dynamics GP 2010 web services are installed before business portal 5. Having followed the wizard I was convinced that the Dynamics GP 2010 web services were installed , however the business portal 5 installation wizard could not see them.

The Business Portal 5 installation wizard suggests the URL for the Dynamics GP 2010 web services should be :

http://computername/DynamicsGPWebServices

However this was not working.

The install documentation suggests the URL for Dynamics GP 2010 Web services should include the TCP/IP port (the default for Dynamics GP 2010 Web Services being 48620) as well as the web services being called DynamicsGPService.

http://computername:48620/DynamicsGPService

This does not work either.

However if you combine the two using the port number from the Install guide and the naming convention from the wizard you get:

http://computername:48620/DynamicsGPWebServices

This does work and you can continue with your Business portal 5 installation for dynamics GP 2010.

If you have any questions please contact the helpdesk@touchstone.co.uk or my self andrew.hall@touchstone.co.uk

Searching on the New Microsoft Dynamics GP Forums

2010-05-11T11:35:00.001+01:00

Hi Folks

The old Dynamics community newsgroups are now being phased out and replaced with the new forums. For the full details on this please see David Musgrave's blog on the below link.

http://blogs.msdn.com/developingfordynamicsgp/archive/2010/05/11/microsoft-responds-to-the-evolution-of-communities.aspx

We have been using the new Microsoft Dynamics GP forums for a while now and have had a good experience with them so far however we have discovered that there is a slight issue with the search. The only way to get meaningful results from your search is to enclose your criteria in double quotes.

For example Management Reporter will not return anything however "Management Reporter" will.

So enclose any query in double quotes and it will save you a lot of frustration.

I have copied in the links to the Microsoft Dynamics GP forums below from David Musgrave's article.

So the time has come to stop using the old newsgroups and shift to using the public community forum or the partner forum, see links below:

Microsoft Dynamics GP Community Forum

Microsoft Dynamics GP Partner Forum

If you have any questions please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Increase efficiency over 90% with Dynamics GP 2010

2010-04-28T11:29:00.000+01:00

Several Touchstone clients were part of the Dynamics GP 2010 TAPs program. Central YMCA (a Touchstone Client) have completed a case study for Microsoft with their experiences of 2010.

In the case study central YMCA have seen a 90% increase in efficiency using Dynamics GP 2010.

You can down load the case study from:

http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?casestudyid=4000006953

Paul Smith from Central YMCA will be presenting at our Dynamics GP 2010 UK launch event at the London Chamber of Commerce on the 19th of May. There will also be presentations from Errol Schoenfish, Director Product Management, Microsoft Dynamics GP.

If your interested in Dynamics GP 2010 come along (you don’t have to be a Touchstone client). You can sign up below. Its a lot easier to get to than Thames Valley Park in Reading (Microsoft Campus), you could say its a more efficient use of your time and you will be able to see what efficiencies you could gain through dynamics GP 2010

www.touchstone.co.uk/gp2010launch

If you have any questions about Dynamics GP 2010 please contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Dynamics GP 2010 has now been released

2010-04-19T09:54:00.001+01:00

Dynamics GP 2010 has now been officially released by Microsoft. To find out more about this latest feature rich version of Dynamics GP come along to our Dynamics GP 2010 launch event on the 19th of May at the London Chamber of commerce.

www.touchstone.co.uk/gp2010launch

Returning Ole Notes File names in Dynamics GP

2010-04-16T11:25:00.000+01:00

Hi folks

Here is another tip from our tame Dex developer Jon, which I have written up as an article for us mere mortals. The below article should help you if you need to bring back an image from the OLE notes folder in Dynamics GP.

To start with you need to know how OLE notes get their file names. Well the file name is the hexadecimal version of the note index held in the Dynamics GP notes master table (SY03900).

Therefore to reference the file you are going to need to convert decimals to hexidecimals. The below function will allow you to do this.

udfConvertBase10NumberToAnyBase function:

CREATE FUNCTION udfConvertBase10NumberToAnyBase

( @iNumber INT,

@iNewBase INT,

@bitUppercaseOnly BIT = 0,

@bitNoNumbers BIT = 0) --1 to use only alphas

RETURNS VARCHAR(120)

AS

BEGIN

DECLARE @vUppers VARCHAR(26)

DECLARE @vLowers VARCHAR(26)

DECLARE @vNumbers VARCHAR(10)

SELECT @vUppers = 'ABCDEFGHIJKLMNOPQRSTUVWXYZ'

SELECT @vLowers = 'abcdefghijklmnopqrstuvwxyz'

SELECT @vNumbers= '0123456789'

DECLARE @vCharactersInBase VARCHAR(62) --Max possible of 10 digits, 26 upper, 26 lower

SELECT @vCharactersInBase = @vUppers --all options allow this

IF @bitNoNumbers = 0

BEGIN

SELECT @vCharactersInBase = @vNumbers + @vCharactersInBase

END

IF @bitUppercaseOnly = 0

BEGIN

SELECT @vCharactersInBase = @vCharactersInBase + @vLowers

END

--If caller requests a "base" size > number of characters in conversion-characters-set, return error

IF LEN(@vCharactersInBase) < @iNewBase

BEGIN

RETURN 'udfConvertBase10NumberToAnyBase - ERROR: Requested Base-size greater than available characters in @vCharactersInBase'

END

DECLARE @vNewNumber VARCHAR(120)

SELECT @vNewNumber = ''

-- Algorithm for generating equivalant number in the new "base":

-- 1) The orignial (base-10) number is continually divided by the new base until the product

-- of the old number divided by the base is zero (meaning the number is finally smaller than the new base).

-- 2) On each cycle (loop iteration), the remainder is added to the number, which is each digit of the new base.

WHILE @iNumber <> 0

BEGIN

SELECT @vNewNumber = SUBSTRING(@vCharactersInBase, (@iNumber % @iNewBase) + 1, 1) + @vNewNumber

SELECT @iNumber = @iNumber / @iNewBase

END --While

RETURN @vNewNumber

END –Procedure

So now we have a function that can convert the decimal to hexidecimal to obtain the file name.

To be able to use this we then need to include this function in a script

See Below:

Select noteindx, right(‘00000000’ + dbo.udfConvertBase10NumberToAnyBase(noteindx, 16, 0,0), 8) as filename from SY03900

You can now bring back the OLE note file.

If you have any questions contact helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

How to Use Microsoft Word mail merge to create a Dynamics GP import macro

2010-04-13T16:56:00.000+01:00

Hi folks as promised in the previous article, here are the steps to use Microsoft's Word mail merge to create an import macro for Dynamics GP. The below will work for any repetative task in Dynamics GP.

Before starting this you will need an excel spread sheet with the values you wish to update. See below example of content.

Segmentid Number description

Segment1 100 Administrator

Segment2 100 Manager

Segment3 100 Tickets

Segment4 100 revenue

Open the window you wish to update. In this case Tools setup financial segment

Then go to Tools Macro Record

Give the macro a name e.g. Segment.

Save macro (the macro is now recording and all your key strokes will be recorded).

Enter one set of data you wish to update e.g. Segment ID , number and description.

Then select save.

Then go to Tools  macro  stop record

Go to where you saved the macro (.mac file) and right click and open Macro with word. You should have text similar to below example.

# DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field ' Description ' , 'Administration'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL

Now in the word document goto mailings and start the mail merge wizard.

Select directory as document type and got to next starting document

Select current document as starting document and go to next select recipients.

Use an existing list and the browse option to browse out to your spread sheet with the values you wish to update.

Do not go to the next stage of the wizard.

Highlight the value between the ‘’ on the type to line of the script. In the above example this would be the value 100, make sure you highlight just the value and not the’’ either side.

Now go to the insert merge field option from the tool bar, it should give you the column headers from your spread sheet (in this case we want number).

The field should now look like this '«Number»'

In the script.

Now repeat the process with the other type to fields in the script you wish to update e.g. description

TypeTo field Description , '«description»’

Now go next , next next in the wizard and save to a new document. You should end up with a script similar to below.

# DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Administrator’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL # DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Manager’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL # DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Tickets’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL # DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'revenue’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL

Before this script will work we need to remove the repeated line DEXVERSION=10.0.193.0 2 2

This should only appear once at the start of the script so the script now looks like the below.

# DEXVERSION=10.0.193.0 2 2

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Administrator’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL #

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Manager’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL #

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'Tickets’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL #

ActivateWindow dictionary 'default' form 'GL_Segment_Maintenance' window 'GL_Segment_Maintenance'

MoveTo field 'Segment ID'

TypeTo field 'Segment ID' , '100'

MoveTo field Description

TypeTo field Description , 'revenue’

MoveTo field 'Save Button'

ClickHit field 'Save Button'

ActivateWindow dictionary 'default' form sheLL window sheLL

Now save this document as a .mac file

Go into dynamics, Open the window you wish to update. In this case Tools setup financial segment

Then go to Tools Macro Play and select the .mac file you just created.

The macro should now run and update the data for you

any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

Hurry hurry hurry Dynamics GP 2010 UK launch event filling up fast.

2010-04-12T12:37:00.000+01:00

Just a quick reminder our Dynamics GP 2010 UK launch event is on the 19th May at the London chamber of commerce. There has been a huge amount of interest in this event so sign up below and find out what Dynamics GP 2010 is all about.

Follow the below link to find out more

www.touchstone.co.uk/gp2010launch

Country codes in Dynamics GP Input macro (VAT Reporting Requirement)

2010-04-12T11:19:00.000+01:00

Hi folks

We have had a couple of enquiries on the help desk recently about setting up country codes for Dynamics GP as there are now extra reporting restrictions in place for VAT when trading in Europe.

Unfortunately you cannot import the country codes into Dynamics GP using integration manager, however do not despair, it can be done quite simply with a macro. The advantage of doing this is that you can ensure the country codes are the same in each company.

You can simply record yourself entering one country code, save the macro, then use words mail merge function to rewrite the macro multiple times with all the appropriate codes. Save as a new macro and run (I’ll cover this in detail in another blog).

Alternatively you can use the Dynamics GP macro I prepared earlier in best Blue Peter fashion.

Simply copy out the code below and paste into a notepad document. Then save the note pad document with a .mac extension rather than .txt. You can then pick this up as a macro in Dynamics GP.

You will need to have the ‘VAT Country Code Maintenance window’ open and this macro was written on version 10. The path is tools>>setup>>company>>countrycodes.

The Macro can be run from tools>>macro>>play.

Any questions please contact the helpdesk@touchstone.co.uk or myself andrew.hall@touchstone.co.uk

MACRO:

# DEXVERSION=10.0.324.0 2 2

CheckActiveWin dictionary 'default' form 'VAT_Country_Code_Maintenance' window 'VAT Country Code Maintenance'

TypeTo field 'Country Code' , 'AF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'AFGHANISTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AX'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ÅLAND ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ALBANIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ALGERIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'AMERICAN SAMOA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ANDORRA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ANGOLA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ANGUILLA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AQ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ANTARCTICA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ANTIGUA AND BARBUDA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ARGENTINA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ARMENIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ARUBA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'AUSTRALIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'AUSTRIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'AZERBAIJAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BAHAMAS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BAHRAIN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BANGLADESH'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BB'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BARBADOS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BELARUS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BELGIUM'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BELIZE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BJ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BENIN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BERMUDA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BHUTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BOLIVIA, PLURINATIONAL STATE OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BOSNIA AND HERZEGOVINA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BOTSWANA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BOUVET ISLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BRAZIL'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BRITISH INDIAN OCEAN TERRITORY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BRUNEI DARUSSALAM'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BULGARIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BURKINA FASO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'BURUNDI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CAMBODIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CAMEROON'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CANADA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CAPE VERDE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CAYMAN ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CENTRAL AFRICAN REPUBLIC'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CHAD'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CHILE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CHINA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CX'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CHRISTMAS ISLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'COCOS (KEELING) ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'COLOMBIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'COMOROS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CONGO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CONGO, THE DEMOCRATIC REPUBLIC OF THE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'COOK ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'COSTA RICA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CÔTE D IVOIRE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CROATIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CUBA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CYPRUS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'CZECH REPUBLIC'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'DENMARK'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DJ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'DJIBOUTI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'DOMINICA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'DOMINICAN REPUBLIC'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'EC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ECUADOR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'EG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'EGYPT'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'EL SALVADOR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GQ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'EQUATORIAL GUINEA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ER'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ERITREA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'EE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ESTONIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ET'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ETHIOPIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FALKLAND ISLANDS (MALVINAS)'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FAROE ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FJ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FIJI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FINLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FRANCE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FRENCH GUIANA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FRENCH POLYNESIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'FRENCH SOUTHERN TERRITORIES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GABON'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GAMBIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GEORGIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'DE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GERMANY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GHANA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GIBRALTAR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GREECE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GREENLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GRENADA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GP'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUADELOUPE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUAM'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUATEMALA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUERNSEY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUINEA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUINEA-BISSAU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'GUYANA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'HAITI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'HEARD ISLAND AND MCDONALD ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'HONDURAS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'HONG KONG'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'HU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'HUNGARY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ICELAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'INDIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ID'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'INDONESIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'IRAN, ISLAMIC REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IQ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'IRAQ'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'IRELAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ISLE OF MAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ISRAEL'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'IT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ITALY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'JM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'JAMAICA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'JP'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'JAPAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'JE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'JERSEY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'JO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'JORDAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KAZAKHSTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KENYA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KIRIBATI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KP'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KOREA, DEMOCRATIC PEOPLES REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KOREA, REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KUWAIT'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'KYRGYZSTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LAO PEOPLES DEMOCRATIC REPUBLIC'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LATVIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LB'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LEBANON'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LESOTHO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LIBERIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LIBYAN ARAB JAMAHIRIYA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LIECHTENSTEIN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LITHUANIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'LUXEMBOURG'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MACAO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MADAGASCAR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MALAWI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MALAYSIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MALDIVES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ML'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MALI'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MALTA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MARSHALL ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MQ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MARTINIQUE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MAURITANIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MAURITIUS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'YT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MAYOTTE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MX'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MEXICO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'FM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MICRONESIA, FEDERATED STATES OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MOLDOVA, REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MONACO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MONGOLIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ME'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MONTENEGRO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MONTSERRAT'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MOROCCO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MOZAMBIQUE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'MYANMAR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NAMIBIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NAURU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NP'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NEPAL'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NETHERLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NETHERLANDS ANTILLES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NEW CALEDONIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NEW ZEALAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NICARAGUA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NIGER'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NIGERIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NIUE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NORFOLK ISLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MP'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NORTHERN MARIANA ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'NO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'NORWAY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'OM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'OMAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PAKISTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PALAU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PALESTINIAN TERRITORY, OCCUPIED'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PANAMA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PAPUA NEW GUINEA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PARAGUAY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PERU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PHILIPPINES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PITCAIRN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'POLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PORTUGAL'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'PUERTO RICO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'QA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'QATAR'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'RE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'RÉUNION'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'RO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ROMANIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'RU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'RUSSIAN FEDERATION'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'RW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'RWANDA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'BL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT BARTHÉLEMY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT HELENA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'KN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT KITTS AND NEVIS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT LUCIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'MF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT MARTIN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'PM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT PIERRE AND MIQUELON'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAINT VINCENT AND THE GRENADINES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'WS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAMOA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAN MARINO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ST'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAO TOME AND PRINCIPE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SAUDI ARABIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SENEGAL'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'RS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SERBIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SEYCHELLES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SIERRA LEONE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SINGAPORE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SLOVAKIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SLOVENIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SB'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SOLOMON ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SOMALIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ZA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SOUTH AFRICA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GS'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ES'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SPAIN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'LK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SRI LANKA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SD'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SUDAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SURINAME'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SJ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SVALBARD AND JAN MAYEN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SWAZILAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SWEDEN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'CH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SWITZERLAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'SY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'SYRIAN ARAB REPUBLIC'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TAIWAN, PROVINCE OF CHINA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TJ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TAJIKISTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TANZANIA, UNITED REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'THAILAND'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TL'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TIMOR-LESTE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TOGO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TK'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TOKELAU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TO'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TONGA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TT'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TRINIDAD AND TOBAGO'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TUNISIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TR'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TURKEY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TURKMENISTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TC'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TURKS AND CAICOS ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'TV'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'TUVALU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'UG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UGANDA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'UA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UKRAINE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'AE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UNITED ARAB EMIRATES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'GB'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UNITED KINGDOM'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'US'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UNITED STATES'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'UM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UNITED STATES MINOR OUTLYING ISLANDS'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'UY'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'URUGUAY'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'UZ'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'UZBEKISTAN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VU'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VANUATU'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VA'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VATICAN CITY STATE (HOLY SEE)'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VENEZUELA, BOLIVARIAN REPUBLIC OF'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VN'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VIET NAM'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VG'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VIRGIN ISLANDS, BRITISH'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'VI'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'VIRGIN ISLANDS, U.S.'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'WF'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'WALLIS AND FUTUNA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'EH'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'WESTERN SAHARA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'YE'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'YEMEN'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ZM'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ZAMBIA'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

TypeTo field 'Country Code' , 'ZW'

MoveTo field 'Country Code Description'

TypeTo field 'Country Code Description' , 'ZIMBABWE'

MoveTo field 'Save Button'

ClickHit field 'Save Button'

SQL script to find PM transactions with missing apply details in Dynamics GP

2010-04-12T10:39:00.000+01:00

Hi Folks

Every now and then you get posting interruptions in Dynamics GP at exactly the wrong time. Normally the Batch recovery routine under tools>routines>Batch Recovery, picks these up. However sometimes this is not the case and you then need to determine what state your data is in within the Dynamics GP product.

The below script is designed to help in these circumstances. It is run against the Dynamics GP company database and is designed to find those payables transactions with missing apply details.

I would recommend running this script if you have found a PM transaction with missing apply details to ascertain the extent of the problem.

If you do have a posting interruption or if you find that you do have missing apply info please contact the helpdesk@touchstone.co.uk and we can investigate further.

If you have any questions about the script etc please feel free to contact me andrew.hall@touchstone.co.uk

Here is the script:

/* Before running this query go to query on the menu bar and select results in text */

/* This query is designed to find open transactions that have missing apply info Open & the info is

in history

The first part of the script selects transactions from

the PM20000 which have apply info in the PM10200 */

select b.VCHRNMBR, b.VENDORID

into #temp1

from PM10200 a, PM20000 b

where b.DOCNUMBR = a.APTODCNM

and a.VENDORID = b.VENDORID

go

/* The second part of the script selects transactions from

the PM20000 which should have apply info but they did not appear in the

results of the first script */

select VCHRNMBR, VENDORID

into #temp2

from PM20000

where DOCAMNT >CURTRXAM

and CURTRXAM>'0.00000'

and VCHRNMBR NOT IN

(select VCHRNMBR

from #temp1)

order by VENDORID

go

/* The third part of the script selects transactions from

the results of the second script which have apply info in the

PM30300 History table */

select a.VCHRNMBR, a.VENDORID

into #temp3

from #temp2 a, PM30300 b

where a.VENDORID = b.VENDORID

and a.VCHRNMBR = b.VCHRNMBR

go

/* The Fourth part of the script selects transactions from

the PM20000 that do not appear in the results of the third part or the first part

( open apply info and History apply info) */

select VCHRNMBR, VENDORID, DOCNUMBR

into #temp4

from PM20000

where DOCAMNT >CURTRXAM

and CURTRXAM>'0.00000'

and VCHRNMBR NOT IN

(select VCHRNMBR

from #temp3)

and VCHRNMBR NOT IN

(select VCHRNMBR

from #temp1)

order by VENDORID

go

/* This part of the script displays the results*/

print 'Transactions from PM20000 missing apply info in PM10200 & PM30300'

select * from #temp4

go

Year End comes before 2010 (year end procedures)

2010-03-12T16:10:00.002Z

If you read the blogs at the moment they are all full of the wonders of 2010, however here in the UK a lot of us will be experiencing our year ends in April before 2010 is released.

Therefore I thought I would devote a little time towards some practical advice for year end.

Once you have got year end out of the way you may then want to turn your sights to Dynamics GP 2010, and if that’s the case may I suggest that you might like to come along to our Dynamics GP 2010 launch event on May the 19th, follow the below link to sign up:

www.touchstone.co.uk/gp2010launch

Back to Year End

The below is a simple checklist you can follow to complete year end, you may notice we are rather fond of doing backups.

1. Do a back up! (told you)

2. Make sure you have enough free disk space on the server. It will need to be a least the size of the GL20000 table but double that would be preferable (It’s going to move all the closed years transactions from the Open table to the History Table so it will need some room).

3. Make sure you run the year end close for all other modules first before the GL (Once you have done the GL you cannot go back and do the others).

Complete year end for each module in the following order:

Inventory

Receivables Management

Payables Management

Fixed Assets

General Ledger

4. Post your final adjusting entries for GL.

5. Print account list to verify posting type (Reports-Financial-Accounts-All Accounts). Incorrectly marked account types is one of the major causes of year end problems. You can also check the posting types using smartlists and the accounts option under Financial.

http://intouchdynamicsgp.blogspot.com/2009/09/no-1-cause-of-year-end-issues.html

If the account's balance is brought forward at the end of year, it should be set up as a Balance Sheet Posting Type.

If the account's balance will be closed to a retained earnings account at the end of the year, it should be set up as a Profit and Loss Posting Type.

6. Close the last period of the financial year.

7. Run the file maintenance routines on financial series i.e. Check links.

8. Make sure Maintain History for Accounts and Transactions is marked in Setup>>Financial>>General Ledger . (If you want to keep history records.)

9. Do a second backup !

10. Print a final detailed Trial Balance, Reports>>Financial>>Trial Balance (I would send this one to file and keep it somewhere safe).

11. Print final Financial Statements.

12. Setup a new fiscal year (Setup>>Company>>Financial Periods)

13. Make sure the Retained earnings account is populated(Routines>>Financial>>Year end closing).

14. Using the Year-End Closing window, enter the starting journal entry number that will be used as the first journal entry number in the new year or accept the default.

15. Close the year, use the Close Year button in the Year-End Closing window .

If the progress window seems to hang at 50%, don't reboot. As long as your hard drive is processing, let it continue. Also make sure you do not click it twice, if you do it we close the next year as well.

16. Close any periods for the new year you do not want people posting to.

17. Adjust budget figures for the new year (remembering to budget for your upgrade to 2010) and print financial statements.

18. Do a third and final backup!

19. Put your feet up and have a well deserved cup of tea

And that is that if you have any questions please contact andrew.hall@touchstone.co.uk or helpdesk@touchstone.co.uk

Dynamics GP 2010 UK launch Event

2010-03-09T17:22:00.000Z

On May the 19th we are having our Dynamics GP 2010 UK launch event.

This will be held at the London Chamber of Commerce.

As well as an introduction to the benefits, new features and functionality, we will be hearing from one of our clients that took part in the early adopters program from Microsoft on their experiences with Dynamics GP 2010.
Microsoft will also be presenting at the event and our consultants that assisted Microsoft in the early adopters program will be on hand to quiz about their findings.
The helpdesk will also be there and we will be happy to talk about the results of our in-house testing with Dynamics GP 2010.

To sign up or for more info follow the below link:

Register today to ensure your place: www.touchstone.co.uk/gp2010launch

How to edit VBA when the client only has customization site licence

2010-02-05T11:06:00.000Z

Well you learn something new every day and today our tame Dex developer is sat next to me in the office (some say he writes code in his sleep, others say he has dexterity tattooed on his heart, all we know is, he is called Jon) so picking up all sorts of things.

This one however is really simple and very useful. Often we will develop modifications for clients on our systems then import these using customization maintenance onto the client systems. This means that the client does not need to have modifier etc, just the customization site licence to run the mods.

However if the VBA on the mods need editing you need to export it back out onto your system to do this then re import it.

Well here is a simple tip. Export the modification out into a package file. Then open the package file up with notepad.

In the VBA code add in the word STOP. This command will tell the VBA to debug.

Re import the package file then open the screen or run the report. The STOP in the VBA code will then open the VBA window and allow you to edit the VBA.

Next handy tip DONT CLOSE THE VBA WINDOW if you do you will have to go through all this again to open the window so leave it open till you have finished and remember to remove the STOP from the code.

Any question contact andrew.hall@touchstone.co.uk

Comparing tables In Dynamics (GP)

2010-02-02T10:01:00.001Z

While we are on the subject of SQL tables, we often need to find records that are in one table but not another. This usually happens after there has been some kind of interruption during a posting process.

This can be done fairly easily with a nested SQL query.

The first thing you need to do is determine which tables you need to look in (Take a look at our previous article on Integration Basics). It is also worth remembering the process flow through Dynamics( GP) (Work>Open>History).

Work tables will start with a 1 after the two alphabetic characters that represent the module/series.

Open tables start with a 2

And you guessed it, history tables start with a 3.

Keys tables etc. start with a 0.

Once you have determined which tables you need to determine which field value you are going to compare. As a rule of thumb, its best to use primary key constraints. You can determine the primary key by using sp_helpindex TABLENAME (Replace TABLENAME with the table i.e. GL10000).

Also it worth remembering that vouchernumber is a unique reference in payables and document number is a unique reference in receivables.

Journal number is unique in GL but only for that year as it is possible to start again with journal numbers after year end in Dynamics (GP) if you so require.

So we now have our tables and which field we are going to compare.

Now we create a nested SQL query

Select VCHRNMBR from PM20000

where VCHRNMBR not in

( Select VCHRNMBR from PM30200)

go

The above statement will return all the records from the PM20000 where they are not in the PM30200. If you wanted to return records in both just drop the not from the statement.

It gets slightly more complex if you are comparing to the master keys table as the Vouchernumber is the control number in this table so I would select into a temp table first and change the field name during the process to match that of the other table. The temptable can be called anything you like as long as it is unique and starts with a # to designate it as a temp table. Mine is #TCLCONTROLNUMB. The temp table will remain in existence as long as the query window is open. Once you close the query the temp table is removed.

Select VCHRNMBR as CNTRLNUM into #TCLCONTROLNUMB from PM20000

go

Select CNTRLNUM from #TCLCONTROLNUMB

where CNTRLNUM not in

(Select CNTRLNUM from PM00400)

go

any questions please contact andrew.hall@touchstone.co.uk

Integrating to Dynamics (GP) The Basics

2010-02-01T15:58:00.000Z

Its only Monday and I have already been asked by two clients about integer values in tables and the best way to integrate to them without using Integration Manager. Add to this the couple of calls I had last week on the same subject I thought it would be worthy of a blog article.

The first question that gets asked is “what is the best way of integrating?”.

Well that depends on what you’re integrating. If you’re integrating static data (addresses, debtors, accounts) then SSIS and other such tools are fine. However if you are integrating transactional data I would suggest it is best to use a tool that will use the business logic of Dynamics (GP) and thus prevent you pumping rubbish into the system. These tools will usually use eConnect to access that business logic, tools like Scribe, Integration Manager and Smartconnect can all use eConnect.

The next question tends to be “what tables do I need to integrate to?”

Well there are several ways of finding this out and a combination of them will provide you with the best results.

• Install the SDK from additional products on your Dynamics (GP) CD. This gives excellent help on integrations and will advise you on tables and the values required for integer fields etc.

• Use the Direct to table import. Open the window in which you would normally enter the information manually, then in that window select Tools > Integrate > Table Import. This will then display a list of tables that this window accesses and therefore would be updated if you entered information.

• Resource descriptions. These can be found under Tools > Resource descriptions > table definitions. Here you can find all the tables within Dynamics (GP) and their structure. It will also show you their physical name (The one used in SQL) and their display name as well as their technical name (Usually the one used in error messages).

Using a combination of these you should be able to get all the info you need. This is a very basic look at integrations and does not cover all the options, it is more of a pointer in the right direction.

And always integrate into a test database first when you’re developing your integration.

If you have any questions please contact helpdesk@touchstone.co.uk

FRx SP11 and 0 budget amounts

2010-01-28T14:02:00.000Z

We have now discovered a slight difference between sp11 and sp10 and it revolves around the way they deal with column layouts and the use of the Base-1 feature in the column.

It would appear that if you use the base-1, base-2, base-3 etc. feature in the period column and this takes you into the prior year it will look into the prior year for the budget when the year column is set to base (previously in SP10 it did not do this and the year remained constant).

For example if you run a report for January 2010, the period column is set to base-1 and the year is base. It should go back one period which is December but as the year is set to base you would expect data in the budget column for December 2010. What we are getting is zero.

This is because the base-1 in the period is now changing the year as well and trying to display data from December 2009. As there is no data for December 2009 in this budget (yearly budget) it is returning zero.

The workaround is to hardcode the periods 1 through to 12 rather than using the base-1 functionality. We do have this logged with Microsoft at the moment, however a lot of people have just completed their year ends or are in the process of doing so, which means this issue is likely to be more obvious as people change the years in which they are processing.

Dynamics (GP) First Aid (MR MUM)

2010-01-28T11:56:00.000Z

I have spent the last three days on a St John’s ambulance First Aid at Work course and I am now fully qualified to deal with those all too common work place wounds, you know the kind of thing, QWERTY shaped bruises on the forehead etc.

Anyway the First Aid procedures started me thinking that this is very similar to what we do on the helpdesk when trouble shooting an issue with Dynamics.

Within First Aid there are loads of handy acronyms to help you remember what you’re looking for and what takes priority. For instance there is DR ABC. This stands for Danger, Response, Airway, Breathing and Circulation. I thought that we could benefit from something similar to make sure all the bases are covered when investigating a Dynamics issue and after several minutes of deep thought I have come up with MR MUM.

M = Multiple Instance: Does it happen all the time, is this the first time , has it happened before?

R = Replicate: Can you replicate it?

M = Machine: Is it machine specific, does it only happen on one workstation, does it happen on the server?

U = User: Is it user specific, does it happen for one user or all users or just users in a specific role or users in a specific Company?

M = Modifications: Are the screens or reports modified , does it happen if you take away access and use the unmodified objects is there VBA attached?

The answers to the above should provide the consultant with a firm basis to start trouble shooting the rest of the issue, in fact, if the answers to these questions were given at the point of case logging the resolution may present itself straight away, it would certainly speed up the triage stage of a support call.

If anyone has any question please feel free to contact me andrew.hall@touchstone.co.uk

FRX SP11 we are happy with it now.

2010-01-22T16:18:00.000Z

The code for FRx sp11 has been re released and we have tested this in house. We are happy to report it does what it says on the packet and we are now happy for our clients to install this service pack.

any questions please contact helpdesk@touchstone.co.uk

Dynamics (GP) 2010 early findings

2010-01-21T13:31:00.000Z

Hi folks.

We have a couple of clients on the early adopters program from Microsoft for Dynamics (GP) 2010.

We have hit our first issue, this only effects non U.S. installs and is a re occurrence of an issue from version 10.

The problem is installing Business portal. It won’t install on non U.S. regional settings. You need to change your regional settings to U.S., install BP and then change them back to U.K. or where ever else you are in the world. This was a problem in BP4 for version 10 and its still there in BP5 for version 2010 (beta).

Any questions please contact helpdesk@touchstone.co.uk

How to Create SQL Scripts in Integration Manager without hardcoding the database

2010-01-19T16:41:00.000Z

Here is a handy bit of code. Have you ever wanted to run a sql script in Integration manager after the task completes but you don't want to hard code the company database so you can use it against multiple companies?

Well here is the code to do this (in version 10), in the script window within Integration manager start off by setting the ADODB connection.

set MyCon = CreateObject("ADODB.Connection")

Then use the connection string to bring back the inter company ID

MyCon.Connectionstring = "database=" + GPConnection.GPConnInterCompanyID

Open your connection

GPConnection.Open(MyCon)

You can then construct your SQL statement, the below is an update statement

updatecommand = "update PM00200 "
updatecommand = updatecommand & " set PHNUMBR1 = 'xxxxx',"
updatecommand = updatecommand & " PHNUMBR2 = 'xxxxx',"
updatecommand = updatecommand & " PHONE3 = 'xxxx',"
updatecommand = updatecommand & " FAXNUMBR = 'xxxx'"

Then close the record set and exercute the command

recset = MyCon.Execute(updatecommand )

This becomes a very powerful tool when you combine it with before scripts which will enable you to fill out blank fields with place holders etc and then remove the place holders after the integration completes.

Any questions contact helpdesk@touchstone.co.uk

Top 5 New features Dynamics (GP) 2010 (Beta release)

2010-01-18T11:46:00.000Z

The beta release of Dynamics (GP) 2010 is here.

Our Dynamics (GP) Product Manager is currently in the process of testing this new code so its to early to give you our findings as yet. However I thought I would take this opportunity to wet your appetites with some of the New features that caught our attention.

2010 is rich in new features so we thought we would do our top 5 and as is traditional with these count downs we will start at 5 and work our way up to 1.

So coming in at number 5

5.Collections Management: View unposted cash amounts

This has been one of those annoying little over sites for credit controllers , well from version 2010 unposted cash amounts are now displayed in the collections main window.

Another new entry (quite literally) at number 4

4.Receivables Management: Enter negative cash receipts

You can now decrease a deposit by entering a negative cash receipt. This shows as a deposit with a negative amount (we have had a few support cases in the past that would have been easier to resolve with this functionality).

A simple piece of functionality at number 3 , however it is one that will make a lot of people happy.

3.Exclude inactive accounts/customers/creditors/sales people etc. from lookups

If your bogged down in active accounts etc. this should make lookups and data entry so much quicker.

At number 2, the word template comes of age

2.Word templates

Predefined word templates come with 2010 from purchase orders to invoices, I have included the list below of the Report writer reports that can now be done with word templates. Good bye to those clunky report writer reports.

Report Writer report name:
SOP Blank History Options Quote Form
SOP Blank History Quote Form
SOP Blank Options Quote Form
SOP Blank Quote Form
SOP Blank History Options Order Form
SOP Blank History Order Form
SOP Blank Options Order Form
SOP Blank Order Form
SOP Blank History Options Invoice Form
SOP Blank History Invoice Form
SOP Blank Options Invoice Form
SOP Blank Invoice Form
SOP Blank Packing Slip Form
RM Statement on Blank Paper
MC Statement Blank Form
Receivables Sales/Invoices
Receivables Debit Memos
Receivables Finance Charges
Receivables Service/Repairs
Receivables Warranties
Receivables Credit Memo
Receivables Returns
POP Purchase Order Blank Form
POP History Purchase Order Blank Form
POP Purchase Order Rollup Blank Form
POP History Purchase Order Rollup Blank Form
Payable Invoices
Payable Finance Charges
Payable Miscellaneous Charges
Payable Credit Memo
Payable Returns
Check Remittance

and we have saved the best till last top of the new features list is:

1. E-mail Functionality

The new email functionality allows you to embed documents into the body of an email or send as attachments. You can send single documents , batches or multiple document types using lists.

The following document types can be sent in an email and you have the choice of HTML, XPS, PDF or DOCx formats.

Documents:
Sales quote

Receivables finance charges
Sales order

Receivables warranty
Sales fulfillment order

Receivables service/repair
Sales invoice

Standard purchase order
Receivables invoice

Blanket purchase order
Receivables return

Drop-ship purchase order
Receivables debit memo

Vendor remittances
Receivables credit memo

If this has wet your appetite then keep watching this blog as we will be posting the initial findings of our testing on 2010 soon.

any questions please contact helpdesk@touchstone.co.uk

2010 EU Tax changes/update

2009-12-21T12:22:00.001Z

As any of you who trade in Europe should know there are tax changes being brought in for 2010.

Simply put if you are trading/providing services in Europe (The EU) then you need to submit a sales listing along side your VAT100 report.

Microsoft have now released extra code to allow you to do this in the VAT daybook and Advanced intrastat modules.

You can use the below link to download the code for versions 9 and 10 :

https://mbs.microsoft.com/customersource/downloads/releases/MDGP10_9_VAT2010

If you have any questions please contact helpdesk@touchstone.co.uk

Bug In FRx SP11 core code (Please do not install)

2009-12-21T09:32:00.000Z

Service Pack 11 was recently pulled due to a core FRx bug found. The last update from Microsoft's Development is that it should be available for release in 4 weeks.
To roll back to SP9 you can follow KB 861724 "How to remove a Service Pack for FRx". The link is provided below. If you can not access the link please contact helpdesk@touchstone.co.uk

https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;861724

FRX and Windows 7

2009-12-16T10:00:00.000Z

Hi Folks, a quick update to the whole windows 7 compatibility status. FRx 6.7 is now compatible with windows 7 as long as the recently released Service Pack 11 is installed.

for more information on SP11 for FRx 6.7 please contact the helpdesk@touchstone.co.uk

Conference High Lights

2009-10-19T11:11:00.000+01:00

As most of you are aware we had our client conference last week, a great chance to meet and greet some of our clients and catch up on the latest technologies and the Dynamics (GP) road map.

I think that most people would agree that one of the high lights was the sneak preview of some of the Dynamics (GP) version 11 features and the integrations with office 2010.
Our thanks to Tom and Will from Microsoft for these insights and especially to Will for the mind blowing insight into project Gemini.
Imagine being able to filter cut pivot millions of rows in excel full of GP data without any effect on performance, all achieved through a simple add in to excel. It will change the face of BI as we know it. As Will mentioned there are loads of demos of it out there on you tube so here is a link to a few.
http://www.youtube.com/user/geminute#p/u

Also the end would appear to be in sight for report writer, as we were shown the new word 2010 report templates allowing you to create professional looking reports in word linked to your dynamics Data and with unlimited numbers of templates per report type ( you could have 20 different invoice layouts if you wanted).

All the presentations from the day are available on request from the contact page of our web site
http://www.touchstone.co.uk/contact_us.aspx

And I can not close off this blog without mentioning the lunch which was fantastic, a full on carvery with roast beef Yorkshire pudding , lamb , turkey all the trimmings and desserts to die for, fantastic.

Dynamics (GP) v8 is no more. Microsoft stopped support yesterday

2009-10-14T09:45:00.000+01:00

For those of you still on Microsoft business solutions (Great Plains) version 8. Microsoft finished support for this version yesterday.

We however have not , if you are one of our clients and you are on version 8 or lower we will still support you. However you need to be aware that we will not be able to escalate issues to Microsoft for these versions or produce code fixes if required.

If you would like look into upgrading you to the latest release please contact helpdesk@touchstone.co.uk

Integration Manager Dynamics (GP) V10 not pulling through fields

2009-10-13T15:02:00.000+01:00

Hi folks , this one has cropped up in several support cases this week.

In version 10 Integration manager data is sometimes not being pulled through. This is usually when the destination field is down several sub levels in destination mapping.

A good example of this is the email field that is held under internet settings when integrating a debtor or creditor record.

We have found that although it is already mapped you just need to go into destination mapping and re add the source field. it will now bring through the data.

This is not immediately obvious when troubleshooting as the source field appears correctly mapped to start with.

If you have any questions please contact helpdesk@touchstone.co.uk

Dynamics (GP) eConnect, web services and ISO Currency codes

2009-10-09T16:25:00.000+01:00

When you set up econnect to use with web services you need to have all the ISO codes for your individual currencies in Dynamics (GP) populated.

These are setup on the currency maintenance window in Dynamics (GP).

There are two internationally recognised codes for each currency. An alphabetic and a numeric code. Please be aware you need to use the alphabetic code as the web services will not pass/recognise the numeric ones.

The below ISO website has the list of internationally recognised codes.

http://www.iso.org/iso/support/faqs/faqs_widely_used_standards/widely_used_standards_other/currency_codes/currency_codes_list-1.htm

If you have any questions contact helpdesk@touchstone.co.uk

Hurry Hurry hurry, Touchstone's Dynamics Client Conference is next week.

2009-10-09T15:35:00.000+01:00

Our annual Dynamics Customer conference is next Thursday, its a great opportunity to catch up on the Dynamics product range and see what extra value you can get out of your Dynamics (GP) system.

Use the below link to sign up.

http://www.touchstone.co.uk/DynamicsConference2009/

Dynamics (GP) v10, unsupported printers and small fonts.

2009-10-09T15:00:00.000+01:00

We have had a couple of cases recently where after an upgrade to Dynamics (GP) v10 , the standard reports all print out in very small fonts.
This usually happens if you are using an unsupported printer. You can request a list of supported printers from helpdesk@touchstone.co.uk .

There are a couple of workarounds you can use for this.

The first is to try different printer drivers for a supported printer from the same range. For example HP printer drivers a pretty well interchangeable. Select the nearest model number off of the supported printer list and down load the driver from the manufacturer’s website and try these.
Nine times out of ten this will work.

We have recently discovered there is a second option you can try. In the Dex.ini file on each workstation add in the following printer commands.

FontCourier New=Lucida Console
Tolerance=-1
MinMilHeight=180

This forces the printer to take on the above font settings, however a quick word of warning, it does not work with all printers and print drivers as they don’t all support these settings and it may not alter the output of the report (In which case you will need to experiment with drivers).

If you have any questions contact helpdesk@touchstone.co.uk

Report writer, calculations, functions and those pesky global fields in Dynamics (GP)

2009-10-09T11:38:00.000+01:00

Anyone who has tried to add a global field (such as company name or companyID) into a function used in a calculated field within report writer for Dynamics (GP), has probably become very frustrated.
For some reason Report writer handles global fields differently. To make matters worse several of these fields are non string values and have integer data types so can not be used within concatenation functions.

Well there is a way round this and it is in essence very simple.

If we take the global field of CompanyID for example. This has a data type of INT5 (integer) and so can not be used in a concatenation in a calculated field. Therefore you need to use the INT_STR function in the calculated field to change its data type to string. However because it is a global field it won’t let you do this.

So to get round this simply create a calculated field with a result type of Integer and insert the global field of companyID. This has effectively created a calculated field with the same value as the global field.

Now because it is a Calculated field Report writer will treat it normally. This means you can now use the INT_STR function but instead of using the global field you use your new calculated field.

This technique will work for all those global fields and will allow you to include them in functions within report writer and with this technique you can add global fields into functions such as STRIP, CAT and INT_STR within Dynamics (GP).

Thanks to Jon Eastman (Touchstone Consultant) who came up with this handy hint.

If you have any questions please contact helpdesk@touchstone.co.uk

Requested registry access is not allowed Error installing on Vista or Windows server 2008

2009-10-06T13:29:00.000+01:00

As I am sure most of you are aware Security on the Vista and server 2008 operating systems is fundamentality different from xp and others that have gone before. This can cause issues when installing Dynamics (GP) products and code onto these environments.

Usually you will get an error message along the lines of “Requested registry access is not allowed” or permission denied error. When this happens you have two options.

The First option is to disable the User Account Control (UAC) feature for the duration of the install on the machine.

1.Click Start, type accounts in the Start Search box, and then click User Accounts in the Programs list.

2. Click Turn User Account Control on or off. If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

3. Click to clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.

4. Restart the computer.

You can now install the code on the machine. Make sure that once you have installed the code , reset the UAC options and restart the machine again.

The Second option (and my preferred one) is to do it from the command line.

1. Open the command prompt (The command prompt is located in the Accessories group) as a user who has administrative permissions on the local computer. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

2. Type the directory of the location where you copied the .msp or install file for the service pack, and then press ENTER.

3. To run the installation, type the following command, and then press ENTER:
Msiexec /p /l*v C:\MSPErrorlog.txt

Note In the command in step 3, is a placeholder for the name of the .msp or install file.

If you have any questions please contact helpdesk@touchstone.co.uk

FRx Forecaster 7 , Roaming Profiles and Amazing Disappearing Database connections

2009-10-02T09:52:00.000+01:00

This is a strange one and is not documented anywhere , in fact when we talked to Microsoft about this they had only seen it once before , so we thought it deserving of a blog post as this may save someone else a lot of time and effort.
This issue happens when you have Forecaster 7 installed in an environment using roaming profiles , in the case of our client they were also on terminal services but the same could be said for citrix.

The problem is, if you create connections to forecaster databases on a machine using roaming profiles, then when you log out and log back in to the machine they are gone and need to be recreated again.

The reason for this is that Forecaster 7 stores the connections on a user basis in an ini file by default in c:\Users\%username%\AppData\Local\Microsoft\Forecaster\ . This as you can see from the file path, is the users local folder not their roaming profile folder. So when the user logs back on, because roaming profiles are used the system checks the roaming profile folder and low and behold the connection details are not there.
There is no official resolution for this from Microsoft. The only option would appear to be to update the roaming profile from the local one. Our clients IT team came up with their own resolution and have set at bat file to run on login copying the details from the local folder to the roaming profile.

So in summary this is a fairly unique set of circumstances and will not affect the majority of clients however if you are using roaming profiles with forecaster you will need to consider this. Our thanks to Daniel Merchant (IT at our client’s site) who pin pointed this issue.

If you have any questions please send them to helpdesk@touchstone.co.uk

Quick Lookup Ctrl L

2009-09-30T10:39:00.000+01:00

I have just got out of a WEBEX session with one of our clients. For those of you who have not had the pleasure of WEBEX yet this is a desktop streaming technology we use to take over your workstation to assist with support call resolution.
Any way whilst looking up a debtor I used the quick look up short cut key stroke and the end user had never seen this before and was impressed with the speed and ease of use. It occurred to me that this is something that no one tells you about, every one uses the smartlist functionality but not the hot keys etc.

So here it is. In any of the look up fields start typing the first couple of characters of the ID then press Ctrl L and it will take you to the first match in Alphabetical order.

Its a simple as that, some times its the little things that make a difference.

I have published a whole list of hot key , keystroke short cuts on our online knowledge base which can be accessed by Touchstone clients.
http://support1.touchstone.co.uk/c360.Portal/index.aspx

any questions please contact helpdesk@touchstone.co.uk

A quick reminder V8 support is about to run out 13th October 2009

2009-09-28T09:42:00.000+01:00

This is a Quick reminder for those of you still on version 8.

Mainstream support for Microsoft Business Solutions – Great Plains 8.0 will end October 13, 2009 per the Microsoft Support Lifecycle Policy. This means that any GP 8.0 issues logged after Oct 13 will not be supported by Microsoft.

You can still log these issues with the Touchstone helpdesk@touchstone.co.uk as we will support our clients on whatever version of Dynamics (GP) they are on. However you do need to be aware that should we need to escalate an issue to microsoft or the code requires a bug fix for a previously undiscovered bug, then the only option will be to upgrade to a supported version.

If you are tinking of upgrading then there is an audit document available on our online knowledge base http://support1.touchstone.co.uk/c360.Portal/index.aspx or you can ask the helpdesk@touchstone.co.uk or your Account Manager.

The Audit document contains sizing information about database sizes , numbers of modified reports and server specifications, all of which are needed to give an acurate quote on an upgrade.

If you would like some help filling it in then the helpdesk@touchstone.co.uk will be happy to assist.

Once it is completed send it tous and we can provide you with a quote for the upgrade.

If you have any questions please feel free to contact helpdesk@touchstone.co.uk

All Change on 15% Tax Again January 2010

2009-09-21T13:48:00.000+01:00

Tax Changes in Dynamics (GP)

This is a quick re working of the advice we put together last time the VAT changed from 17.5 to 15%. This change is being reversed in January 2010 so now would be a good time to start thinking about how this might effect your systems. The changes in VAT where originally set out in the Chancellors PBR on the 24th November 2008. Because of the nature of Tax calculations in Dynamics (GP) this article is intended purely as a Guide and you will need to choose the appropriate actions for your circumstances.

Note: We have kept these notes fairly generic as we have clients on several different versions, however in version 10 where we give a path to Setup>company etc these are found under Tools> setup > Company

Tax Details

Originally we advised that everyone will need to set up a new set of tax details to replace the 17.5% details currently used. We recommended that you did not simply change the rate on your existing detail as this could cause you reporting problems and issues when trying to post back.

To set up a new Tax detail you need to go to Setup>Company>Tax details
You needed to set up a minimum of two details, one for sales and one for purchasing. This needed to be done in each of your companies.

If you followed this advice you should now still have your original 17.5% tax codes to which you can now revert in January.

Tax Schedule

Here you have Two choices.

Option 1: We advised that you could retain the existing Tax schedule and simply remove the 17.5% detail from this schedule. Then add the new 15% detail to the schedule and to the ALL Sales and ALL purchasing schedules that you have setup on the company. Schedules can be accessed from setup>Company>Tax Schedules. This has the advantage of not then needing to change any setup on classes , debtors, creditors , items or projects. Simply put where ever the old 17.5% detail appears in a schedule on its own (No other details)you will need to replace it with the 15% detail and wherever it appears with other details you will need to add in the 15% detail. If you took this option then it is simply a matter of swapping the details back.

Option 2: is to setup two new Tax schedule (one sales one purchasing). Again this is done through setup>company>Tax schedules. Once these have been crested you will also need to add the 15% Tax detail to the existing All sales and All Purchasing tax schedules. However if you create a new schedule you will need to change all the card records within dynamics that have a schedule attached. These are Debtor maintenance, Creditor Maintenance, Item maintenance, Cards project categories, SOP setup options default tax schedules , and the appropriate Classes for all of the above , this will also need to be done in each company. If you took this option then you will need re allocate the ols schedules to classes etc and role down the changes.

VAT Reporting and Vat input and Output codes

Originally we advised, If you are using the standard Vat reporting within Dynamics (GP) this all works off of Tax detail ID so if you have created a new detail there should be no issues. However some of our clients are reporting directly off of the GL account code. If this is the case you will need to setup two new GL accounts for the new tax rate (input and output accounts)and add these accounts into the new details you have created.
Setup new accounts under cards >Financial>Accounts remember it will need to be a balance sheet account.
The Account can be associated with the Tax detail Setup>Company>Tax detail id.
You may wish to do this even if not reporting directly of the GL. If you followed these instructions you will need to change the account code back.

Sales Order Processing

SOP will cause some issues as any outstanding transactions created this week will retain their 15% tax detail when transferred to invoice (This is not a problem for POP as this recalculates). The Tax setup options for SOP are on the options Tab of the Sales Order setup window found under Setup>Sales> Sales order processing. To get round this issue you will need to go back and change the tax on the order to the new rate before transferring to invoice.

Nolan’s Advanced VAT

We have spoken to Nolan’s and they are issuing no specific advise however like us they are advising to create new details rather than update existing ones. These are found in the same place as the standard Tax details as these are alternate windows.
Note: if using Nolan’s advanced VAT you can set an account to be Taxable, in which case a tax schedule is held against the account as well as an individual Tax ID , these will need to be changed as well where they are using the 15% tax detail. These are accessed under cards>financial>Account .

Project Accounting

Depending on how your projects are setup , you may need to change the tax schedules on Cards> Projects> cost category.

Further Advice from the Government

For further detailed information and HMRC guidance about the original change, please visit the HMRC Website at http://www.hmrc.gov.uk/pbr2008/

Advice has yet to be issued on the upcoming change in January 2010

No advice has been issued by Microsoft at this time , but when they do we will update you.

If you have any questions please contact the helpdesk@touchstone.co.uk

No 1 Cause of year end issues

2009-09-18T17:42:00.001+01:00

Its been a funny old day on the helpdesk today , every other call seemed to be about year end. So this is probably the opportune time to post a little reminder that the No 1 cause of year end issues is incorrectly marked posting types on accounts.

When you run year end all your P&L accounts are closed to retained earnings and your Balance sheet accounts produce a BBF (Balance brought forward) entry. If the accounts are incorrectly marked under cards>financial>accounts with the wrong posting type , then they will produce the wrong type of entry.

So Top tip for the day is make sure these are correct , this is easily done using smartlists.

If you have any questions please contact the helpdesk@touchstone.co.uk

How to Reconcile RM to GL when you have multiple RM control accounts

2009-09-16T12:14:00.000+01:00

This situation presents us with a unique set of circumstances as you can not restrict the Receivables aged trial balance by account. It can be restricted by payment priority and class so with some forethought and planning you could have debtor classes set up that use a specific control account or something similar along the lines of payment priority. If you have not done this or you think some transactions may have been miss posted then using smartlists would be your next best thing.

In Smartlists you can create a report for the receivables transactions based on the system date range and then create a report for GL (account transactions) for the system date range. This way, you can compare when the information was physically entered in the system (even with a different document date between modules). If one of the modules has the transaction posted and the other is missing, you can determine if the transactions were posted with a different date in GL than in receivables.

Within smartlists, open up the receivables transaction option. Add the column Posted Date. This column stores the date from your computer of when the document was physically entered in receivables. Even if the document date was for the previous year, the posted date stores the date of when you physically entered it. You can compare the posted date to the posting date (holds the document date) or the document date as well. You can narrow your search by entering the posted date since you were last in balance. This will tell you all of the transactions that were entered in receivables since then and you can compare your GL report to that and see if one module is missing the transaction, has a different document date, or a wrong amount as well(possibly the batch was edited in GL before it was posted). To restrict this report to just one of your multiple control accounts you will need to add in the Account receivable Account Number field and then restrict your report by this in the search option. This is where you would put in the value of the Control account you wish to reconcile.

Next, you will want to open the account transaction option within smartlists. Add the columns Originating Posted Date and Originating Document Number. This stores the posted date (system date) from the originating module. Even if you change the batch date, this stores the date of when it was entered. You can compare the originating posted date to the trx date (document date) in account transactions as well to see if they vary from what your receivables transaction report returns. You may also want to add the Originating Document Number and Originating Master ID (debtor id) to this report, that way you can tick transactions off by using the document number instead of looking for amounts. This time to restrict the report to the specific control account you will need to add in the Account Number field to the search criteria and add your Control account number here.

These reports will give you a good guideline on trying to narrow down when something was entered, but there could be other possibilities that could be a cause such as a posting interruption (but this may have updated one module and not the other so you can compare what's missing), receivables history was removed (which only effects receivables and not GL).

The reporting can be automated further by using excel functionality. Both reports can be out put to excel from smartlists. If they are put into the same workbook on different sheets , you can then use the V lookup functionality to compare the Document number on the RM report to the originating document number on the GL report thus highlighting differences and giving you a place to start.

If you are interested in a certain sub set of transactions on the RM such as the unapplied/outstanding transactions then the RM side of the report can be restricted further by adding in the Current Trx Amount field to Columns. If the value of this field is greater than 0.00000 then there is an amount outstanding on the document and so this can be added to the search criteria.

If you have any questions then please contact the helpdesk@touchstone.co.uk

How to split out One RMA to multiple RTV with multiple vendors

2009-09-11T10:27:00.000+01:00

This functionality is easy to find in version 10 of Dynamics (GP). Ordinarily if you create multiple RTVs (Return to vendors) from a single RMA (Return material Authorisation) then the system will try and create one RTV for just one of the vendors.

However if you go to Tools > Setup > Project > service setup and go to the Returns button. On the RTV side you will find a consolidated check box. Un Check this box and the system will then allow multiple RTV's to separate Vendors.

In Version 9 however the check box is not there in the setup options. Instead it is on the window that appears when you create the RTV from the RMA. When you click process this box appears at the bottom of the screen and is very easily missed. Un check this to allow multiple RTVs to multiple Vendors.

It seems simple but that check box is easily missed (Rhonda at Microsoft pointed it out to me, thank you).

If you have any questions, please contact the helpdesk@touchstone.co.uk

Touchstone Group's Microsoft Dynamics Client Conference 2009 - 15th October - Registration is now open!

2009-09-09T17:44:00.000+01:00

Yes its that time of year again where you actually get to meet some of our helpdesk staff. If you ever wondered what we look like when your talking to us on the phone now is your chance to find out. There will be several of us at the conference.

Also it is an excellent opportunity to meet with some of your peers in the industry and get up to date on the latest software releases and version 11. We will also be looking at modules etc that can save you money during these tough economic times, such as spend control and several electronic document solutions (yes if those Royal mail strikes affected your business then emailing your remittance advices may be the way to go).

For more information and to sign up, follow the below link to the Conference micro site.

www.touchstone.co.uk/DynamicsConference2009

Integration Manager and Windows 7

2009-09-09T08:53:00.000+01:00

For those of you who like to keep up with the latest releases of Microsoft operating systems , you may be contemplating a move to Windows 7.

As Mentioned in earlier posts this is compatible with version 10 of Dynamics (GP) however not all third parties and other modules have been tested at this time. One of the most notable of these is Integration Manager. Currently this has not been tested with version 10 and is unsupported on the windows 7 platform.

If the Situation changes we will let you know.

If in doubt about supported operating systems please log a call with our helpdesk

helpdesk@touchstone.co.uk

Stuck Batches

2009-09-07T11:57:00.000+01:00

Well its Monday morning, the summer holidays are over and we have had to sit on London’s orbital car park (other wise known as the M25) to get to work.
One of the first things we do on a Monday morning is to go through those emails and support cases that have been logged outside of office hours over the weekend. This morning there were three cases all to do with batches being stuck. Therefore I thought a blog on the subject might be of some use.

Since the batch recovery tool was introduced back in version 6 the instances of stuck batches have dramatically reduced , however we still get those annoying loops once in a while where you pick up your batch from batch recovery and it sends you straight back to batch recovery. When this happens your only option is to reset the batch in SQL.
Below is an extract from an article on our online knowledge base that tells you how to deal with this.

If you are one of our clients, you can sign yourself up to our customer portal to access this via the support section of our website (http://www.touchstone.co.uk) or simply ask the helpdesk and they will set you up.

Batches should be freed through batch recovery, these steps should only be taken if this is not possible.

1. Make sure you have a current backup of your company database.

2. Go to the SQL Query tool located in your Microsoft SQL Server Program Group.

3. Under DB select the company database you are working with, i.e., TWO is the lesson company.

4. Enter the following query in the query window;UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 WHERE BACHNUMB='XXX'(where XXX is the batch number of the batch you are trying to post).

5. Under DB select the DYNAMICS database and enter the following query;DELETE SY00800 WHERE BACHNUMB='XXX'(where XXX is the batch number of the batch you are trying to post).

6. Verify the accuracy of the transactions.

7. Verify that you can edit and post the batches.

What should I back up?

2009-09-02T15:20:00.000+01:00

This is not as obvious a question as it would seem.
We are all aware that you will need to backup your Dynamics and Company databases however there are other files which store unique set-up information required to run your dynamics system. Below I have listed these areas:

Sysdata This is the file/folder that stores all your FRx rows, columns and trees along with the FRx registration information.

IM.mdb If you are using Integration Manager, this is the access database that will store all the queries etc. that you set-up within Integration Manager.

Reports.dic This is where any reports that you modify will be stored; you should have an up-to-date copy of this somewhere accessible. In the event that this becomes corrupted you can then replace it.

Forms.dic This is the same as the reports.dic but contains modified windows.

Any files with.dic or .vba extensions These are the dictionaries for any modifications to the third party products and any VBA modifications

Letters folder, if you are using the letter writing wizard then all your templates are held here. This could be local or on the server.

OLE notes. This folder should be on the server and will contain any attachments that you have added to notes in Dynamics.

For further advice please contact the Touchstone helpdesk.

helpdesk@touchstone.co.uk

Dynamics (GP) 10 Service Pack 4

2009-09-02T13:58:00.000+01:00

Service Pack 4 for version 10 has now been released and is available for download from Microsoft’s customersource web site. Please do not install this service pack yet as we have not completed in house testing on it at this time. Salim Umerji (our Product Manager for Dynamics (GP)) has scheduled time for this testing and will be updating this blog once testing has been completed.

If you have any questions regarding this service pack please contact the helpdesk
helpdesk@touchstone.co.uk

Windows 7 and Dynamics (GP)

2009-09-02T13:33:00.000+01:00

Well there is good news and there is bad news .

The good news is Windows 7 is compatible with version 10 of Dynamics (GP).

The bad news is that there are no plans to make it backwards compatible with earlier versions and no testing has been done at this point with FRX or any 3rd party add ons .

Please contact the helpdesk before upgrading to windows 7

helpdesk@touchstone.co.uk