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

Changing "Used for" in Custom Field set should reset conditional fields to expected values.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: 4.6.4
    • Fix Version/s: Unscheduled
    • Component/s: Core CiviCRM
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Needs Funding

      Description

      A Custom set "Used for" contacts that has "Does this Custom Field Set allow multiple records?=enabled " and "Display Style= Tab". I then change it to be used for relationships. When saved I see that the display style remains unchanged (Tab), but it is not displayed when you add a relationship. Apparently the Overlay display was not prepared to support Tab.

      Expected behaviour is that the Custom set appears, either by supporting support for Tab or by resetting the Display Style to inline automatically where necessary. Same thing happens with "allow multiple records". Apparently not supported in all "Used for" choices. So when Used for is changed and then "allow multiple records" should be disabled automatically when it is not supported (when previously active, then still "Maximum number of multiple records" keeps appearing.

      Usually you don't change Custom field sets in production, but while prototyping, you still want thing to work as expected. The work around is to temporary change back to the previously "Used for" and then disable what is not supported.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ñull René Nieuwburg
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: