Calling a procedure

You can call a Microsoft Dynamics GP procedure exactly the same way as you call your own procedures. Use the call script_name syntax for procedures and the call script_name of form form_name syntax for form procedures.

1. Find out which procedure you want to use.

There are a variety of ways you can determine which procedures you’ll need to use:

• Use the Dexterity Script Logger to find the specific procedures Microsoft Dynamics GP calls for a given process.
• Use the procedure design documents available with the SDK for a description of all procedures available.
• Use the procedures listed in Procedure list as a reference to the most common and useful procedures.
• Use the procedures listed in Script Reference, to perform common integration tasks, such as adding navigation for your application.

2. Call the procedure.

In your development dictionary, write the script that calls the procedure. Be sure you’re using the exact name of the procedure as it’s displayed in the SDK procedure design documents. Parameters passed from your script must use the same data types and the same order as those listed in the documentation.

3. Test the results of the procedure.

Use the sample company and test the results of the call. If the procedure updated several tables (such as when posting a batch or adding a record to a work table), the accounting system may reject new records if the procedure didn’t update associated tables properly. To check the validity of any Microsoft Dynamics GP tables you’ve updated, use the table maintenance utilities for each table you’ve updated.

Documentation Feedback

---