When I have a Webform with CiviCRM enabled and have a contact and an activity on the webform. If I have the activity "Update Existing Activity" set to scheduled and completed. Then when I view the webform it is prefilling with the first activity of the correct type and status but the webform doesn't care if the activity is associated with contact 1 or not.

On submission of the form the activity gets moved to the Contact 1 and loses its association with its original contact.

The help button on the update existing activity field says it will update an activity if it is associated with the contact 1.

This is an problem that has appeared from doing the CiviCRM Core 4.6.18 upgrade, webform_civicrm version 4.15. I have checked on another site also using 4.6.18 (webform_civicrm version 4.14) and found the issue was repeatable. On a site with CiviCRM core 4.7.9 this issue is not found.

This issue seems similar to what was brought up in this issue https://www.drupal.org/node/2495199 but given it was a year old I wasn't sure if it was the same issue or just linked.

I have attached the node export of the webform I created to test this issue

CommentFileSizeAuthor
node-export of Webform testing 10661.txt11.72 KBgemma.potaka
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gemma.potaka created an issue. See original summary.

gemma.potaka’s picture

gemma.potaka CreditAttribution: gemma.potaka commented
Issue summary: View changes
petednz’s picture

petednz CreditAttribution: petednz commented
Priority: Normal » Major

setting to major since this is potentially degrading data.

yosefr’s picture

yosefr CreditAttribution: yosefr commented

I am having the same issue on my site.
In addition to that which was mentioned above when "Update Existing Activity" is enabled,
the activity date is set to a random date rather than today's date.

yosefr’s picture

yosefr CreditAttribution: yosefr commented

I just upgraded to civicrm 4.6.19 to see if that fixes it and it does not :(

gemma.potaka’s picture

gemma.potaka CreditAttribution: gemma.potaka commented

There is a recent commit that fixes this issue in 4.6.20. It is https://github.com/civicrm/civicrm-core/commit/e5f15ce2225c2a969e3c4b42d...

colemanw’s picture

colemanw CreditAttribution: colemanw commented
Status: Active » Fixed
pmoz’s picture

pmoz CreditAttribution: pmoz commented

Which CiviCRM versions should this fix be applied to?

petednz’s picture

petednz CreditAttribution: petednz commented

Gemma's comment said that it was a fix for 4.6.20

pmoz’s picture

pmoz CreditAttribution: pmoz commented

Thanks Pete. i saw that but didn't know if it applied to later versions as well. On one of our installs that is on 4.6.9, the Activity.php file does not have the patch in it.

Status: Fixed » Closed (fixed)

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