{"id":222,"date":"2014-12-31T06:45:07","date_gmt":"2014-12-31T01:45:07","guid":{"rendered":"http:\/\/learnsf.wordpress.com\/?p=222"},"modified":"2014-12-31T06:45:07","modified_gmt":"2014-12-31T01:45:07","slug":"how-to-implement-edit-locking","status":"publish","type":"post","link":"https:\/\/blog.felineflock.com\/index.php\/2014\/12\/31\/how-to-implement-edit-locking\/","title":{"rendered":"How to implement edit locking"},"content":{"rendered":"

When 2 users start\u00a0editing the same record, the first user who saves<\/strong> the record wins, and the other user will lose the changes with an error message similar to “The record you were editing was modified by *someone*<\/em> during your edit session. Please re-display the record before editing again.”<\/strong><\/span><\/p>\n

This can be an inconvenience: \u00a0if an integration process updates the records, any\u00a0user who opened the record for editing will lose his changes if he\/she doesn’t hit Save\u00a0quick enough.<\/p>\n

To lock the record when the first user opens it\u00a0for editing, you can implement the following 4 steps:<\/p>\n

    \n
  1. Create a date\/time field “Last Edit Date Time” – this field will store the date and time when the record was opened for editing.<\/li>\n
  2. Create a validation rule to prevent any updates to the record during the period when it is locked (a period of 5 minutes so that no one\u00a0can keep the record locked indefinitely).<\/li>\n
  3. Create a Javascript “Edit” button that updates the\u00a0“Last Edit Date Time” field and redirects to\u00a0the record editing page.<\/li>\n
  4. Replace the standard Edit button on the page layout with the custom Edit button.<\/li>\n<\/ol>\n

    First we create the field (this example uses Accounts):<\/p>\n

    \"Screen<\/a><\/p>\n

    Then we create the validation rule as follows:<\/p>\n

    AND( NOW() – PRIORVALUE( Last_Edit_Date_Time__c ) < ( 5\/1440 )
    \n\/* locks for 5 minutes *\/
    \n, PRIORVALUE( LastModifiedById ) != $User.Id )<\/p><\/blockquote>\n

    The first line in this validation rule calculates how long since the last time the record was locked and compares the number to 5\/1440 (5 minutes divided by the number of minutes in a day).<\/p>\n

    If it is less than 5 minutes, then, on the second line, it checks whether the user doing the update is the same user that set the edit lock.<\/p>\n

    If it is the same user, it will allow the update to go through, but if it is a different user, it shows an error message. I chose the error message to be “The record is locked for editing by another user (5 minutes duration).”<\/p>\n

    Lastly, we need to create a new Button on Account to run Javascript code that updates the\u00a0Last_Edit_Date_Time__c and redirects to the\u00a0the account standard editing page:<\/p>\n

    \"Screen<\/a><\/p>\n

    This is the Javascript code:<\/p>\n

    {!REQUIRESCRIPT(\"\/soap\/ajax\/29.0\/connection.js\")}<\/p>\n

    \/\/ prepare account for updating the last edit date time
    \nvar anAccount = new sforce.SObject( \"Account\" );
    \nanAccount.id = '{!Account.Id}';
    \nvar dtNow = new Date();
    \nvar nowInJSON = dtNow.toJSON();
    \nanAccount.Last_Edit_Date_Time__c = nowInJSON;<\/p>\n

    \/\/ update the account
    \nvar result = sforce.connection.update( [ anAccount ] );<\/p>\n

    window.location.href = '\/{!Account.Id}\/e';<\/code><\/p><\/blockquote>\n

    Now we need to just remove the standard Edit button and place the new custom Edit button on the page layout.<\/p>\n

    \"Screen<\/a><\/p>\n

    This makes it so that if an user clicks Edit, it will set the Last Edit Date Time. The validation rule will prevent updates to the record from anyone else during the next 5 minutes. If another user attempts to save the same record, the validation rule will cause this error message to\u00a0appear:<\/p>\n

    \"Screen<\/a><\/p>\n

     <\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    When 2 users start\u00a0editing the same record, the first user who saves the record wins, and the other user will lose the changes with an error message similar to “The record you were editing was modified by *someone* during your edit session. Please re-display the record before editing again.” This can be an inconvenience: \u00a0if […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[13,18],"tags":[],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-no-category","category-validation"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts\/222","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":0,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts\/222\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/media?parent=222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/categories?post=222"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/tags?post=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}