![]() ![]() It’s worth mentioning that there are advanced admin tools out there to help the experienced admin navigate this process the IDE and the Jitterbit Cloud Data Loader for Salesforce both deserve a shout-out here. ![]() Thankfully, back in the Winter ‘16 release, Salesforce gave us access to these fields through tools that can make API changes, like Salesforce Data Loader. ![]() They are populated automatically by Salesforce whenever a record is created or edited. Rather, they can only be changed by the system itself. Now that we know what audit fields are, and we know they can be incredibly useful, how do they work? These fields are set through the API (application program interface) only this means that you cannot click on the field in the user interface and change them. Preserving the CreatedDate helps you understand how much and for how long different kinds of students need tutoring before they can successfully pass the GED. Take this use case for example: a nonprofit gives clients tutoring to pass their GED, and tracks these tutoring events, GED pre-assessments, and GED test attempts. For nonprofits using Salesforce to track program data like key client interactions, achievements, or other events, audit field data can give you longitudinal insight that can validate your theory of change model. In this use case, preserving the CreatedDate or the LastModifiedBy can give you insights into your sales cycle, the effectiveness of your up-sell or cross-sell strategies, and the speed and efficiency of your customer support efforts.įor the nonprofit, the value goes beyond just capturing donor giving patterns. In the traditional sales model of a for-profit firm, this can look like when opportunities or cases are created over time, especially relative to their close date. But sometimes audit data provides critical insights into how your instance has changed over time, or even more importantly, how effective your organization is at whatever it’s trying to accomplish. It may not matter terribly when a customer or a donor’s record was created in Salesforce because you originally imported it from some other legacy system anyway. In some cases, this data may not be that useful to you. These fields tell you important things ABOUT your data: who created this record in the system and when? Who modified last? When did that modification take place? On the lead object, you have a few other fields that capture important audit data about your lead and its conversion, but we’ll mostly be talking about these four. So what is audit field data, why should you care, and how can you preserve it? What Are Audit Fields and Why Do They Matter?Īudit Fields in Salesforce are special fields that track information about your records that can be valuable for audit purposes. In some cases, this data is valuable in painting a picture of your org’s creation and usage over time, and you may not want to lose it. One of the major drawbacks of a data migration is that you can lose a lot of the “audit field” data in the process. ![]() In these cases, a migration of the old data to a new org can make it easier to monitor progress, onboard new users, and maintain data integrity to build user trust in the new system. One situation we see often at Arkus is a total re-think of an instance’s data model in an effort to make it more efficient or effective. Sometimes the opposite happens, and firms split up, splitting up their Salesforce instances as well. Why might you do this? Your firm may have been purchased by another, and you need to merge your Salesforce orgs. From time to time, it is necessary to migrate your Salesforce database - in part or in whole - between two instances of Salesforce. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |