Share
ReportGood day all. I just wanted to help someone save several hours of their life (and sanity) with a situation i encountered.
I had at one time setup PSTL Master Record Triggers. Just for clarification, this feature provides the ability to roll down Accounts, Vendors, and Customers from 1 database to others and includes changes. Keep in mind this feature is roll down --> only.
Well, since this is TWO, and I mess around with it quite a bit. Add'l databases on my test system come and go. I happen to make a change to an account for testing of another situation, and I received the error
SAVE OPERATION FAILED ON TABLE GL_ACCOUNT_MASTER. TABLE COULD NOT BE FOUND.
Well, I dove right in and ran the standard fixes. Rebuild GL00105. Checklinks. Reload Dynamics procs, triggers...etc. and ultimately DELETED TWO, right down to remove from sql.
After new TWO load, i had the same issue.
I ran a DEXSQL.LOG - Nothing indicative of the problem. I included all ODBC in the DEXSQL.LOG.
SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE
This time...1 line reference that the process couldn't find a table from a long gone database.
(insert Lightbulb here).
Could Master Record Triggers survive a database reload? well, in fact they do....partially.
I rushed right in to PSTL, (no indication Master triggers is enabled) opened up Master Triggers, and there is a partially completed row.
Delete Row, and verify that was the issue.
Have a great day.
*This post is locked for comments
All responses (
Answers (
11,009
