Skip to main content
Glenn Daly (Pod Point) 님이 #Data Management에 질문했습니다
I have two fields on a junction object that look up to the account object. One is called "Member Account" the other "Group Account". If Account A = Member Account, and Account B = Group Account then Account A shouldn't be able to be a Group Account if Account B is a Member Account.

 

I realise that I can't enforce this with a validation rule, so was thinking along the lines of creating another field, making it unique, and updating it with the values of two fields combined, but that probably won't work either.

 

Any ideas on how I can prevent this happening?
답변 2개
  1. 2016년 6월 3일 오후 5:28
    Hi Glenn,

     

    I don't know how complicated it is to accomplish this using duplicate rule/validation rule but I can suggest you to get advantage of a trigger/flow. I can help you in trigger but you will have to wait for someone who is more efficient in flows.

     

    Thanks,

     

    Naval
0/9000