I recently discovered that the system trigger 'taCustomerInsert' is was disabled and has been disabled for the past several years, dating back to when we were on GP10. We are now on GP 2013, R2, wanting to take advantage of some of the new features. I ran the PSTL for GL Account modify/combine, during the process the trigger was enabled. In most environment this would not be an issue, but it cause a custom process to fail because a service account. The issue has since been resolved with elevating the permission of the service account, but I have the following questions:
What is the purpose of the taCustomerInsert trigger? What does the DYNAMICS.dbo.TA_ParentInsertRM do?
Any insight on this matter is greatly appreciated!