Call us on : +44 (0)118 303 0100
Placeholder

Customer Forum

Submitting no_phone_soliciting value to a sales lead

External Posted: 2011-11-04 10:07

Hello,

Could anyone confirm the correct format to supply values for the opt out section for a new sales lead?

In php I have tried the following param array configurations:

$params['org_lead_party[no_phone_soliciting] '] = true/on/1

$params['org_lead_party[no_email_soliciting]'] = true/on/1

$params['org_lead_party[no_post_soliciting]'] = true/on/1

$params['no_phone_soliciting '] = true/on/1

$params['no_email_soliciting'] = true/on/1

$params['no_post_soliciting'] = true/on/1

$params['org_lead_party[main_location][no_phone_soliciting]'] = true/on/1

$params['org_lead_party[main_location][no_email_soliciting]'] = true/on/1

$params['org_lead_party[main_location][no_post_soliciting]'] = true/on/1

$params['person_lead_party[no_phone_soliciting]'] = true/on/1

$params['person_lead_party[no_email_soliciting]'] = true/on/1

$params['person_lead_party[no_post_soliciting]'] = true/on/1

Looking at the web lead form Workbooks produces it seems the correct value is org_lead_party[no_phone_soliciting] but they all return the 'following form values were not recognised' error. In the php example that updates a person record the value is simply 'no_phone_soliciting' but presumably different in the context of a sales lead.

Any help would be appreciated.

Workbooks Support Posted: Tue, 08.11.2011 - 17:48

Hello Antony

Unfortunately this isn't possible just yet.  I have logged an enhancement to get this addressed.  

In the meantime you could create a custom field to hold these values and use Custom Form Layout to hide the built-in fields.  

With the advent of the Process Engine feature (about a month away) you could also automatically move values from one field to the other if necessary.  A bit clunky but it will work.