Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Answered

How to find procedure parameters in recent versions

(0) ShareShare
ReportReport
Posted on by 199
I wrote a Dexterity procedure trigger in a previous version that runs after the GP procedure SOP_DP_Print_Forms.  I'm updating the code to 18.6.1728 and I'm getting an error 2 when registering the trigger. 
 
Can anyone tell me where to go to find the current parameters for GP procedures to find out what changed?
Categories:
  • Pam Robertson Profile Picture
    Pam Robertson 199 on at
    How to find procedure parameters in recent versions
    Thank you so much, Dave.  This was exactly what I needed, and it will be so helpful to have the group link you provided in the future!  
  • Verified answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,945 Most Valuable Professional on at
    How to find procedure parameters in recent versions
    Hi 
     
    The Microsoft Dynamics GP SDK contains a CoreParams_140.txt text file which has the parameters for functions and procedures up to v14.0 when they stopped maintaining the SDK documentation. 😢
     
    Since then, the support team have been posting blog articles with the parameter changes for common procedures and functions.  I have all the articles grouped together on the Microsoft Dynamics GP Links page on my blog (scroll down to second last section):
     
     
    For most (over 92%) of functions and procedures, you can also use the GP Power Tools Resource Information window in Procedures and Functions mode to show parameters. This only works for scripts exposed to visual studio, so there are 8% of scripts which use parameter types not supported by visual studio which don't show up.
     
    Sadly SOP_DP_Print_Forms is one of those.
     
    To minimize disruptions to core code, additional parameters are often added using optional parameters. This requires a recompile of the Dexterity code, but no changes to calling scripts that don't use the new parameters. The downside is that visual studio does not understand optional parameters and so that script is no longer accessible in visual studio.
     
    There are now 3 optional parameters at the end of the parameter list.
     
    optional inout    integer                nProcessID = 0;
    optional inout    boolean                fValidDocsToEmail = false;
    optional    in    boolean                fPrintAllDocuments = false;{Print All documents}
     
    If you try GP Power Tools and it says it cannot find the parameters, then the best you can do is ask on this form and someone (probably me) will give you want you need.
     
    Let me know if you need the full list or if the optional parameters are all you need. The first two optionals where in v14.0. The third parameter was added for v18.3.
     
    Kind regards
     
    David

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,391 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,445 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans