Hi,

I'm getting the following error:

A duplicate value was specified for field 'WebformSID__c' in object 'Lead', duplicate value '6-3c0b21f7' prior value '6-3c0b21f7'

I've set-up my Salesforce.com field to be:

Unique - Treat "ABC" and "abc" as duplicate values (case insensitive)
External ID - Set this field as the unique record identifier from an external system

Any ideas?

Many thanks
Zap

CommentFileSizeAuthor
#3 DuplicateWebformSIDError-1535722-3.patch856 bytesobsidiandesign

Comments

obsidiandesign’s picture

obsidiandesign commented

Is this error occurring with only one particular submission, or do you get the exact same SID code error no matter why is submitted?

Bryan

Firetracker’s picture

Firetracker commented

Hi,

Each submission seems to have it's own unique code but I get the duplicate error each time.

Submission 1: A duplicate value was specified for field 'WebformSID__c' in object 'Lead', duplicate value '6-3c0b21f7' prior value '6-3c0b21f7'
Submission 2: A duplicate value was specified for field 'WebformSID__c' in object 'Lead', duplicate value '6-cb41dd92' prior value '6-cb41dd92'
Etc

Andy

obsidiandesign’s picture

obsidiandesign commented
StatusFileSize
new DuplicateWebformSIDError-1535722-3.patch856 bytes

Thanks - there was a tiny bug in the module that could cause a duplication error that I hadn't picked up. The module was trying to pass the WebformSID key twice.

The next roll of the 7.x-1.x branch development snapshot will contain the fix, but if you need it sooner, just change salesforcewebform.module using the attached patch.

Bryan O'Shea
Obsidian Design

obsidiandesign’s picture

obsidiandesign commented
Status: Active » Fixed

Marking fixed.

Firetracker’s picture

Firetracker commented

Hi Bryan,

Just to let you know I've applied the patch and the issue is fixed.

Many thanks for your help.

Andy

obsidiandesign’s picture

obsidiandesign commented

Awesome! Thanks for taking the time to report the issue!

Other than that, does the 7.x-1.x branch seem to be working for you?

Bryan

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.