0

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

12
  • can you confirm what entity eg Contact, Individual, Contribution etc these fieldsets are being used on
    – petednz - fuzion
    May 25 at 19:50
  • and/or set up a really simple example on eg dmaster.demo.civicrm.org so you can compare and others can take a look
    – petednz - fuzion
    May 25 at 19:51
  • This is a custom contact type, a subtype of Organization. I'll set up something on the demo and post here when completed.
    – minbori
    May 26 at 8:21
  • 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?
    – petednz - fuzion
    Aug 18 at 20:56
  • 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
    – petednz - fuzion
    Aug 23 at 19:40
2

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

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.