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

Deleting Location Type should warn about loss of related contact data

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.6.8
    • Fix Version/s: 4.6.12
    • Component/s: None
    • Labels:
    • Documentation Required?:
      User and Admin Doc
    • Funding Source:
      Contributed Code

      Description

      Dave - eileen said i should put in as a ticket. Client recently had a catastrophic loss of data. Eventually figured it was due to an inadvertent/unintended deletion of a Location Type.

      We haven't had it confirmed yet but assume client saw this

      WARNING: Deleting this option will result in the loss of all location type records which use the option. This may mean the loss of a substantial amount of data, and the action cannot be undone. Do you want to continue?

      but did not 'compute' - and yes who bothers to read things on screen.

      But I took a re-read of it and realised that it did not explicitly say. "For example any Email, Phone or Address that uses this Location Type will be deleted."

      or perhaps you have a better idea to better ensure an admin understands the scale of destruction they might be about to unleash

      An awesome solution would be to put up a count of how many of each of Email, Phone etc was about to be deleted but doubt such a change could happen without funding.

      Any thoughts on at least a wording improvement? I think the current "loss of all location type records" may be the sort of wording that makes some users eyes glaze over.

        Attachments

          Activity

            People

            • Assignee:
              palantejon Jon K Goldberg
              Reporter:
              peted Peter Davis
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: