I have a source file that provides Constituent ID, Constituent Code Name, and either "Date From" or "Date To" on each row (sorted oldest to newest). 4-10 varieties of code name.
IOM will only update the first instance of the a given code on a given const record.
So, how can I maintain my constituent code from and to dates without deleting the specific code and reimporting the entire history, every week?
1- Could I easily map a RE export of the existing constituent code import IDs to my weekly import sheet? [sure, but what about multiple instances; and, doesn't this excel work introduce risk, perhaps unnecessarily?]
2- Could I develop a constituent code import ID system that can be "predicted" by the import sheet or IOM profile, and easily applied? [I'm imagining some combination of constituent ID and an identifier (year month week?) for the last import, but I can't see how to do this in a way that would not require some level of Export for those constituents who do not have activity in the current month but still need their CC import ID "updated" so they would be updated next month, should there be some status change (not to mention some level of deleting prior instances of the code?)].
Mostly just wondering: how folks do accomplish this task?
Also considered exporting all codes that are on the import sheet, global delete, and reimport to ensure that every instances of a code with a blank "Date To" is first on the record? Sounds like a lot of mess. Using "primary" const code for this also doesn't do much for me.
Thanks for the input!
Looked at attributes, but short of having a unique attribute for every code for every period needed (ex: "CodeX 2015.2 - Yes") I just don't see how Query can accurately identify constituents with that code in any given range... Const Codes seem the obvious choice for this information with to and from dates linked in one instance.
Anyone at IOM or in the community with other ideas?