Emailing POs using new GP2010 word templates

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:

1. The purchase order number from the PO Document list table
2. Section additional header 1 based on the above field
3. 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

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

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.

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

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.

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

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