Open Forum

Expand all | Collapse all

Report Writer fields showing unexpected information

  • 1.  Report Writer fields showing unexpected information

    Posted Dec 17, 2019 03:47 PM
    Good afternoon,

    Our business office is using Stub/Check/Stub checks and has requested that the vendor name and address be printed on the bottom stub. I made some changes to the report, and it works well when they print a batch including a single check, but displays incorrect information when printing batches including multiple checks.

    Steps I took to change the report:
    1. Opened Microsoft Dynamics GP 2015 and logged in using our service account.
    2. Navigated to Microsoft Dynamics GP -> Tools -> Customize -> Report Writer.
    3. Selected Microsoft Dynamics GP as the product and clicked OK.
    4. Clicked Reports in the toolbar.
    5. Clicked Check With Stub on Top and Bottom - Graphical in the Modified Reports toolbar. Note that they had already modified this report before I started working here, which is why it already appeared in the modified reports list.
    6. Clicked Open.
    7. Clicked Layout.
    8. Examined the F2 section of the report, which contained the body of the check and showed the data that the business office had requested be duplicated on the bottom stub. It had the following fields: Vendor Check Name, Address 1, Calc Address 2, Calc City-State-Zip, and CountryIFnotUSA. Vendor Check Name and Address 1 came from the PM Payment WORK table and had a Display Type set to Last Occurrence. Calc Address 2 and Calc City-State-Zip had blank table names and had a Display Type set to Data. CountryIFnotUSA had a blank table name and had a Display Type set to Last Occurrence.
    9. Dragged each of those fields from the Layout tab of the Toolbox window onto the PF area, and set their display types exactly as they were set in the F2/main check area.
    10. Closed the Report Layout window and clicked Save.
    11. Clicked OK in the Report Definition window.
    12. Clicked File -> Microsoft Dynamics GP to return to the main interface.

    Steps I took to print test checks:
    1. Clicked Transactions -> Purchasing -> Receivings Transaction Entry.
    2. Changed Type from Shipment to Shipment/Invoice.
    3. Hit tab to autogenerate a Receipt No.
    4. Entered 12/17/2019-2 for the Vendor Doc. No
    5. Entered 12/17/2019 EA4 as the Batch ID and hit tab. Clicked "Add" on the "Do you want to add this batch?" prompt.
    6. Clicked Save on the new Purchasing Batch Entry window.
    7. Entered the Vendor ID for Vendor A and hit tab.
    8. Clicked in the Vendor Item field and then clicked the small blue arrow pointing to the right in the group of buttons just to the right of the "Vendor Item" label.
    9. In the Receiving Items Detail Entry window, entered "test item" for the Vendor Item, 1 for the Qty Shipped, $123.45 for the unit cost, and tabbed down to the Purchases Account field. Entered an account number and clicked Save. Closed the Receiving Items Detail Entry window.
    10. Clicked Save in the Receiving Transaction Entry window.
    11. Repeated steps 2-10 with the following exceptions:
    * Changed the Vendor Doc. No to 12/17/2019-3.
    * The second time through, it did not prompt me to create the batch called 12/17/2019 EA4 as it already existed.
    * I used the Vendor ID for Vendor B instead of Vendor A.
    12. Closed the Receivings Transaction Entry window.
    13. Clicked Transactions -> Purchasing -> Purchasing Batches.
    14. Clicked the magnifying glass next to the Batch ID field and double clicked the 12/17/2019 EA4 batch.
    15. Clicked the Post button, which caused it to print four pages.
    16. Closed the Purchasing Batch Entry window.
    17. Clicked Transactions -> Purchasing -> Select Checks.
    18. Typed 12/17/2019 EA4 into the Batch ID field. Clicked "Add" on the "Do you want to add this batch?" prompt.
    19. Clicked Save in the Payables Batch Entry window. This closed that window.
    20. Clicked Build Batch in the Select Payables Checks window. After a few seconds, a batch total of $246.90 appeared in the Batch Total field.
    21. Clicked Print Checks.
    22. In the Print Payables Checks window, clicked the Print button.
    23. Clicked Print in the Report Destination window. This printed two checks.
    24. Clicked Process Later in the Post Payables Checks window.

    What I expected to happen:
    At this point, I expected to have two printed checks in Stub/Check/Stub format. On the first check, I expected Vendor A's name and address information to show up on the check (where the window would be on an envelope) and Vendor A's name and address information to show up near the bottom edge of the bottom stub. On the second check, I expected Vendor B's name and address information to show up on the check and Vendor B's name and address information to show up near the bottom edge of the bottom stub.

    What actually happened:
    On the first printed page, Vendor A's name and address information showed up on the check (where the window would be on an envelope) and Vendor **B**'s name and address information showed up on the attached bottom stub. The second printed page looked as I expected with Vendor B's information in both locations.


    Any help in resolving this issue would be appreciated.

    ------------------------------
    Eric Anopolsky
    New Mexico Military Institute
    Roswell NM
    ------------------------------
    Conference-GPUG_200x200


  • 2.  RE: Report Writer fields showing unexpected information

    GOLD CONTRIBUTOR
    Posted Dec 18, 2019 09:29 AM
    Eric,

    Not sure if this is your issue or not.  But, I would look at all of the properties for the field(s) you placed on the report.  To see the properties window click Layout > Properties.  With the Properties window visible, click on your field.  Note there are two tabs of properties in the window.  I would play with the DisplayType field.

    I hope this helps.

    Chris

    ------------------------------
    Chris Donnelly
    Sr Mgr of Info Systems and Financial Reporting
    Healthmark Industries
    ------------------------------

    Conference-GPUG_200x200


  • 3.  RE: Report Writer fields showing unexpected information

    Posted Dec 18, 2019 04:20 PM
    Good afternoon,

    Thanks for the suggestion!

    Please be advised I just compared the field properties for each field that appears in both the check itself (F2 section) and the footer (PF section). In the Object tab of the Properties window, all properties are indentical except for the Section property, which seems to reflect the location of the field rather than the data it contains.

    In the Visual tab of the Properties window, the fields have several differences, but they appear to be purely cosmetic.

    Thanks,

    ------------------------------
    Eric Anopolsky
    New Mexico Military Institute
    Roswell NM
    ------------------------------

    Conference-GPUG_200x200


  • 4.  RE: Report Writer fields showing unexpected information

    GOLD CONTRIBUTOR
    Posted Dec 18, 2019 05:33 PM
    Eric,

    Here's what I would do...  revert back to the out-of-the-box check layout (after saving a copy of your modified one) and make your updates in small 'waves'.  Do a few changes and verify them for each wave.  Test both single-check batches and multi-check batches for each wave.  This should help to isolate whatever flaw or issue you are encountering.

    Sorry I don't have a silver bullet.  Maybe someone else might find it in your explanation.  I've been in your shoes many a time.  Sometimes, you just have to start over with something that works and build on it until you get there,

    Chris

    ------------------------------
    Chris Donnelly
    Sr Mgr of Info Systems and Financial Reporting
    Healthmark Industries
    ------------------------------

    Conference-GPUG_200x200


  • 5.  RE: Report Writer fields showing unexpected information

    Posted 15 days ago
    Good afternoon,

    Please be advised we have found a workaround. In case anyone else is having the same issue, here is a summary:

    It appears that something about the PF section of the check report causes fields to start using values from the next check and its associated vendor. After checking with the user, she determined it would be acceptable to print a copy of the vendor's address information on the top stub rather than bottom stub, so that she could retain the top stub and send the check and bottom stub to the vendor.

    We identified two locations on the check report that could be filled with custom data: line 2 of the PH section (the first line being only intermittently visible due to page margins) and line 1 of the F2 section. The PH section appears entirely on the top check stub, which is what we wanted. While the F2 section is supposedly set aside for the check itself, we found that line 1 of section F2 printed just above the perforation separating the top stub from the check, so it would appear on the top stub.

    We then placed copies of the fields from the payee/address window area of the check stub in the areas identified in the previous paragraph. For cosmetic reasons, we reduced the font size of each field to 8 points and set the background fill style to clear.

    We set each field's display type to Data for two different reasons:

    1. According to page 66 of the Microsoft Dynamics GP 2013 Report Writer User's Guide document (the most recent one I could find), Data is one of few permitted display types in the Page Header section where some of our fields ended up. In particular, Last Occurrence is not permitted.

    2. According to the Data section on page 64 of the same document, "Calculated fields placed in footers should have their display type changed from Last Occurrence to Data, so that the calculations will perform properly." Some of our calculated fields ended up in line 1 of the check area, which is technically a footer, so we changed the display type accordingly.

    This was sufficient to generate correct results.

    ------------------------------
    Eric Anopolsky
    New Mexico Military Institute
    Roswell NM
    ------------------------------

    Conference-GPUG_200x200


If you've found this thread useful, dive deeper into User Group community content by role