Answers.Body: <p>You could set up a Profile as you can specify where people go when they submit it.</p>
  <p>therefore you should be able to set Profile A to redirect to Profile B on submission.</p>
  <p>I expect this will work 'as is' for logged in users.</p>
  <p>There would be a problem if you send someone to Profile A via a link with a checksum as the checksum will 'expire' before they get to Profile B, hence they would be submitting that form as 'anonymous'. if that daisy-chaining the profiles is a requirement, you would need a customisation so the the 'session' that is opened on Profile A is extended to cover Profile B</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-08-24T19:43:16.583Z
Answers.LastActivityDate: 2021-08-24T19:43:16.583Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I'm trying to set up a form for contacts to update their own data via our Joomla frontend.  However, I ran into an unexpected problem when I tried to add a second multi-record custom fieldset to a profile:</p>
  <p>&quot;You cannot configure multi-record custom fields belonging to different custom sets in one profile&quot;</p>
  <p>Does this mean I have to create TWO profile edit forms if I want my users to be able to update all their data via the frontend?  I'd really prefer all the frontend data entry for the user in one form, not have to break it up.  Is there any other way around this?</p>
  <p>System deets:  Joomla 3.9.26, CiviCRM 5.37.1</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-25T19:50:22.663Z
Comments.Text: can you confirm what entity eg Contact, Individual, Contribution etc these fieldsets are being used on
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-25T19:51:33.117Z
Comments.Text: and/or set up a really simple example on eg dmaster.demo.civicrm.org so you can compare and others can take a look
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-26T08:21:25.690Z
Comments.Text: This is a custom contact type, a subtype of Organization.  I'll set up something on the demo and post here when completed.
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-26T08:38:38.730Z
Comments.Text: So of course I'm not getting this error on the demo :-(  I've set up two multi-record custom fieldsets (Multi-Record Fieldsets 1 and 2) for the Organization-Team contact type, and successfully created a profile "Edit Multi Record Fieldsets" with all fields from custom fieldsets included.
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-26T08:39:26.513Z
Comments.Text: In the process now of trying to figure out what's different between demo setup and mine.  Differences I already am aware of:  
  Demo = Drupal, My System =Joomla
  Demo version=5.39.alpha1, My version=5.37.1
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-05-26T10:45:41.223Z
Comments.Text: I'm stumped.  I've found the error in /CRM/UF/Form/Field.php line 785, and indeed there's a check "if profile already has a different multi-record custom set field configured".  So I don't know why it's actually working in the demo?
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-18T20:56:54.570Z
Comments.Text: it may not be a great workaround but iirc we have 'daisy-chained' profiles together in the past, so it seems like a multi-page form - might be a thought?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-19T11:06:31.997Z
Comments.Text: Interesting suggestion petednz -- how exactly would that be done?
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-19T19:30:50.670Z
Comments.Text: i may have misspoken - i checked what we have done previously and it was to ensure that if someone used a checksum to do a renewal, they could then click through to a second profile after submitting the form, and 'keep the session open'. i don't see why a similar approach could not be done from one Profile to another.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-23T08:55:21.913Z
Comments.Text: Hmm ok, sounds good, but not sure if I'm following.  I don't understand the mechanics of "clicking through and keeping the session open". Is this just customizing one profile to include a link to the second?  But how does the data submission work?
Comments.UserDisplayName: minbori
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-23T19:40:54.710Z
Comments.Text: when you set up a Profile you can specify where people go when they submit it. therefore you should be able to set Profile A to redirect to Profile B on submission. I expect this will work 'as is' for logged in users. problem is if you send some to Profile A via a link with a checksum, the checksum will 'expire' before they get to Profile B, hence they would be submitting that form as 'anonymous'. assuming that is not acceptable, you would need a customisation so the the 'session' that is opened on Profile A is extended to cover Profile B. hth
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-08-24T09:29:47.443Z
Comments.Text: Ah ok, so this would be simple forwarding to a separate profile on submission.  In this case Checksums aren't needed, as we don't use personalized links for these profile forms.  Not the prettiest workaround, but should do the job.
  
  Thanks so much for your help and patience!  Do you want to post this as an answer so I can award you the bounty points?
Comments.UserDisplayName: minbori
Tags: <custom-fields><profile><multi-record>
Title: Is it really not possible to have two multi-record custom fieldsets in one profile?
ThreadText: # Is it really not possible to have two multi-record custom fieldsets in one profile?
  
  (Asked by: username_0 on 2021-05-25)
  
  I'm trying to set up a form for contacts to update their own data via our Joomla frontend. However, I ran into an unexpected problem when I tried to add a second multi-record custom fieldset to a profile:
  
  "You cannot configure multi-record custom fields belonging to different custom sets in one profile"
  
  Does this mean I have to create TWO profile edit forms if I want my users to be able to update all their data via the frontend? I'd really prefer all the frontend data entry for the user in one form, not have to break it up. Is there any other way around this?
  
  System deets: Joomla 3.9.26, CiviCRM 5.37.1
  
  **Tags:** custom-fields, profile, multi-record
  
  > **Comments:**
  > **username_1**: can you confirm what entity eg Contact, Individual, Contribution etc these fieldsets are being used on  
  > **username_1**: and/or set up a really simple example on eg dmaster.demo.civicrm.org so you can compare and others can take a look  
  > **username_0**: This is a custom contact type, a subtype of Organization.  I'll set up something on the demo and post here when completed.  
  > **username_0**: So of course I'm not getting this error on the demo :-(  I've set up two multi-record custom fieldsets (Multi-Record Fieldsets 1 and 2) for the Organization-Team contact type, and successfully created a profile "Edit Multi Record Fieldsets" with all fields from custom fieldsets included.  
  > **username_0**: In the process now of trying to figure out what's different between demo setup and mine.  Differences I already am aware of:   Demo = Drupal, My System =Joomla Demo version=5.39.alpha1, My version=5.37.1  
  > **username_0**: I'm stumped.  I've found the error in /CRM/UF/Form/Field.php line 785, and indeed there's a check "if profile already has a different multi-record custom set field configured".  So I don't know why it's actually working in the demo?  
  > **username_1**: it may not be a great workaround but iirc we have 'daisy-chained' profiles together in the past, so it seems like a multi-page form - might be a thought?  
  > **username_0**: Interesting suggestion petednz -- how exactly would that be done?  
  > **username_1**: i may have misspoken - i checked what we have done previously and it was to ensure that if someone used a checksum to do a renewal, they could then click through to a second profile after submitting the form, and 'keep the session open'. i don't see why a similar approach could not be done from one Profile to another.  
  > **username_0**: Hmm ok, sounds good, but not sure if I'm following.  I don't understand the mechanics of "clicking through and keeping the session open". Is this just customizing one profile to include a link to the second?  But how does the data submission work?  
  > **username_1**: when you set up a Profile you can specify where people go when they submit it. therefore you should be able to set Profile A to redirect to Profile B on submission. I expect this will work 'as is' for logged in users. problem is if you send some to Profile A via a link with a checksum, the checksum will 'expire' before they get to Profile B, hence they would be submitting that form as 'anonymous'. assuming that is not acceptable, you would need a customisation so the the 'session' that is opened on Profile A is extended to cover Profile B. hth  
  > **username_0**: Ah ok, so this would be simple forwarding to a separate profile on submission.  In this case Checksums aren't needed, as we don't use personalized links for these profile forms.  Not the prettiest workaround, but should do the job.  Thanks so much for your help and patience!  Do you want to post this as an answer so I can award you the bounty points?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-08-24. Score: 2 | Accepted answer
  
  You could set up a Profile as you can specify where people go when they submit it.
  
  therefore you should be able to set Profile A to redirect to Profile B on submission.
  
  I expect this will work 'as is' for logged in users.
  
  There would be a problem if you send someone to Profile A via a link with a checksum as the checksum will 'expire' before they get to Profile B, hence they would be submitting that form as 'anonymous'. if that daisy-chaining the profiles is a requirement, you would need a customisation so the the 'session' that is opened on Profile A is extended to cover Profile B
  
  
  ---
  
  