Can I import a constituency code and automatically make it primary for existing constituent records?

Dan Kirk · January 2018

I want to add an additional constituency code for a group of constituents who already have an RE record. For this group, I would like the new imported code to become the primary, and appear first under Constituency Codes on the bio 2 tab (which makes it the primary constituence code in query). I tested this out with import, however I don't see an easy way to set the imported code as primary for each record. The process seems to automatically insert the new code under the existing code(s) without any way to set it as primary during the import. There are a few possible solutions in these forums and the knowledgebase, but my preference is not to update with SQL or go through a process of globally deleting and re-adding just to set the newest additions as the primary constituency code. Can anyone confirm that there is no easy way to do this through import?

Thanks,

Dan

Jen Claudy · January 2018

I'm not sure on Import, but if you use Global Add for Constituent Code, you can check the box to make the new one the Primary.

fd1dfb8549a69d956fc30d9d57e12d2c-huge-ca

Ryan Hyde · January 2018

Yeah, just checked and it doesn't look like this is an option from within import, so you would need to use Jen's method.

Anne Herbert · January 2018

If you do it via Import-O-Matic you have the
ability to make it the primary constituent code.

Dan Kirk · January 2018

Jen Claudy:

I'm not sure on Import, but if you use Global Add for Constituent Code, you can check the box to make the new one the Primary.

That worked. So glad it was this simple.

Thanks,

Dan

Charles Babian · January 2018

Dan Kirk:

Jen Claudy:

I'm not sure on Import, but if you use Global Add for Constituent Code, you can check the box to make the new one the Primary.

That worked. So glad it was this simple.

Thanks,

Dan

It would be really very useful if this "so-called" primary showed up in the actual record! No? Likened to the Phones and Emails.

Alan French · January 2018

Charles Babian:

It would be really very useful if this "so-called" primary showed up in the actual record! No? Likened to the Phones and Emails.

The constituent code at the top of the list on Bio 2 is considered the primary one.

Karen Stuhlfeier · January 2018

It would be more useful if there were a check box for primary instead of it being the one on the top of the list.

Jen Claudy · January 2018

The Primary Constituent Code is the first valid/active code listed on each record.

CodeA 1/20/2018 [blank] this code is considered the Primary Constituent Code as it is the first listed

CodeB 1/1/2017 12/31/2017

CodeC 3/31/2016 [blank]

CodeB 1/1/2017 12/31/2017 this code is first, but has a [Date To] and is considered invalid or inactive

CodeA 1/20/2018 [blank] this code is considered the Primary Constituent Code as it is the first listed that is valid

CodeC 3/31/2016 [blank]

CodeC 3/31/2016 [blank] this code is considered the Primary Constituent Code as it is the first listed that is valid, even though the [Date From] is prior to CodeA

CodeB 1/1/2017 12/31/2017

CodeA 1/20/2018 [blank]

If you make [Constituent Code] a Required Field in your database, the first one will then be blue (or whatever color your required fields are in the Legend)...but this then means that every new Constituent Record must have at least one Constituent Code.

Personally, I dislike the [Primary] and [Inactive] checkboxes on Phones. They're not easy to use, particularly in Query, because they're not tied directly to a Phone Record (i.e. they are in the Field List under [Phones] instead of lower in the tree under [Specific Phones] and each separate [Phone Type]. Love [Phone Comment], though!

Can I import a constituency code and automatically make it primary for existing constituent records?

Comments

Categories