nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Non-Constituent Spouses that have a Cons ID

Carlene Johnson

Have any of you seen this before? I have 67 records in a client database where the spouse looks like they have a Cons ID, but the spouse isn’t actually a constituent.

Query criteria I was able to use to identify the records:

7d7cff95b028b261283711deac5dad28-huge-im

Here is what the record looks like:

8e63c7d52a54255a5d4e9b97aa91752f-huge-im

As you can see the ID field is populated in gray but the name fields are in black – so she isn’t a constituent.

d77375e17fcf7f15831090ae66738404-huge-im

Any suggestions on how to delete that data from the Spouse Cons ID field? I looked to see if there was a plugin or utility to address these situations, but I couldn’t find one. Google searching the Knowledge Base didn’t provide any insight.

All thoughts are welcome!

Find more posts tagged with

Comments

JoAnn Strommen

@Carlene Johnson Goodness LOL
Have not seen. Duplicated your query to see we had any like records. My results were 0.

I think that might be a support thing. Do the records show anything in web view that might be a reason?
Sorry no solution suggestions. Best of luck on this one.

Carlene Johnson

@JoAnn Strommen
Thanks so much. I am opening a support case but, as always, find it beneficial to crowd source as well! ? Nothing in webview that I can see. I suspect that it was constituents who were promoted to full record and then demoted after the fact, but I really wish there were a plug-in to clear the code!

I know I can promote to a full constituent and then break link and delete constituent record but don't want to have to do that 67 times.

I will also explore to see if via import I can use the ^ to delete the Cons ID, but have doubts that it will work.

I was really hoping there was a plugin or utility to address this!

Christine Robertson

@Carlene Johnson Definitely weird, but why do you need to remove the ID? Is it breaking something?

Carlene Johnson

2cf52977186ba9523a71419f82d5be87-huge-im

@Christine Robertson Great question! One example is this query that I use to identify Matching Gifts that have not been soft credited to spouses.

There are other queries where I use that field to either identify the presence or absence of the spouse. Some of the queries can be written differently, but not all of them. And Cons ID is a 1:1 field which is a helpful thing.

There are a bunch of random things I use it for, so while not a dealbreaker it is just super frustrating to have to remember that for this one client I have to do everything differently than I would in all the other databases I work in.

Dariel Dixon

@Carlene Johnson Is this database have an associated FE instance? Could it be a link to something else down the line. I would definitely export any importIDs and Constituent IDs for these individuals before removing them.

Sunshine Reinken Watson

@Carlene Johnson hmmm… this is definitely frustrating. Is it possible to use other criteria for the spouse that would only be present if they were a constituent? Maybe constituent code if that is a required field for your client?

Carlene Johnson

@Dariel Dixon Nope, not integrated with FE. But always good advice to hang onto that information!

Carlene Johnson

@Sunshine Reinken Watson

There are some queries where I use that field to either identify the presence or absence of the spouse. Some of the queries can be written differently, but not all of them. And Cons ID is a 1:1 field which is a helpful thing.