web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Trigger on SOP_Post_TR...
Microsoft Dynamics GP (Archived)

Trigger on SOP_Post_TRX procedure not working in 2016*

(0) ShareShare
ReportReport
Posted on by HasibRahman 325

Hi Experts,  in need of help very badly.

i have placed a trigger on SOP_Post_TRX , 

the trigger is working on this version  16.00.0439   (RTM)

but the same trigger is not working on this version  16.00.0620

may i know what will be the reason for the uncertainty.

i dont have access to the source code. so kindly direct me with this problem friends.

below are the two versions 

working in below microsoft gp 2016 version

SE-Dev.jpg

not working in below version of microsoft GP  2016

SE-Staging1.jpg

have anyone faced this situation before?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Tim W Profile Picture
    Tim W 2,925 on at

    I've never seen what you describe but I have many times thought I was running a trigger and was not for various reasons.

    First thing I do in similar situations is put -> warning("Here"); at the top of my trigger.  Then when running see if I get that far in runtime because I might have commented out the startup line, GP might run a different trigger then I expect, parameter miss match etc....

    Dex version being the issue ... I don't see that as very likely.

  • Suggested answer
    MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    Hasib,

    I took a look at the procedure signature between RTM and R2 and did not notice anything different. Maybe you are missing some script parameter or have an invalid data type?

    2016 RTM

    in		boolean					IN_Edit_List;
in		boolean					IN_Print_Report;
in		boolean					IN_Print_MC_Report;
in 		boolean					IN_PrintDistReport;
in		boolean					IN_Auto_Post_To_GL;
in		boolean					IN_Post_To_GL;
in		boolean					IN_Use_Unique_Batches;
in		boolean					fBatchMaintainHist;
in		boolean					fTrxMaintainHist;
in		boolean					fDistMaintainHist;
in		integer					IN_Post_With_Detail;
in		boolean					fUseAcctSettings;
in		integer					IN_Window_Type;
in		'Source Document'		        IN_Source_Doc;
in		'TRX Source'			        IN_TRX_Source;
out		integer					OUT_TRX_Error;	{errors which may cause posting to stop, 0=OKAY}
inout	        boolean					INOUT_First_TRX;
inout	        'GL Journal Sequence'	INOUT_GL_Sequence;
inout	        'GL Journal Entry'	INOUT_GL_Journal;
inout	        'GL Batch Number'	INOUT_GL_Batch;
inout 	        'TRX Source'		sPerpAdjustTrxSrc;		{Batch ID for any Perpetual revaluation}
inout	        'Journal Entry'		nPerpAdjustJE;			{Journal Entry for any Perpetual revaluation}						
inout	        'Sequence Line'		nPerpAdjustSeq;			{Journal Entry Line Number for any Perpetual revaluation}
inout	        integer		        nPerpAdjustErr;			{Journal Entry Err Number for any Perpetual revaluation}
inout	        file			Batch_Headers;		{positioned}
inout	        file			IV_Cost_Variance_TEMP;
inout	        file			RM_Module_SETP;		{positioned}
inout	        file			SOP_HDR_HIST;
inout	        file			SOP_HDR_WORK;		{positioned}
inout	        file			SOP_Report_TEMP;
inout	        file		        SOP_SETP;		{positioned}
in		table			sopIVCache;
inout	        table			sopDistributionTemp;
optional inout	boolean			fDistributionsPosted;
optional in	boolean			IN_InvoiceHasReturns;
optional inout 	table 			CM_Transaction_Temp;
optional in 	integer 		nCallerID;
optional out	string			sMsg;
optional in 	integer			IN_Use_Posting_Date_From;


    2016 R2

    in		boolean				IN_Edit_List;
in		boolean				IN_Print_Report;
in		boolean				IN_Print_MC_Report;
in 		boolean				IN_PrintDistReport;
in		boolean				IN_Auto_Post_To_GL;
in		boolean				IN_Post_To_GL;
in		boolean				IN_Use_Unique_Batches;
in		boolean				fBatchMaintainHist;
in		boolean				fTrxMaintainHist;
in		boolean				fDistMaintainHist;
in		integer				IN_Post_With_Detail;
in		boolean				fUseAcctSettings;
in		integer				IN_Window_Type;
in		'Source Document'		IN_Source_Doc;
in		'TRX Source'			IN_TRX_Source;
out		integer				OUT_TRX_Error;			{errors which may cause posting to stop, 0=OKAY}
inout	        boolean				INOUT_First_TRX;
inout	        'GL Journal Sequence'	        INOUT_GL_Sequence;
inout	        'GL Journal Entry'		INOUT_GL_Journal;
inout	        'GL Batch Number'		INOUT_GL_Batch;
inout 	        'TRX Source'			sPerpAdjustTrxSrc;		{Batch ID for any Perpetual revaluation}
inout	        'Journal Entry'			nPerpAdjustJE;			{Journal Entry for any Perpetual revaluation}						
inout	        'Sequence Line'			nPerpAdjustSeq;			{Journal Entry Line Number for any Perpetual revaluation}
inout	        integer			        nPerpAdjustErr;			{Journal Entry Err Number for any Perpetual revaluation}
inout	        file			        Batch_Headers;		{positioned}
inout	        file				IV_Cost_Variance_TEMP;
inout	        file			        RM_Module_SETP;		{positioned}
inout	        file				SOP_HDR_HIST;
inout	        file				SOP_HDR_WORK;		{positioned}
inout	        file				SOP_Report_TEMP;
inout	        file				SOP_SETP;		{positioned}
in		table				sopIVCache;
inout	        table				sopDistributionTemp;
optional inout	boolean			        fDistributionsPosted;
optional in	boolean			        IN_InvoiceHasReturns;
optional inout 	table 			        CM_Transaction_Temp;
optional in 	integer 		        nCallerID;
optional out	string			        sMsg;
optional in 	integer			        IN_Use_Posting_Date_From;


  • Verified answer
    Lucas Miller Profile Picture
    Lucas Miller Microsoft Employee on at

    Like Mariano I also checked the procedure's parameters for those two specific builds and didn't see any differences.

    If you go to the Customization Status window and print the Trigger List report can you confirm that your trigger wasn't registered?  

    Otherwise Tim's recommendation to add some warnings to your Startup or trigger script to see that it is going where you think it should be going.

  • HasibRahman Profile Picture
    HasibRahman 325 on at

    Thank you very much Mariano,Lucas,Tim.

    as you people suggested the problem was not because of the version difference, that helped me to think from the other perspectives.

    Problem faced

    The SOP_Post_TRX script didn't trigger in one particular company. but was working fine in all other company. finally found that the batch didn't even got posted because of out of range fiscal period .

    Thanks ones again guys.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
talty09 Profile Picture

talty09 2

#1
Anthony Beatty Profile Picture

Anthony Beatty 2

#3
CP04-islander Profile Picture

CP04-islander 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans