Delete Fakes

#Participants - This feature will allow you to delete any Participant, Entity, or POS element with the name of “Fake.”

Updated over a week ago

This feature will allow you to delete any Participant, Entity, or POS element with the name of “Fake.” This is a helpful way to delete any “Fake” or “Test” data which may have been used during Implementation/Training. The word the software looks for is “Fake” and only “Fake” – names such as “Fakest,” “Faker,” etc. will not be recognized by this feature. This feature is Site-specific; please note that once deleted, this data cannot be reinstated.

  • Participants must have the first or last name Fake.

    • Note: If a fake Participant had any appointments entered into a user's calendar, the appointments will need to be deleted individually before the Delete Fakes feature can remove them.

  • Entities must begin with the word Fake

    • For Entities marked as "Is Individual", the first name of the entity must be Fake. This change in name may not take effect unless edited in the Contacts tab of the View/Edit Entity page (as opposed to the Entity Information tab).

  • POS elements must begin with the word Fake.

All data associated with the fake Participants, Entities, and POS elements will be deleted. This includes any Efforts, Assessments, TouchPoint responses, Workflows, etc. that have been attached to the Participants or Entities.

You can update and write over the existing name of any Participant, Entity, or Point of Service with the word "Fake" if it was not added as Fake originally.

In-Depth Instructions

Step 1 – On the Navigation Bar, click "Site Administration". Then select "Delete Fakes".

Step 2 – Click the box for the type of fake that you would like to be deleted.

Step 3 – Click "OK".

Note: Depending on how many Fakes are in the database and how many records (TouchPoint responses, Program enrollments, referrals, etc.) are associated with them, Delete Fakes can be a very resource-demanding feature to execute. When deleting more than a few Participants at a time with many dependent records, Bonterra recommends using this feature during non-peak hours so the process does not slow down your Users’ experience in other areas of the software.

Did this answer your question?