This is a recent change made in the plugin. Ultimately CRP's API has special logic around candidate committees which was used as a patch during an earlier phase of this project. That logic is now causing candidates with multiple committees to share the same unique ID. The plugin was using unique ID as a foreign key when running updates (which is what it SHOULD be using) but that was causing overwrites due to that quirk.
Until the CRP API is modified, we are using the actual sponsor name as the key. As soon as possible we should switch back to using the "unique ID" instead.
NOTE: plugin issues will be tracked in the proper repository after launch)
This is a recent change made in the plugin. Ultimately CRP's API has special logic around candidate committees which was used as a patch during an earlier phase of this project. That logic is now causing candidates with multiple committees to share the same unique ID. The plugin was using unique ID as a foreign key when running updates (which is what it SHOULD be using) but that was causing overwrites due to that quirk.
Until the CRP API is modified, we are using the actual sponsor name as the key. As soon as possible we should switch back to using the "unique ID" instead.
NOTE: plugin issues will be tracked in the proper repository after launch)