Volunteers-for-Salesforce
Volunteers-for-Salesforce copied to clipboard
Cloning V4S Campaign in wizard w/ similar name to source fails
Steps to reproduce:
- create campaign with name "taco bell 12345" and make active with 2 jobs and 3 shifts 2.save record 3.click clone 4.change campaign name in resulting screen "foo bell 12345" 5.click save
The error will occur "Name already exists. Enter a unique name"(see screenshot) No record with the new name exists

@SukiVongchanh I can't reproduce this when testing this manually.
- did you only get this when running automation, or can you manually reproduce?
- do you have any duplicate rules turned on for Campaigns?
never mind! i can reproduce. missed the clone step. thanks!
**lurch: add
Tracking W-020825
Judi I asked I post this extra info here.
From what I can tell, it's not because the campaign name is similar; it looks more like it's balking on the V4SF-specific campaign member statuses that are inserted when you clone. You the see same error cloning a Volunteer campaignand changing it to a totally different name.
AND you see the same error when trying to replace all the statuses on a Volunteer campaign using the AAKConsult Campaign Status app in "replace" mode. With a trigger after insert, it should replace all the statuses in a campaign with new ones. If you try to replace them with the Volunteers standard statuses and any new statuses you would like to add, it errors out with same text. You can't use it with V4SF at all (in my case to add some extra statuses needed for other project management tasks)
I know you are planning on redirecting folks to the wizard, but I assume the underlying issue might get in the way for mass inserts or other code, so I wanted to give you my extra info. Thanks.
I'm getting the same issue using the wizard:
I've tried not overriding the volunteer status as per Barbara's comment, but still the same issue. We always clone all campaigns at the end of the FY.

Anyone knows what's happening?
Another set of users are experiencing this issue as reported on the Hub today.
Another user is experiencing this issue today trying to clone a campaign.