Announcements
I received a call today that SOP invoices are not appearing where they should be. The client uses eConnect and there were triggers on the SOP30200 tables. Today those triggers are gone. I checked other tables and those triggers are there. How do I recreate those triggers? I have gone into Requester Setup Tool and unclicked and reclick the insert/update options and clicked update but the triggers do not return.
*This post is locked for comments
Tim, I am dealing with a vendor that never makes mistakes. It is always someone else that made the mistake. At this point I have alerted IT to what I have found. That is where I will leave it.
Ah - yes looks like that is not a standard trigger.
I wonder how it got removed. You've already given your options, up to you which one to take... vendor or backup. You probably need to reverse engineer the out table values from the trigger so might be quicker to call the vendor.
Tim.
Tim, is this DOCTYPE 'toWebSite_Post_Sales_Transaction_Header' standard for eConnect or is this something the developer added?
It is the four triggers associated with this and the SOP30200 table that are missing. We did a GP upgrade on 05/25/2019. I have a backup from 07/09/2019 showing these triggers were still there. Somewhere between 07/09/2019 and last week these triggers got deleted. The code for these triggers must reside with the vendor. I could load the one I have from the 9th but I am not sure if they are the most recent.
This is perfect, Thank you. Now I get to argue with the eCommerce vendor who uses eConnect who will blame me for deleting these triggers.
From
C:\Program Files (x86)\Microsoft Dynamics\eConnect 14.0\Custom Procedures\Requester
grab Sales_Hist_trans.sql
Use this to rebuild the requester table data. Read it first to understand what it will clear before it recreates the records.
Then enable the requester.
select * from eConnect_Out_Setup where TABLENAME='SOP30200'
UPDATE eConnect_Out_Setup
SET INSERT_ENABLED=1,UPDATE_ENABLED=1,DELETE_ENABLED=1
where TABLENAME='SOP30200'
Should see 3 triggers named link this:
eConnect_Sales_History_TransactionSOP30200_*Trigger
If that doesn't work, go back and look at the trigger on the eConnect_Out_Setup table and check they are enabled in SQL, named:
eConnectOutSetupDelete
eConnectOutSetupEnabled
Next you are into permissions, but running above manually via SQL you should see and errors to diagnose from there.
Tim.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
