Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-21643

Profile confirmation page shows the wrong values for multi-value custom data

    Details

    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Paid Issue Queue
    • Verified?:
      No
    • Overview:
      Hide
      When you submit a profile that uses multi-value custom fields, the confirmation page shows the wrong data. So does the notification email. It shows the very first entry in the custom field multi-value data, rather than the most recent one. The same happens for notification emails.
      Show
      When you submit a profile that uses multi-value custom fields, the confirmation page shows the wrong data. So does the notification email. It shows the very first entry in the custom field multi-value data, rather than the most recent one. The same happens for notification emails.
    • How it works currently:
      Hide
      (tested on WP sandbox)

      1. Create a custom field set that allows multiple records (for an Individual, say)
      2. Create a field in this set
      3. Create a new contact record with test@test.com
      4. On this contact record, populate the custom field with an initial entry. Enter 'first data' or similar.
      5. Create a profile with a) an email address field b) this custom field
      6. Set the profile settings to 'update the matching contact'
      7. Go to the profile list on Civi, click 'more' and go to 'Use - Create mode'
      8. Enter 'test@test.com' and 'second data', and submit the form
      9. The confirmation page shows 'first data'.
      Show
      (tested on WP sandbox) 1. Create a custom field set that allows multiple records (for an Individual, say) 2. Create a field in this set 3. Create a new contact record with test@test.com 4. On this contact record, populate the custom field with an initial entry. Enter 'first data' or similar. 5. Create a profile with a) an email address field b) this custom field 6. Set the profile settings to 'update the matching contact' 7. Go to the profile list on Civi, click 'more' and go to 'Use - Create mode' 8. Enter ' test@test.com ' and 'second data', and submit the form 9. The confirmation page shows 'first data'.
    • How it should work:
      Hide
      1. Create a custom field set that allows multiple records (for an Individual, say)
      2. Create a field in this set
      3. Create a new contact record with test@test.com
      4. On this contact record, populate the custom field with an initial entry. Enter 'first data' or similar.
      5. Create a profile with a) an email address field b) this custom field
      6. Set the profile settings to 'update the matching contact'
      7. Go to the profile list on Civi, click 'more' and go to 'Use - Create mode'
      8. Enter 'test@test.com' and 'second data', and submit the form
      9. The confirmation page shows 'second data'.
      Show
      1. Create a custom field set that allows multiple records (for an Individual, say) 2. Create a field in this set 3. Create a new contact record with test@test.com 4. On this contact record, populate the custom field with an initial entry. Enter 'first data' or similar. 5. Create a profile with a) an email address field b) this custom field 6. Set the profile settings to 'update the matching contact' 7. Go to the profile list on Civi, click 'more' and go to 'Use - Create mode' 8. Enter ' test@test.com ' and 'second data', and submit the form 9. The confirmation page shows 'second data'.
    • Acceptance Criteria:
      The confirmation page and the the notification email show 'second data'.

      Description

      When you submit a profile that uses multi-value custom fields, the confirmation page shows the wrong data. So does the notification email. It shows the very first entry in the custom field multi-value data, rather than the most recent one.

      Note that the data does save correctly. It's just the display that is incorrect.

      If you configure a notification email, this also sends 'first data'.

        Attachments

          Activity

            People

            • Assignee:
              monish.deb Monish Deb
              Reporter:
              krypto Andrew West
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 3 hours
                3h
                Remaining:
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 1 hour, 30 minutes
                1h 30m
                Logged:
                Time Spent - 1 hour, 30 minutes Remaining Estimate - 1 hour, 30 minutes
                1h 30m