CiviCRM Community Forums (archive)

Hi,

Trying to use Webform CiviCRM for the following requirement...

- Create Individual with "Employee of" + optionally another relationship to an existing Organization, chosen with an autocomplete field. The user interface should show only the optional additional relationship type, not "Employee of".

Tried following setup:

Contact 1: Person (Individual)
- the new Ind. being created.
- has Current Employer field set to Company; this field is an autocomplete with:
    - Set default contact from: Relationship to Person,
    - Specify Relationship(s): Employer of Person,
    - Filter - Type of Organization: Company.
Contact 2: Company (Organization, subtype Company)
- has Relationship to Person: User Select (non-mandatory field with the 2 additional relationship type options).

So essentially, trying to use two different means to create the relationships: one for Employer of, one for the optional additional user-selectable relationship.

Result: only the "Employer of" relationship is created.

Would this be expected to work in the way described? If not, is there a better way? A hacky option might be to make use of the facility to have multiple relationship types and do some meddling with the UI to hide "Employer of" from the user but still have it created behind the scenes. But it would be nice to avoid that sort of shenanigans.

Many thanks,

Dave

Hi Coleman,

Many thanks for your helpful response.

1. Yes it ought to work as you describe. I'm not sure why the additional relationships would not be created, but it could be a bug. Can you check your drupal watchdog log?

Thanks for confirming that this method should work, that's always useful to know! The following PHP notice is logged when the Employer autocomplete is filled in:

Notice: Undefined offset: 1 in wf_crm_webform_base->loadContact() (line 114 of .../webform_civicrm/includes/wf_crm_webform_base.inc).
I added some extra watchdogs in loadContact() and found:

loadContact: $contact['number_of_relationship'] = '1'

loadContact: before $this->getRelationship, $c = '2', $r = '1', $cid = '15233', $types = Array ( )

loadContact: before $this->getRelationship, $this = wf_crm_webform_ajax Object
(
...[snip]...
    [id:protected] => Array
        (
            [cid] => Array
                (
                    [2] => 15233
                    [0] => 15233
                )
        )
...[snip]...
)
So the "Undefined offset: 1 in wf_crm_webform_base->loadContact()" occurs because $this->id['cid'][$r] doesn't exist, where r = 1. $this->id['cid'] just has 0 and 2, both with the ids of the Company.

The only watchdog errors on submit are dozens of these from webform_conditional:
Notice: Undefined index: value in _webform_conditional_get_all_components() (line 662 of .../webform_conditional/webform_conditional.module).
There are no conditional actions on this form.

2. I don't think the backend option selection you described is needed in light of #1, but for the record, doing that sort of thing isn't really shenanegans with webform_civicrm. It's a build-in feature. On the admin form (civicrm tab) you can select for relationship type both "user select" and additional options. The ones you check on the admin form will be hidden from the front-end webform and automatically submitted in addition to whatever the user chooses. This works with any multivalued field. If you click the help bubble next to a multivalued field, it will tell you so

Thanks, also very useful to know. I failed to mention one further requirement: the Org should be set as the Individual's current employer.

I tried method 2 by making the following changes to the webform:

- In Webform tab, settings for Employer field, changed: "Set default contact from" from "Relationship to Person" to "None".
- In Civi tab, Contact 2 (Company), Relationship to Person, changed from single-select "User Select" to multi-select with both "User Select" and "Employer of" selected.
- In Webform tab, expected available options for "Relationship to Person Relationship Type(s)" field to have changed (i.e. "Employer of" not to be available), but there was no change. This field was set for static options but I changed that to dynamic to see if the available options had changed.
==> Re-tested, same problem as original set-up: only "Employer of" relationship created. The same PHP notice occurred when completing the Employer field.

- In Webform tab, deleted "Relationship to Person Relationship Type(s)" field.
- In Civi tab, Contact 2 (Company), Relationship to Person, again changed from single-select "User Select" to multi-select with both "User Select" and "Employer of" selected => this recreated field Relationship to Person Relationship Type(s).
- In Webform tab, "Relationship to Person Relationship Type(s)" field, set to single select with desired static options (as we want the labels to differ from the relationship type names).
==> Re-tested, same problem as original set-up: only "Employer of" relationship created. The same PHP notice occurred when completing the Employer field. :-(

EDIT: webform_civicrm version is 7.x-4.5, Civi 4.4.1 .

Cheers,

Dave

Hi Coleman,

You should uninstall and remove webform_conditional - it is not compatible with webform v4, which has a built-in conditional feature.

Thanks, I have disabled, uninstalled and removed the code of webform_conditional. Re-tested and the behaviour is still the same: only the "Employee of" relationship is created.

Cheers,

Dave J

I tried and failed to reproduce the issue.
Screenshots attached showing everything working normally.

Hi Coleman,

A quick follow-up question if I may.

When using the webform to edit an existing individual with 2 existing relationships to an existing company (employee + second relationship type), the relationship type field pre-populates with the second relationship type - great. (The relationship type field is a single select with static options, which excludes employer, which is set via Current Employer in Contact Fields.)

If the user un-selects the second relationship type on the webform & saves, the desired behaviour is that the second relationship should be removed. This doesn't happen, both relationships remain. Would you expect it to be removed?

Regards,

Dave J