![]() ![]() Retrospective: Through the ability to automate actions when editing records (and not just creating) we can identify potentially dirty data in our existing database. Even if you allow the user to save the record, you can then see all the records that were flagged within a report, meaning that potentially dirty data can be found fast and effectively.Ĭustomisation: You can set up your duplicate and matching rules so that they match your own organisations, the terminology and the business process that sit behind them. So, when one of your users goes to create a record that shares data with a record already entered on Salesforce, you can get your duplicate rule to flag its existence to the user before they go on to save the record - or you can get Salesforce to block it entirely from being able to be saved. In Salesforce's own words, it enables you "to control whether and when you allow users to create duplicate records inside Salesforce customise the logic that's used to identify duplicates and create reports on the duplicates you do allow users to save". ![]() So, what does the new native tool provide? I would imagine there are now a few furrowed brows and nervous looks being exchanged by those providers as they look at this new tool and its implementation. And so it proved, as a micro-industry sprang up to manage duplicate data in Salesforce with multiple apps on the AppExchange being developed to solve this problem for you. For me, there is a lot of vulnerability in all of that to be able to rely on it for your data integrity. You are reliant on your user remembering to search, getting the search terminology right/accurate, and being diligent enough to do so every time they are creating a new record. This approach can lead to PICNICs (PICNICs? Problem In Chair Not In Computer - User Error. Historically, we relied on training our users to search for accounts, contacts, etc. For those of us that live, breathe and preach data integrity in our organisations, seeing the ease with which Salesforce has allowed users to enter data with precious few controls causes us sleepless nights and well-bitten nails! The Salesforce Spring '15 release saw the introduction of Duplicate Management and we think its a cracking piece of functionality - here we investigate why.įor a long time, duplicate or 'dirty' data in Salesforce has been the bane of a System Administrator's life. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |