The Dynamics GP Blogster's best articles of 2012

It's that time of the year again! Time to say goodbye to the outgoing year, 2012, and receive the new one, 2013, making all sort of resolutions that we never seem to be able to achieve and with good measure, since most of us are simply consumed with the daily grind that lifting our heads up to take a breather and see the forest from the trees seems difficult and sometimes downright impossible.

2012 however was a very good year and gave me tons of stuff to write about. In retrospect, 3 conferences, 2 virtual conferences, the release of Microsoft Dynamics GP 2013 and the Web Client are simply a subset of the activities that allowed me to write some really cool stuff that you expressed through your comments to enjoy. Without further due, here is a list of the "best articles of 2012" written on this site (in no particular order):

1. Microsoft Dynamics Convergence 2012 Houston. Convergence Houston in March of 2012 was a very cool experience and probably one that I will never forget as I was able to meet up with my good friend David Musgrave and his wife, Jennifer. I also had the opportunity to share some time with some of my customers in attendance. As always, the good part is meeting tons of people and the thrill of presenting.

2. Microsoft Dynamics GP Technical Airlift 2012. In the realm of cool, the Technical Airlift in Fargo, North Dakota was a very awesome conference, but also marked the first time I presented without my compadre, David Musgrave. The Tech Airlift also demanded tons of prep work and was built upon cooperation between Microsoft and GPUG's GPPC and featured a record number of partners in attendance. I also liked the fact that I met up with some of my fellow MVPs.

3. GPUG Summit 2012 Seattle. Seattle has this aroma of coffee mixed with sea all over the city and I have to say the GPUG summit was a very charming conference, with lots of topics for the attending crowd. Seattle, Seattle...

4. Windows 8 and the Microsoft Dynamics GP Web Client Series. Okay, so I confess. I was a nuisance to the Escalation Engineering team testing the Web Client. You see, the Web Client was not supposed to even be working on Windows 8 as a compatible installation platform, but after months of annoying I had my way with this. The best part though was working with the team of Aaron Donat and Jason Lech and understanding the nuances of the deployment process of GP Web Client. Thanks guys for putting up with me and for making this happen.

5. Adding Customer Item User Defined fields to SOP Invoice. I love the Support Debugging Tool and how it can make live easier for things that seem unconceivable. How about this cool article on getting customer item user defined fields onto the SOP invoice? Well, I have to say I had tons of fun getting this to work.

6. How to add a "Cover Letter" page to a Microsoft Dynamics GP Word Template document. Life is not complete without a Word Template article. I hope to keep these coming in 2013 since Word Templates are essential to Web Client.

7. Resizing SmartList panes with the Support Debugging Tool. Now, did I say I love the Support Debugging Tool? David Musgrave leverages some obscure Dex functions to make SmartList a dream tool to use.

8. Leveraging Custom Links to track carrier shipments in Sales Order Processing. You know, I am always amazed at how underutilized GP seems to be sometimes, but my duty as a blogger and consultant is to expose these underutilized features to the community.

9. Microsoft Dynamics GP Add-In for Microsoft Word not enabling despite several attempts to install. I had a number of clients come to me with this issue. Upon doing more research, I realized it was a community wide problem and I had to do something about it.

10. Adding more comment lines to POP Purchase Orders. Building on a previous article written by David Musgrave for SOP, I thought I would show how to accomplish the same in POP - it was all worth it as the community gave praises for the solution.

101 articles throughout the year are simple quite a bit of stuff written. I just hope I can keep the good stuff coming. Happy New Year!

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 "Feature of the Day" - Week 15 Digest

Week 14 saw no activity from the Inside Microsoft Dynamics GP team, since all the relevant players were out at the GPUG Summit 2012 Seattle event - read GPUG Summit 2012 Seattle - Wrap Up! to find out more.

Last week, the Inside Microsoft Dynamics GP team, however, went nuts (probably as a result of jet lag) with Pam and Jay mixing things up a bit in renaming the "Features of the Day" to "Feature when Pam or Jay Reveals it". The truth is, these two are a bit unpredictable, so I will simply continue to call this - and in the interest of keeping your sanity and mines in check - Feature of the Day.

Feature When Pam or Jay Reveals It: Reprint Payables Management Remittance

Now you can reprint remittances from Payables Payment Zoom window

Original article: Feature When Pam or Jay Reveals It: Reprint Payables Management Remittance
Link to presentation: GP2013 13716_Reprint PM Remit FOD.ppsx
Learning script: N/A

Feature When Pam or Jay Reveals It: RMA Sales Order Consolidate

Consolidate SOP Order Document now an option in Service Setup

Items entered on the RMA...

... are consolidated on the Order in SOP

Original article: Feature When Pam or Jay Reveals It: RMA Sales Order Consolidate
Link to presentation: GP2013 FOD RMA SOP Consolidate.ppsx
Learning script: N/A

Feature When Pam or Jay Reveals It: Search by Contract in Revenue Recognition

Search by Contract Number now an option in Contract Revenue Recognition

Original article: Feature When Pam or Jay Reveals It: Search by Contract in Revenue Recognition
Link to presentation: GP2013 FOD Search by Contract in RR.ppsx
Learning script: N/A

Feature When Pam or Jay Reveals It: Shipping Address Overrides Remain In Service Call

Original article: Feature When Pam or Jay Reveals It: Shipping Address Overrides Remain In Service Call
Link to presentation: GP2013 FOD Shipping Address Overrides Remain in Service Call.ppsx
Learning script: N/A

Feature When Pam or Jay Reveals It: Copy AA Trx Dimensions for POP, SOP, GL

Now you can copy analytical accounting info across the board

Original article: Feature When Pam or Jay Reveals It: Copy AA Trx Dimensions for POP, SOP, GL
Link to presentation: GP2013 12245 Copy AA Trx Dimension Info FOD.ppsx
Learning script: N/A

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 "Feature of the Day" - Week 8 Digest

Welcome to Microsoft Dynamics GP 2013 "Feature of the Day" Week 8 Digest!

As you read this article, I will be putting the final touches (well, the stuff I am wearing to be precise) to my suitcase to travel to Fargo, North Dakota for the Microsoft Dynamics GP Technical Airlift 2012 hosted by GPUG's GP Partner Connections (GPPC). Much of the Technical Airlift content will focus on Microsoft Dynamics GP 2013: how to sell the product, install it, customize it, and support it - doesn't get any better than that!

For those of you not attending the conference, the "Feature of the Day" series, published by Inside Microsoft Dynamics GP and summarized here on a weekly basis as a digest article, is the best way to keep building your Microsoft Dynamics GP 2013 knowledge, in addition to the Technical Airlift blog articles I will be releasing all this week, live from the conference.

Without further due, here are the articles topics for last week.

Feature of the Day: Multi-Tenant

Web Services installation: Multi-tenant Configuration window

Original article: Feature of the Day: Multi-Tenant
Link to presentation: GP2013 FOD - Multi-tenant GP Web Services.ppsx
Learning script: GP2013 Multi-tenant GP Web Services Learning Script

Feature of the Day: Fixed Assets to General Ledger

Fixed Assets General Ledger Posting window

Fixed Assets Batch Inquiry window

Original article: Feature of the Day: Fixed Assets to General Ledger
Link to presentation: GP2013 FOD Fixed Assets Batches.ppsx
Learning script: N/A

Feature of the Day: Multi-User Editing in Returns Management

RMA Entry/Update window displaying multi-user capabilities

Original article: Feature of the Day: Multi-User Editing in Returns Management
Link to presentation: GP2013 FOD Multi-user Editing Allowed in RMA Entry.pptx *
Learning script: N/A

*NOTE: This will download an actual PowerPoint presentation to your hard drive.

Feature of the Day: Paycode History Edit and Payroll Check Enhancements

Payroll Setup Options window

Employee Paycode History window

Original article: Feature of the Day: Paycode History Edit and Payroll Check Enhancements
Link to presentation: GP2013 FOD PaycodeHistEdit_PRCheckEnhance.ppsx
Learning script: N/A

So far, we have a total of 38 features in 8 weeks. That's not bad, considering this release introduces hundreds of enhancements and new features.
Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 "Feature of the Day" - Week 6 Digest

Six weeks! Can you believe it? And so far 30 new features in Microsoft Dynamics GP 2013. The features have ranged across the board: payables, receivables, SOP, POP, inventory, system manager, you name it! Without further due, here are the features for Week 6 digest.


Feature of the Day: Requisition List

Requisitions Navigation List in HR & Payroll

Original article: Feature of the Day: Requisition List
Link to presentation: GP2013 FOD_Requisition_List.ppsx
Learning script: N/A

Feature of the Day: Consolidated Invoicing

Sales Bulk Confirmation window

Original article: Feature of the Day: Consolidated Invoicing
Link to presentation: GP2013 FOD Consolidated Invoicing.ppsx
Learning script: GP2013 Consolidated Invoicing Learning Script

Feature of the Day: Reconcile Bank Reconciliation to General Ledger
 

Reconcile Bank Rec to GL

Original article: Feature of the Day: Reconcile Bank Reconciliation to General Ledger
Link to presentation: GP2013 FOD Reconcile BR to GL.ppsx
Learning script: GP2013 Reconcile BR to GL Learning Script


Feature of the Day: 64-Bit Microsoft Office Compatibility
 

Configure Email Settings and Office 64-bit Compatibility

Original article: Feature of the Day: 64-Bit Microsoft Office Compatibility
Link to presentation: GP2013 FOD_64-Bit Office Compatible.ppsx
Learning script: N/A

Feature of the Day: Intercompany Asset Transfer

Fixed Assets IC Transfer window

Original article: Feature of the Day: Intercompany Asset Transfer
Link to presentation: GP2013 FOD Intercompany Asset Transfer.ppsx
Learning script: N/A

As you can tell, the Product Management team and Dynamics GP developers have been hard at work making things happen. I just can't wait to see the final product all put together.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

How to add a "Cover Letter" page to a Microsoft Dynamics GP Word Template document

I wrote an article almost a year ago showing a simple technique to add a Terms and Conditions page to a Microsoft Dynamics GP Word Template document. You can read more about this here:

How to add a "Terms and Conditions" page to a Microsoft Dynamics GP Word Template document

Just recently, I received a comment on the article, where the poster was asking how to use the same techniques outlined to add a Cover Page to an invoice document, so I figure, after playing with the idea for a bit, that I would post the steps to accomplish this too.

All steps - up to step 3 - are the same, except, you probably would want to give this template an appropriate name. I will continue with step 4 as it applies to this article.

4. Position your cursor immediately above the company address information and add 2 single line tables. Add one table first, then create additional separation with the company information by pressing enter on your keyboard a couple times. Move up a line or so, and add another singly line table as shown below.

2 single line tables added

5. In the first single line table, add your Cover Page content.

Content added to the first single line table

6. Highlight the second single line table, then click on the Paragraph expansion button under the Home ribbon to open the options window. Click on the Line and Page Breaks tab and mark the Page Breaks Before check mark. Click Ok to continue.

Paragraph options for Page Break

7. This will now have the desired effect, by sending the first table with the Cover Page content to the first page of the document.

Cover page plus invoice page

8. The rest are some cosmetics... you can highlight each table and chose to remove the borders from each, which will give your document the look you are hoping to achieve.

Word Templates are always fun to play around with, especially because every single piece of information must be displayed within a content control - in this case a table. So it makes for some cool puzzles.

If you have resolved this same problem in a different way, I would love to hear from you. Please add your comments to this article. Also, keep in mind that I have tested this with limited data, so there's always a chance something might not work.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Microsoft Dynamics GP 2013 "Feature of the Day" - Week 5 Digest

Week 5 of the "Feature of the Day" series over at Inside Microsoft Dynamics GP is a mix bag of pleasant surprises: improvements in Sales Order Processing, Accounts Receivable, Human Resources/Payroll, and the Dexterity Runtime Engine, you could easily see how keeping track of all these things at once could drive anyone to the loony bin. As usual, this is where I come in by compiling all these features in one place for your delight.

Feature of the Day: Relate-Link Items for Suggested Sales

Two new windows: Suggest Sales Item Entry and Suggest Sales Item Maintenance

Original article: Feature of the Day: Relate-Link Items for Suggested Sales
Link to presentation: GP2013 Relate-Link Items for Suggested Sales.ppsx
Learning script: N/A

Feature of the Day: Cetification, Licensing, and Training Management

CLTM now allows to delete history (password protected) and rows

Orginal article: Feature of the Day: Cetification, Licensing, and Training Management
Link to presentation: GP2013 13915_CLTM_History FOD.ppsx
Learning script: N/A

Feature of the Day: Multicurrency Apply in RM Cash Receipts Entry

Multicurrency cash receipts can now be applied on the fly to invoices

Original article: Feature of the Day: Multicurrency Apply in RM Cash Receipts Entry
Link to presentation: GP2013 11800_MC Apply FOD.ppsx
Learning script: N/A

Feature of the Day: Select Printer at time of Print

Select Printer at Print Time

Original article: Feature of the Day: Select Printer at time of Print
Link to presentation: GP2013 13715_Select_Printer FOD.ppsx
Learning script: N/A

NOTE: It was just about darn time!

Feature of the Day: Deduction in Arrears Templates

Mandatory Arrears and Arrears Template Setup windows

Original article: Feature of the Day: Deduction in Arrears Templates
Link to presentation: GP2013 Deduction in Arrears Templates FOD.ppsx
Learning script: N/A

In all fairness, while they were no learning scripts, the presentations available acted very well as such. Congrats are in order for the Microsoft Dynamics GP Product Management team.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Leveraging Custom Links to track carrier shipments in Sales Order Processing

You know, I believe I will forward this to MVP Frank Hamelly for his next session at the upcoming GPUG Summit Seattle 2012, "13 MORE Classic, Underused Features in GP".

And now that I did the plug in for Frank's session...

This week I have a chance to review one of those truly underutilized features in Microsoft Dynamics GP, this time, as a result of some quality control work I am performing at one of our projects going live in 2 weeks.

My customer, a specialty food and fine chocolates distributor here in the Washington D.C. area needed to provide his customer service staff with the ability to see package delivery status when products leave any of the 5 warehouses around the country. To make matters more interesting, they are currently using Savant Software's Shipping Manifest module coupled with Savant Software's Warehouse Management System, both of which are integrated to Microsoft Dynamics GP. When orders are shipped from the Shipping Manifest solution, product tracking numbers are returned to the order document in Microsoft Dynamics GP.

Tracking Numbers on the Sales User-Defined Fields Entry window

My customer uses the four major delivery carriers: UPS, DHL, FedEx, USPS, and Ontrac.

We used Microsoft Dynamics GP Custom Links feature to provide the package tracking capabilities required.

Custom Link Setup

To setup a link to the Fedex tracking site, you select the Prompt to which you want to associate the link, in this case the "Tracking Number" prompt. You will then provide a prompt to display for the link, "FedEx Tracking". Next, you will want establish the field value for which the prompt will be displayed, in this case we want to display the Fedex Tracking prompt when the associated shipping method is FEDEX GROUND. Finally, we need the URL for the FedEx tracking website and need to pass in the tracking number string as a parameter to the URL. This is accomplished with the "%1" string substitution moniker at the end of the URL.

The result is shown below:

Tracking Number Custom Link

When the link is selected, the user is directed to the FedEx tracking site where information is displayed about the tracking number selected.

The following are tracking sites URLs for each of the major carriers, with the corresponding string substitution parameter for the tracking number:

DHL
http://www.dhl.com/content/g0/en/express/tracking.shtml?brand=DHL&AWB=%1

FedEx
http://fedex.com/Tracking?action=track&tracknumber_list=%1

UPS
http://wwwapps.ups.com/etracking/tracking.cgi?submit=Track&InquiryNumber1=%1&TypeOfInquiryNumber=T

USPS
https://tools.usps.com/go/TrackConfirmAction_input?qtc_tLabels1=%1

Ontrac
http://www.ontrac.com/trackingdetail.asp?tracking=%1

Happy package tracking!


MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More

Adding Customer Item User Defined fields to SOP Invoice

Just recently I ran across a request to add the Customer Item user defined fields to the Sales Blank Invoice Form report in Report Writer. As usual with these type of requests, chances are it's been done before and/or it's probably documented in some KB article.

As it turned out, KB article 918943 outlines the steps required to add the Customer Item Number to the Sales Blank Invoice Form report:

How to add the "Customer Item Number" field to a quote, order, or invoice form in Sales Order Processing in Microsoft Dynamics GP

The KB article however, makes use of the Report Writer function rw_SOP_GetCustomerItemNumber to get around the issue. There's also an additional Report Writer function, rw_SOP_GetCustomerItemDescription which allows you to retrieve the description for the customer item. Now, that's all cool, but what about the user-defined fields?

Customer Item Maintenance

The screenshot above highlights the fields in question. As it turned out, there are no Report Writer functions to retrieve those.

In looking at possible ways to add these fields you could try 3 different things:

1. Use Modifier with VBA to retrieve the user-defined fields. While this is a viable solution, the partner was adamant about not using VBA because of lack of supportability on the Microsoft Dynamics GP 2013 Web Client.

2. Table relationships in Report Writer. After looking at the table keys on SOP_LINE_WORK (SOP10200) and sopCustomerItemXref (SOP60300), I concluded that table relationships would not work either. The problem here is that the SOP_LINE_WORK table does not contain the Customer Number field, required to be able to establish a relationship to the sopCustomerItemXref. After all, if the field existed, there would be no need for the Report Writer functions mentioned above.

3. Support  Debugging Tool. The SDT has the ability to encapsulate Dexterity code with it's Runtime Execute feature. That code can be saved to a Script ID. Furthermore, the Support Debugging Tool leverages the 6 generic Report Writer functions available in the Microsoft Dynamics GP dictionary. These functions were created to allow third party developers a way around an Alternate Report, with the ability to retrieve data from their tables.

For more information on the generic Report Writer functions, take a look at KB article 888884:

Useful functions for developers to use instead of creating alternate reports in Microsoft Dynamics GP

Given all the options and drawbacks, it was decided that Support Debugging Tool would be able to accomplish the job. Since it's a Dex application, it certainly would move forward to Microsoft Dynamics GP 2013 and Web Client, and in addition, would be able to work around the table relationships issue.

---

One thing I like about the Support Debugging Tool's Runtime Execute is the ability to use the Helper functions. In particular, the helper function needed is one that allows us to leverage a generic Report Writer function, the rw_TableLineString, while line items are being printed on the report - when a line item is displayed, we must display the corresponding Customer Item user defined field.

Insert Helper Function window

Since there's a template for the above function, all we need to do is click on the Ok button. As if the Support Debugging Tool wasn't already helpful, it now autogenerates some of the code needed to work with the rw_TableLineString:

Runtime Execute window with auto-generated Dexterity code

All that's left now is to add a script ID and enter the bit of code needed to retrieve the user-defined fields:

Runtime Execute script

The full version of the script can be found below:
Script ID: CUSTITMUDF

local string MBS_TableLineString;
local string MBS_Number;
local integer MBS_Type;
local currency MBS_SequenceOne;
local currency MBS_SequenceTwo;
local integer MBS_Control;
local string MBS_String;

{Declarations}
local string ItemNumber;
local string CustomerNumber;

call with name "MBS_Param_Get" in dictionary 5261, "Number", MBS_Number;
call with name "MBS_Param_Get" in dictionary 5261, "Type", MBS_String;
MBS_Type = integer(value(MBS_String));
call with name "MBS_Param_Get" in dictionary 5261, "SequenceOne", MBS_String;
MBS_SequenceOne = currency(value(MBS_String));
call with name "MBS_Param_Get" in dictionary 5261, "SequenceTwo", MBS_String;
MBS_SequenceTwo = currency(value(MBS_String));
call with name "MBS_Param_Get" in dictionary 5261, "Control", MBS_String;
MBS_Control = integer(value(MBS_String));
MBS_TableLineString = "";

{ Add your code below here }

{ Retrieve the item number in question }
clear table SOP_LINE_WORK;
set 'SOP Number' of table SOP_LINE_WORK to MBS_Number;
set 'SOP Type' of table SOP_LINE_WORK to MBS_Type;
set 'Line Item Sequence' of table SOP_LINE_WORK to MBS_SequenceOne;
set 'Component Sequence' of table SOP_LINE_WORK to MBS_SequenceTwo;

get table SOP_LINE_WORK by number 1;
if err() = OKAY then
 set ItemNumber to 'Item Number' of table SOP_LINE_WORK;
end if;

{ Now, get the customer number }
clear table SOP_HDR_WORK;
set 'SOP Number' of table SOP_HDR_WORK to MBS_Number;
set 'SOP Type' of table SOP_HDR_WORK to MBS_Type;

get table SOP_HDR_WORK by number 1;
if err() = OKAY then
 set CustomerNumber to 'Customer Number' of table SOP_HDR_WORK;
end if;

{Since we have the customer number and item number, we should now be able to
 retrieve the customer item number
}

if not empty(ItemNumber) and not empty(CustomerNumber) then
 clear table sopCustomerItemXref;
 set 'Item Number' of table sopCustomerItemXref to ItemNumber;
 set 'Customer Number' of table sopCustomerItemXref to CustomerNumber;
 
 get table sopCustomerItemXref by number 1;
 if err() = OKAY then
  case MBS_Control 
   in [1] {UDF 1}
    MBS_TableLineString = 'User Defined 1' of table sopCustomerItemXref;
   in [2] {UDF 2}
    MBS_TableLineString = 'User Defined 2' of table sopCustomerItemXref;
   in [3] {UDF 3}
    MBS_TableLineString = 'User Defined 3' of table sopCustomerItemXref;
   in [4] {UDF 4}
    MBS_TableLineString = 'User Defined 4' of table sopCustomerItemXref;
   in [5] {UDF 5}
    MBS_TableLineString = 'User Defined 5' of table sopCustomerItemXref;
   in [6] {UDF Key 1}
    MBS_TableLineString = 'User Defined Key1' of table sopCustomerItemXref;
   in [7] {UDF Key 2}
    MBS_TableLineString = 'User Defined Key2' of table sopCustomerItemXref;
   in [8] {UDF Key 3}
    MBS_TableLineString = 'User Defined Key3' of table sopCustomerItemXref;
   in [9] {UDF Key 4}
    MBS_TableLineString = 'User Defined Key4' of table sopCustomerItemXref;
  end case;
 else
  MBS_TableLineString = "";
 end if;
end if;

{ Add your code above here }

call with name "MBS_Param_Set" in dictionary 5261, "TableLineString", MBS_TableLineString;

Cool balloons! One aspect of the programming was, how to leverage the same function (as opposed to creating multiple scripts that would perform the same operations) to pull in different UDFs? As it turns out, there's a parameter in the rw_TableLineString function, which allows you to specify a control value which determines the position of the piece of data to be returned. This control value is an integer type. Knowing this allowed me to send in a numeric value for the UDF I wanted to retrieve and define a case...end case statement evaluating the control parameter to return the proper UDF field.

---

Finally, the rest is just house keeping at the Report Writer level... First, we must create two currency calculated fields: one for the Line Item Sequence and another for the Component Sequence. As it turns out, our Report Writer custom function requires two currency parameters. Below is the rw_TableLineString function signature

rw_TableLineString()

in integer dict_id; {Dictionary ID}
in string script_id; {Script ID} in string sNumber; {control field 1}
in integer sType; {control field 2}
in currency cSequenceOne; {control field 3}
in currency cSequenceTwo; {control field 4} 
in integer iControl; {which piece of data to return}

Our calculated fields are shown below:

(C) Component Sequence calculated field

(C) Line Item Sequence calculated field

Finally, we need a calculated field to invoke our Report Writer function, which in turn will call our script ID created in Support Debugging Tool. In this specific case, we are going to retrieve the Customer Item user-defined field 1.

CustomerItemUDF1 Calculated Field

FUNCTION_SCRIPT( rw_TableLineString 5261 "CUSTITMUDF" SOP_LINE_WORK.SOP Number SOP_LINE_WORK.SOP Type (C) Line Sequence Number (C) Component Sequence 1)

We can now move our CustomerItemUDF1 calculated field onto the report layout:

After granting security to the modified report, we can print an invoice to verify the report works.

As you can see, once more we have leveraged the power of the Support Debugging Tool to deliver what would have otherwise seemed like a difficult or unattainable customization to a report. I hope this is yet another incentive to install the tools and begin taking advantage of its features.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Read More