How to set trigger to CRM Contact base table

(0) Share

Report

Posted on by Community Member

I have created one Trigger in CRM Contactbase table, whenever an Insert/Update happens in Contactbase table this trigger will Update/Insert the same data in the another table on another database. This trigger working fine without any error when manual update happens in SQL, but when i update the field in contact entity form it troughs me SQL error .

I get to know that trigger wont work in CRM database tables, But in production it working fine with trigger in CRM table. Facing issues only in non-prod environment. Is there any other way to achieve this SQL trigger to work in CRM ?

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (2)

gdas 50,091 Moderator on at

Like (0)

Report

First of all doing changes in CRM database is completely unsupported. Why not you write plugin and services or windows batch job to push data to another database instead doing unsupported way.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes you are correct but in my client machine, they are already having one trigger enabled in the Contact base table. It working fine Update/Insert to another database table. But in non-prod they kept that trigger in disable mode. I got the change requirement for that trigger now, but i don't know how to validate it after my change made in trigger without affecting the CRM functionality.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Also i have noted one-thing, If i created table in the CRM means the trigger working fine, if i created table in different database means trigger through error.

Was this reply helpful? Yes No
Verified answer

Dynamics365 Rocker 7,755 on at

Like (0)

Report

Doing any development in data base and update any record in database directly is highly unsupported.

It is better to go back to your client and say that what ever development is there is unsupported and we have to do all requirement in supported way.

Was this reply helpful? Yes No
David Jennaway 14,065 on at

Like (0)

Report

I completely agree with the previous post that you should try and replace this with supported functionality. That said, if you only get the error when the custom table is in another database, then the likely issue is SQL permissions. CRM does all data operations via a login that's a member of the SQLAccessGroup AD group, so you'll need to be sure that login has rights to update your custom table

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi David, I am having access to those two database. If setting trigger in CRM table is unsupported means then i am confused how its working in my client Production machine. Anything i am missing.

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (0)

Report

It may work or may not work there is no guaranty and completely depends on your luck , and you can not say why its not working ,as we don't know how Microsoft Dynamics internally works , what are the procedure and trigger internally there in SQL database. Writing trigger in database which may impact CRM system unknowingly. I have similar experience somebody wrote trigger in CRM database and found many issues for that even the systems running properly more than three months and we came to know later when all our data got impacted due to this . So strongly recommend not to write trigger.

Was this reply helpful? Yes No
RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi,

In addition to above, you can share the below documentation from Microsoft which states that it is unspoorted to change the SQL schema other than adding indexes.

docs.microsoft.com/.../supported-extensions

Was this reply helpful? Yes No