Hi guys,
I wanted to tell all you committers and participants you're doing a great job with this module!
I'm wondering if it's possible to show values inserted in the various description fields I've put into my webform (descripion_1, description_2 etc.) separately in my sugar crm lead form and not all mashed together in one description field as it is now.
To put it more clearly, if I have in my sugar webform 'Rome' as a value in description field 1 and 'Italy' in description field 2, the values 'Rome' and 'Italy' will show up together in my sugar lead 'description' field.
I was so naive as to think it would be enough for me to create in the sugar studio module two new field names, descripion_1 and description_2, put them into the lead masks and those webform2sugar values would show up separately each one in it's own field.
Hope someone can shed some light on this...
Thanks!
Friso
Comments
Comment #1
patrickroma commentedsubscribe
Comment #2
rmcom commentedDear Friso,
I am trying to get
- webform2sugar-6.x-4.0-beta1
to work with
- webform-6.x-3.6
However, in the Webform3 form, the field to enter the Campaign ID seems to be missing.
Are you aware of this issue? Can you help?
Grazie, Robert
Comment #3
rurri commentedFriso,
This appears to be happening because of the current special case for descriptions. The system specifically maps all of these to a description field.
Not sure which version of sugar you have, but if you can create custom fields (that do not map to a field name of description_x, then you should be able to create a custom mapping in the webform2sugar_fields.inc file.
I have not tested this before, but I have heard success from others who have created custom fields, then added them to the mapping in the above file.
Rurri
Comment #4
drhus commented#3 rurri
would you give us some details about mapping to custom fields?
Comment #5
rurri commentedIn order to map custom fields you simply need to add a line webform2sugar_fields.inc file. I think if you open the file you will see where the new field should go.
However, as this should not be necessary in the majority of cases, and since it sounds like Friso is willing to make the field name anything such as description_1, etc.. I have updated the field list to include 9 custom fields.
custom_1
custom_2
....
custom_9
This should allow for the mapping of up to 9 custom fields, if you create the fields in the sugar studio.
I think these new fields will fix this issue that Friso was having.
This code was just checked into the dev branch.