Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

CALCULATED FIELD IN PACKING LIST REPORT

(0) ShareShare
ReportReport
Posted on by 17

Hello Experts. Has anyone encountered a scenario wherein the Modified Report is different from another user? We currently have one workstation  where in there is a field missing when we try to print a modified packing list report. The whole report is the same but there is one particular calculated field which is not displaying (item color). When we tried to print from other workstation everything is correct. I am fairly new to GP 2015 and I can't find any workaround to this issue. Please advise.

*This post is locked for comments

  • twelvestrikes Profile Picture
    3,657 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Donn

    We have eliminated the variable that the reports could have been different.  The only other suggestion I have is to re-install the workstation and see if that resolves the issue.

    Be sure to use the reports.dic file from the working workstation after you have done the re-install.

  • Donn Profile Picture
    17 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Jeffrey,

    I've followed all your instructions and I am still printing the same results.

    Just to give the actual scenario, below image is the actual correct print out of the Modified Packing list report.

    Capture-2-_2800_1_2900_.JPG

    and below is the incorrect print out .

    Capture-2-_2800_1_2900_.JPG

    If you can see, all details are the same except for this particular "color" field. I've also checked some other workstations and all of them are printing fine. Any suggestions?

    Thanks again for your assistance.

  • twelvestrikes Profile Picture
    3,657 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Donn

    It appears to me that you may have a mismatch in the report dictionaries. Meaning that they are not exactly the same.  This why I don't like having the report dictionaries local as you can get many versions of reports and then it becomes a nightmare to handle.  A shared reports dictionary on the server is the best route as everyone uses the same version and it gets backed up being on your server.


    Here is what I suggest you try. 

    On the workstation that the report doesn't print correctly, launch Dynamics GP and go to tools > customize > Customization Maintenance.  Take a screen shot of this window that lists the modified reports.

    Next close Dynamics GP and make a backup of the reports.dic file found in the \Program Files (x86)\Microsoft Dynamics\GPxxxx.  You can simply rename it to reportsORIG.dic

    Next copy the reports.dic file from the workstation that the report works correctly from and place it in the \Program Files (x86)\Microsoft Dynamics\GPxxxx directory.

    Launch Dynamics GP and see if you can now print the report correctly.

    If it does print correctly, then you need to determine if the reports in the original reports.dic are different than the reports in the newer reports.dic file that you copied over that will need to be re-imported.  Otherwise you can just go forward with the reports.dic file that you copied.

  • Donn Profile Picture
    17 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Jeffrey,

    Thank you for the swift response.

    This is from the workstation that prints correctly, I have also checked the Dynamics.set file for the other workstation that is not printing correctly and the mapping is also local. Please advise.

    Thank you again for the assistance.

  • Suggested answer
    twelvestrikes Profile Picture
    3,657 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Donn

    Yes, that is exactly what you need to check. Is this from the workstation that prints correctly or incorrectly?

    This shows that the reports are located on the local hard drive. Ideally, I like to have the reports dictionaries located on the server so that there is only one version available and most important, the dictionary file gets backed up regularly. What does the other workstation's file show?

    If it shows a mapping to a shared server location then you will want to have that on all workstations.

    Example you have

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/Data/REPORTS.DIC

    but the working one has

    //servername/directory_name/reports.dic

    This is what you need in the file. Make a backup of the Dynamics.set file just in case before you change any lines. Or you can copy the dynamics.set file from one workstation to another assuming that all the same products are installed on both workstations and the local installation directories are the same.

    Then re-launch Dynamics GP on the problem workstation and you should now have access to the same reports.

    If both workstations are pointing local let me know and I will give you some other instructions

  • Donn Profile Picture
    17 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Jeffrey.. Thank you for the response..

    I am really new with GP and I've followed your advice.

    Is this the path you are referring to? If there is a difference, then what will be the next step to correct this issue..

    Windows

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/Dynamics.dic

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/Data/FORMS.DIC

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/Data/REPORTS.DIC

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/IM.DIC

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/IMFORMS.DIC

    :C:Program Files (x86)/Microsoft Dynamics/GP2015/IMRPTS.DIC

    Thank you again for the response and assistance.

  • Suggested answer
    twelvestrikes Profile Picture
    3,657 on at
    RE: CALCULATED FIELD IN PACKING LIST REPORT

    Hi Donn

    First make sure that both workstations are pointing to the same reports dictionary.

    Check the Dynamics.set file in the \Program Files (x86)\Microsoft Dynamics\GPxxxx  (where xxxx is the version number)

    Open the Dynamics.set file using note pad on the workstation that prints correctly and note the pathing to the reports.dic file.

    Next do the same for the workstation that doesn't print correctly and note where it is pointing to.

    If the path's are different then that is your answer.  The workstations are using different reports dictionaries.  If the paths are both pointing local, then you may have different reports dictionary files loaded on each workstation.  If this is the case then you need to be careful not to over write reports that have been customized on one dictionary over another.  I suggest you let us know and we can guide you further.

    Assuming that both workstations are pointing to the same reports dictionary, the next thing I would try is making sure that the workstation that doesn't print the report correctly has the same printer drivers installed as the one that is printing correctly.  I presume both workstations are printing to the same printer for the packing slip. If this is not the case, try printing from the workstation that doesn't work correctly to the same printer as the workstation that does print uses to see if it is printer related.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 293,311 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,183 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans