0

I have done a code that will not allow the users to convert an account to partner and set the field Type to a particular value. So far all is working as expected. However, the user can still take out the primary contact role afterwards. This means they set the primary contact role, so they are allowed to set the account for a particular Type and convert it into partner, but after this they can take out the primary contact. I hope this is clear.

To tackle this issue I was thinking of creating a trigger for the object AccountContactRole to code the constraint, but it is not possible to use a trigger over that object.

Can you please advise?

0

Maybe you could change it in the trigger of the contact related to your accountContactRole?

  • It needs to be done over the AccountContactRole object. However, it seems that there is no solution because AccountContactRole does not allow triggers. – Cuban coffee Jul 25 '16 at 8:01
0

I do not think there is a solution because the AccountContactRole Object does not allow triggers. However, this can be tackled by creating a field on the Account Object, for instance a field called Primary contact e-mail and using constraints to enforce the end-user to fill it out.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.