How to avoid "neccessary" duplictes?

Jasmin Beckles · October 2017

Good morning to all!

I am new at my org and have been given the task to clean and manage our RE and the proccesses around it. Any ideas on the following would be more than welcome!!

-Sometimes, over 10 constituent records have been created for let's say Wells Fargo. This has historically been done by the Fianance team in order to have individual checks reflected (different addresses on different checks). Yet for development purposes, this serves to be confusing and often off putting to team members that we ask to log actions and proposals in for Welld Fargo, as so many records appear.

I'm thinking of implemeting some sort of relationship procedure that branches off of a main Wells Fargo account...what are some of your ideas?

Jen Claudy · October 2017

You can combine them all into one Constituent Record with multiple Address Records. Or you can create Relationship Links between the existing Records with one marked as the Main Record and the others as Subsidiary/Branch...then create a Business Rule or Annotation for the records, directing the User to use the main record.

Jasmin Beckles · October 2017

Jen Claudy:

You can combine them all into one Constituent Record with multiple Address Records. Or you can create Relationship Links between the existing Records with one marked as the Main Record and the others as Subsidiary/Branch...then create a Business Rule or Annotation for the records, directing the User to use the main record.

Thanks Jen!

Caitlin Gilmore · October 2017

Jen Claudy:

You can combine them all into one Constituent Record with multiple Address Records. Or you can create Relationship Links between the existing Records with one marked as the Main Record and the others as Subsidiary/Branch...then create a Business Rule or Annotation for the records, directing the User to use the main record.

That's what my org does. We get a lot of grants and contracts from different parts of the government. We have a main office/headquarters and then have subsidiary orgs.

Heather MacKenzie · December 2017

Jasmin Beckles:

Good morning to all!

I am new at my org and have been given the task to clean and manage our RE and the proccesses around it. Any ideas on the following would be more than welcome!!

-Sometimes, over 10 constituent records have been created for let's say Wells Fargo. This has historically been done by the Fianance team in order to have individual checks reflected (different addresses on different checks). Yet for development purposes, this serves to be confusing and often off putting to team members that we ask to log actions and proposals in for Welld Fargo, as so many records appear.

I'm thinking of implemeting some sort of relationship procedure that branches off of a main Wells Fargo account...what are some of your ideas?

For anyone looking at this post, has anybody used the parent org field on the Org 2 tab? I just realized that was there, and wonder how that would work in this situation. Would it be helpful?

JoAnn Strommen · December 2017

We've used the parent / subsidies function for records like Wells Fargo. Parent record easily gives complete giving history if you use SC. Don't know if it would be helpful for actions or proposals. Are those with parent company or with branch facilities? For us actions would be with local branch.

How to avoid "neccessary" duplictes?

Comments

Categories