Details about this thread
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 294 subscribers
  • Views 1273 views
  • Users 0 members are here
Related content from around SugarClub

Best Practice: Deleting records but not customizations

Kristjan Geir Mathiesen

Hi all.

Ok, we´ve got an instance that has been a test and development instance. Now we want to copy it and make it the production environment. However, it´s "full" of all kinds of records.

What is the best way to clean out all those records, yet keep the customization?

I.e. we need to "reset" the instance without loosing the customization

Thanks,

KGM

Parents
  • 0

    You'd typically want to preserve the following tables:

    acl*

    team*

    fields_meta_data

    relationships

    users*

    workflow*

    pmse*

    schedulers

    config

    There is an off chance that a specific type of customization requires data from another table, such as dashboards, but the above list should contain the vast majority of the customization related data.

    It would likely be safer to identify the tables related to the modules containing data you wish to purge and then focus on deleting that data. 

Reply
  • 0

    You'd typically want to preserve the following tables:

    acl*

    team*

    fields_meta_data

    relationships

    users*

    workflow*

    pmse*

    schedulers

    config

    There is an off chance that a specific type of customization requires data from another table, such as dashboards, but the above list should contain the vast majority of the customization related data.

    It would likely be safer to identify the tables related to the modules containing data you wish to purge and then focus on deleting that data. 

Children
No Data