32766 maximum row export to excel from smartlists in Dynamics GP2013

Hi Folks

This issue was causing us some concern and we could not find any reference to it on any forum or partnersource so now we have an answer, I thought I would put it on the blog so the rest of the community was aware and maybe save some people some serious head scratching.

The issue is this, when exporting to excel from Dynamics GP 2013 smartlists it was crashing out when reaching row 32766.

All the DEX developers out there are now going “oh , Oh , 32766, that’s the maximum integer value in Dex” and you would be right. Here in lies the problem, the smartlist code in Dynamics GP2013 has been rewritten to speed it up. It used to do it line by line but it is now casting to an integer.

The folks at Microsoft Dynamics GP Technical Support have been great helping us with this (thanks folks you're all stars) and it has now been written up as a change request and sent to development.

I’ll update the blog when we get a date, however in the mean time you just need to be aware this limitation exists.

Cheque (check for US readers) Remittance word template not emailing from Dynamics GP

Here is an interesting set of circumstances one of my team came across. The word template for the cheque (check) remittance in Dynamics GP 2010 sp3 would print but not email. We had the vendor id field from the pmRemittanceTemp file on the report layout but the word template was still not emailing.

The clue to the issue was that the exception report was not showing the supplier id’s we were expecting to be emailed.

In the end it was traced to the fact that the report writer version of the report had had the “Payment Number” additional footer removed. Once this was replaced the templates emailed fine.

So to sum up , to be able to email the Cheque (Check) Remittance word template you must retain the “Payment number” additional footer.

Value cannot be null. Parameter name: title Value when switching navigation pages in GP2013

Hi Folks

I have been fairly quiet for a while on the blogging front however with the roll out of GP2013 there is  now a whole raft of new features and the odd issue that have prompted me to start typing.

We have experienced an issue with navigation pages and according to the forums a few other people out there have come across the same. In GP2013 when switching to certain navigation pages the user may get an error message saying "Value cannot be null. Parameter name: title Value", you may then be forced to crash out of GP (this does not seem to happen every time).

According to the forum post, Microsoft were tentatively looking at putting a fix in SP1. However SP1 has been released and the fix did not make it in in time. All is not lost though there are a couple of workarounds available.

·         You can run the following SQL script, this will temporarily solve the issue, however it may re occur and you will need to run the script again.

 

Delete DYNAMICS..SY07140 where CMDDICTID = 1

·         On the Splash/Home page of the module in which this occurs, if you click into the 'Customise this page' link you will see a blank module which is ticked. Un-tick the mystery option, and the error will go away. However, the blank option remains in the list...(and the error won’t always allow you to get to the customise this page option).

Microsoft are working on a fix and I’ll update this blog when we know a release date.

UPDATE.....UPDATE......UPDATE......

Since publishing this article it would now appear that the fix has been included in SP1 (Conflicting information from two different engineers). I have confirmed this with our TSAM , full details can be obtained from the below Knowledgebase article:


http://support.microsoft.com/kb/2843273

Management reporter not warning me to save.

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

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

Management reporter migration wizard (FRx)

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.

Management reporter and segment names

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.