If using the API to routinely purge databases it would be useful to be able to specify a folder ID where the lists of purged records should be created. These could then more easily be manually deleted, rather than navigating a complex, nested folder structure to identify them. Alternatively consider a new "deletedatabase" API which allows a search string to be passed or a parameter to prevent the creation of a purge list.
How will this idea be used?
Standard contact expiry functionality is based on the date the contact was added to the database. We base purging on the contact Last Modified date. To support this we use the PurgeData API call, fired from Unica as part of regular data refreshes. By creating all of the Purge lists in a central location these can be more easily identified for manual deletion. |
|
What is your industry? | Non-Industry Specific |
What is the idea priority? | Medium |