Reciprocal Relationship Upload Issue

Paula Pack · August 12

Hello RE family! I uploaded 10K + constituents to RE database and included a reciprocal parent/child relationship. All data populated correctly in web view EXEPT the parent is not showing up on the child's record but the child IS showing up on the parent's record. To complicate things further, I tried to just upload a file tying the parent to the child and when I did this, the record showed up twice on both the child and the parent's account. Additionally, If I go to the parent's account in web view and open the child relationship, but change nothing, and then hit save, the parent then populates on the child's account. It's almost like the data are "stuck." Any suggestions from the group on how to fix this?

Alex Wong · August 12

When you say you "uploaded", do you mean you use dbview import relationship to do this?

If so, there's a checkbox in the import that is used to do "recipricol" of relationship, if not checked (by default it is NOT checked), you will only get relationship record on one side only.

If you "upload" again (import again), you are essentially importing a 2nd "new" set of relationship.

Ryan Hyde · August 13

I concur with Alex's diagnosis here. I think the best way to clean this up, assuming you haven't added any additional data to the records you just imported, is to just globally delete all of the records from RE and try again, making sure you check that box. Globally deleting these records should be pretty easy, as they'll all have the same characteristics (added on the same date, added by the same person, zero gift history, zero proposals, zero actions, etc.).

It's also always best practice to do a sample import of a handful of records (or even one, assuming they're all basically the same) to see if everything works as expected when doing a novel import like this.

It's also best practice to set the import module to create a query of all imported records when you do this sort of thing so that if you find you've made a mistake after the fact, you can use that static query to feed your global delete or global change.

Alex Wong · August 13

Adding some clarity to what Ryan said here. If you only imported relationships, the constituents already exists in your database prior to relationship import, then you do not want to delete the constituent records.

There is a global delete relationship in dbview Admin. I haven't used it before, so you may want to take extra care to not delete relationship that pre-exists prior to your relationship import.

Austen Brown · August 13

Here's directions on how to reciprocate those relationships via import, without running a Global Delete: https://kb.blackbaud.com/knowledgebase/Article/40399

Reciprocal Relationship Upload Issue

Answers

Categories