Skip to main content

My journey on converting Attachment to Files in Salesforce

Everyone know that soon Salesforce will remove related list of Attachment & Note in Page Layout(implementation expected in Winter'18). This is indicate that we should start using Salesforce Files that have better features especially for sharing.

I started researching on this exercise somewhere in 2016 and I feel very grateful that I found a very good tool developed by Douglas C. Ayers.I have been testing the tool  in my organization and thanks to him because this app helps a lot of organization 😃.

I am writing here to share experience. I am happy to inform that we completed our conversion successfully.These are few steps that perhaps you find it useful.Bear in mind that this approach may not suitable for you.Please do some research before implementing it.
  1. Refresh UAT with the latest Production data , install the app and run a lot of testing till you gain confidence.We hit the Content Publication Limits Exceeded which is annoying because we know our total Attachment is not even reach 200000.So we called Salesforce and it turned up they set it to 25 000 as default.So it's good to give them a call if you know that you should not hit the limit.
  2. Install to Production and make sure your setting it based on your need.
  3. Before we run , we need to plan conversion properly and to do so we need a report.Data loader can be used to retrieve it.I found that converting to Excel is very useful.Basically you may want to know how many object that have Attachment ,how many Attachment that we need to convert,ParentId etc. The simple query like below might be helpful
  4. Select Id,ParentId,Parent.Type,OwnerId ,Owner.IsActive from Attachment
  5. I just get complicated by creating visual force which is something like below.I labeled ParentType as 'Unknown' if the field value is null. 
  6. Decide which object that we want to convert, we may want to skip Unknown or 00X.Also we might want to put the sequence on which object that we should convert first.I prefer this approach because we can easily reduce the risk if something went wrong.We might want to start converting the object that has less Attachment first.
  7. ObjectTotal AttachmentNeed to convertSequenceConvertedRemark
    Marketing Support524Y2
    Account Plan4Y1

  8. Before start converting in Production, communicate with user.Ensure that they are aware on what happen to their Attachment and educate them about Files related list that they are going to see  in Page Layout once the conversion is completed.
  9. I copy ParentId  from the  query in previous step and use Excel to remove duplicate.For example, I copy ParentId of Opportunity and paste it into Excel and remove duplicate.We want to have unique parentId. As you can see, instead of running automate conversion for all, I manually paste the ParentId per object.
  10. Once the job is completed, I manually remove Attachment related list from Page Layout and replace it with Files related list.This will avoid user to keep uploading old Attachment in future.
  11. The job is faster that I expected. Once it completed, I checked Convert Attachment to Files log just in case there an error.Luckily we faced no error.
  12. Once I finished converted all of Attachment for object that we planned, I go to option Automate Conversion and run the schedule job in case there  old Attachment left over. We decided to run the schedule until end of this year.

  13. That's all. I hope you find this tips helpful.


  1. Additional info:
    1- I used version 1.2
    2-In setting, I choose keep Attachment because if something happen, we can simply retrieve it back.We plan to keep the Attachment until we completely confident to delete it.
    3-Also , I choose option Share the files with all users who have access to the Attachment's parent record.


Post a Comment

Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {