Skip to main content
Topics#ApexPergunta de Glenn Daly
Glenn Daly (Pod Point) perguntou em #Apex
6 de jun. de 2016, 16:26

Preventing duplicate records on a junction object with 3 lookup fields.

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?

Key point here is that if Account A = "Group Account" and Account B = "Member Account" then Account A can never be "Member Account" if Account B = "Group Account" on another record within the junction object.
4 respostas
  1. Glenn Daly (Pod Point)
    6 de jun. de 2016, 20:05
    Thanks Ashish

    I'm completely new to writing triggers. Would you mind checking if I'm along the right lines below?

    I guess it's going to be a before insert trigger on the junction object.

    Then I'll need to get all of the records of the junction object using a SOQL query and put them into a list/map?

    I'll then need to write some kind of logic. (can you help with this please?)

    Put the records back into a list and insert them into the database?
Escrever uma resposta...
0/9000