Finance | Project Operations, Human Resources, ...

problem with upgrade to GP 18.3.1200

(0) Share

Report

Posted on by pmg@ics

Hi - last night i upgraded a customer's customization from GP2018 to GP 18.3.1200

I'm getting a warning that one of our Startup triggers failed.

Our scripts uses SOP_DP_Run_Reports. I'm guessing that the parameters might have changed, but cannot find anything regarding that. Although i do know that there are changes to Print Sales Documents in 18.3.

Can someone please provide the parameters for SOP_DP_Run_Reports?

Thanks,

Patti

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (12)

Answers (0)

Suggested answer

Terry R Heley Microsoft Employee on at

Like (1)

Report

Hi Patti,

I do list some of the common parameter changes off this blog

community.dynamics.com/.../table-column-and-parameter-changes-in-microsoft-dynamics-gp-october-2020-release-2020-year-end

You can also use GP Power Tools as part of the free version you can look up parameter changes.

www.winthropdc.com/products_GPPT.htm

I have pasted what I found below for you.

in 'Batch Number' IN_Batch;

in 'SOP Number' IN_Doc;

in long IN_Comp_Seq; {0=no components,filled=components}

in boolean IN_Print_Tax_Details;

in boolean IN_Print_Inclusive_Tax;

in boolean IN_Print_Tax_Invoice;

in boolean IN_Print_Adjustment_Note;

in boolean IN_Include_PS_Line_Comments;

in boolean IN_Include_PT_Line_Comments;

in boolean IN_Force_Functional;

in boolean IN_Print_Doc[9];

in integer IN_Format[8];

in integer IN_Sort;

in 'Print to Screen' IN_Screen[9];

in 'Print to Printer' IN_Printer[9];

in 'Export Type' IN_Export[9];

in string IN_Filename[9];

in integer IN_File_Source;

in 'User ID' IN_UserID; {PR2511}

in 'Sequence Number' IN_SeqNum; {PR2511}

inout file SOP_Document_HDR_TEMP;

inout file SOP_Document_TEMP;

inout file SOP_Error_Log_TEMP;

inout table sopDocumentLineTemp;

in boolean IN_Bin_Sequened;

in boolean IN_Print_PS_Per_Site;

in boolean IN_Print_PT_Per_Site;

in boolean IN_Print_Kit_Components;

in boolean IN_Print_Customer_Item_Document;

in boolean IN_Print_Customer_Item_PS;

in boolean IN_PrintShipToAddrWithLines;

in boolean IN_PrintPTShipToAddrWithLines;

in integer nProcessID;

optional inout table sopIndividualPickTicketTemp; {SOP00029}

optional inout table SOP_Serial_Lot_WORK_HIST_TEMP;

optional in boolean fPrint = true;

optional in boolean fSendEmail = false;

optional in integer nCalledFrom = 0;

optional inout ListObjState oListObjState;

optional in boolean fPrintExceptionReport = false,

fPrintExceptionToScreen = false,

fPrintExceptionToPrinter = false;

optional in integer nExceptionExportType = 0;

optional in string sExceptionPath;

Terry Heley

Microsoft

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi Terry - thanks for providing those parameters. You answered my question, but it doesn't solve my problem - since that's not what changed.

I did read your blog re: parameters and i did try to find the parameters using GP Power Tools, but it was one of the few that are not included - unless i did something wrong.

I appreciate your sending it so quickly.

Thanks very much,

Patti

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi Terry -

We are triggering our script on SOP_DP_Print_Forms. It doesn't look like that has changed, but could you please those parameters also.

Thanks,

Patti

Was this reply helpful? Yes No
Suggested answer

Terry R Heley Microsoft Employee on at

Like (0)

Report

I have had a couple ISV's not have issues with the SOP_DP_Print_Forms.

I think the Dexterity runtime engine seems to be treating the new fPrintAllDocuments parameter like a mandatory parameter, rather than an optional parameter.

That is the only one that changed from 18.3.1173 to 18.3.1200.

I installed the Power Tools and it was free and I think there is a 30 day free trial on it as well that may help you.

Thanks

Terry

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi Terry - the customer is upgrading from GP2018 to GP 18.3.1200. The customization works in GP2018.

I do have GPPT but i get the message {** Global Procedure SOP_DP_Print_Forms not found in Visual Studio **) when i try to Display Parameters.

Are there any changes from GP2018?

Thanks,

Patti

Was this reply helpful? Yes No
Terry R Heley Microsoft Employee on at

Like (0)

Report

I noted it above

I think the Dexterity runtime engine seems to be treating the new fPrintAllDocuments parameter like a mandatory parameter, rather than an optional parameter.

That is the only one that changed from 18.3.1173 to 18.3.1200.

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi Terry - Thank you for your quick responses. I took a chance and added fPrintAllDocuments as a boolean to the end of the IN parameters of our script. I'm no longer getting the error. But i would still like to see that actual new parameter list for SOP_DP_Print_Forms. I would appreciate it if you could sent that.

I do not see them listed in your blog and the parameters for SOP_DP_Print_Forms are not available in GPPT.

Thanks very much,

Patti

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi - i was mistaken. it is not working. Please provide the parameter list for SOP_DP_Print_Forms.

Thank you.

Patti

Was this reply helpful? Yes No
kmalone43 894 on at

Like (0)

Report

Hey Patti, we're receiving the same error after upgrading from 18.3.1200 to 18.3.1245. Did you ever find a solution to this?

Was this reply helpful? Yes No
pmg@ics 15 on at

Like (0)

Report

Hi Kyle - i was never able to get a new list of the parameters SOP_DP_Print_Forms, but based on emails, testing, etc. I changed my script to the following and it worked. In an email, Terry Heley mentioned a new fPrintAllDocuments parameter so i added it at the end. Hope that helps.

in integer IN_Print_Group_Box;

in integer IN_Type;

in 'SOP Number' IN_Doc;

in 'Batch Number' IN_Batch;

in boolean fPrintingList;

in 'SOP Number' IN_Start_Doc;

in 'SOP Number' IN_End_Doc;

in date IN_Start_Doc_Date;

in date IN_End_Doc_Date;

in 'Batch Number' IN_Start_Batch;

in 'Batch Number' IN_End_Batch;

in 'SOP Status' IN_Start_SOP_Status;

in 'SOP Status' IN_End_SOP_Status;

in integer IN_Doc_Sort;

in integer IN_File_Source;

in integer IN_Match_Packing_Slip;

in integer IN_Match_Picking_Ticket;

in boolean IN_Print_PS_Line_Comments;

in boolean IN_Print_PT_Line_Comments;

in boolean IN_Print_PS_Per_Site;

in boolean IN_Print_PT_Per_Site;

in boolean IN_ReprintPS;

in boolean IN_ReprintPT;

in boolean IN_IncludeDSItems;

in boolean IN_IncludeBackOrderedItems;

in boolean IN_Print_Kit_Components;

in boolean IN_Include_Tax_Details;

in boolean IN_Print_Dual_Currencies;

in integer IN_Tax_Print_Options;

in boolean IN_Print_Inclusive_Tax;

in boolean IN_Print_Tax_Invoice;

in boolean IN_Print_Adjustment_Note;

in boolean IN_Print_Prev_Printed;

in integer IN_Format[8];

inout boolean IN_Print_Doc[9];

in boolean IN_Screen[9];

in boolean IN_Printer[9];

in integer IN_Export[9];

in string IN_Filename[9];

in integer IN_Which_Currency;

in 'Sequence Number' IN_SeqNum;

in boolean IN_Print_Customer_Item_Document;

in boolean IN_Print_Picking_Instructions;

in boolean IN_Include_Kit_Components_PT;

in boolean IN_Bin_Sequened;

in boolean IN_Sort_Kit_Components;

in boolean IN_Include_Kit_Components_PS;

in boolean IN_Print_Customer_Item_PS;

in boolean IN_Include_Incomplete_Documents_PT;

in boolean IN_Include_Incomplete_Documents_PS;

in boolean IN_PrintShipToAddrWithLines;

in boolean IN_PrintPTShipToAddrWithLines;

inout ListObjState ListObj;

in boolean IN_Print;

in boolean IN_SendEmail;

optional inout integer nProcessID=0;

optional inout boolean fValidDocsToEmail=false;

optional in boolean fPrintAllDocuments;

Was this reply helpful? Yes No