With the release of Microsoft Dynamics GP 2010 SP3, MSFT GP development team has fixed one of the nagging bugs which got introduced in Microsoft Dynamics GP 2010 R2.
The following posts would explain what exactly that issue is:
Error When Switching Back To Microsoft Dynamics GP From Report Writer (Ian Grieve)
Unhandled script exception: Illegal address for field ‘[Not Found]’ in script ‘Unregister_Triggers’ (Mariano Gomez)
Rest assured that this bug is now fixed with the release of Gp 2010 SP3.
I had earlier posted about this ongoing series; not long back. To know what it is exactly, read it here: Report Writer Series.
The new post on this series discusses about how to create custom report writer reports.
Report Writer has been considered by most of the clients as static and bland reporting tool, due to it’s look & feel and it’s rigidity in terms of modifying the reports.
But, Report Writer is an amazing reporting tool, if only people know how it’s structured technically and how to bend it for our requirements. I am not certainly talking about customers. It’s the consultants’ responsibility to convince customers by demonstrating the power of Report Writer.
Over at Kuntz Consulting blog, series of posts are to be read to understand Report Writer as a tool and how to use it for our betterment. Following are the posts that are already been posted:
- Report Writer Demystified – Part 1 – Dictionaries & Launch Files
- Report Writer Demystified – Part 2 – Other Considerations
- Report Writer Series – Formatting Text
- Report Writer Series – Don’t Settle for Ugly Reports – Part 1
- Report Writer Series – Don’t Settle for Ugly Reports – Part 2
- Report Writer Series – Toolbox Tips
- Report Writer Series – Drawing Options Tips
- Report Writer Series – Sections
And it’s only going to get more on this series.
Worth reading for all those who would want to know about this silent performer, that is Report Writer.
Mariano’s latest post explains how to add more comment lines to POP Purchase Order report. The idea is to split the comment text into 80 characters sized fields and then displaying it on separate report sections. I leave you here so you could refer to this awesome piece of post from Mariano. It’s a step-by-step guide on how to do this.
David, way back in 2011, demonstrated a similar approach on his post about adding more comment lines on SOP Documents. It’s worth to remind that post now.
Those who want to know how to add/use Extender Fields on a Report Writer report, Mark’s Weekly Dynamic post, Extender and Report Writer walks us thru’ simple steps with a real time scenario.
There are also links to relevant KB articles which will form the base for your task.
The first thing a Dex Developer would do once he/she learns Dex programming is to start becoming curious and write their own functions / procedures to meet the requirements.
I am certainly not against it and I myself started off my programming career like that. But we must also understand that when we have in-built functions that can do what we want, we don’t have to lose our time in recreating the same logic.
RW_DateToString function would certainly save us lot of time. And it does have almost all much used formats to display a Date on the report.
David details this function in his article: Display Dates in Any Format On Report.
Such a weird issue, but since it’s said to be known, we can’t do much about it. But David gives us an alternate option to tackle this.
Read it here: Currency values returned by VBA to a report are multiplied by 10 or 100.
Must read for Developers.