![]() ![]() You will need to add the flow where you want it to appear. Let’s call it Create a New Contact and Associated Files.īest practice tip: Provide a description so you and other/future admins know what this flow is for. Debug the flow to ensure it is working as expected. Now, we need to connect the flow elements to match the screenshot below. This will take the user to the contact record page.) We need to create a text template to store the contentdocumentid’s file name and extension. This is how that flow resource would be configured.ī. We need to create a v ariable resource to store the newly created contactId to relate the files to.īest practice tip: Provide a description so you and other/future admins know what this flow resource is used for. In the flow, we would configure the following flow resources.Ī. Click on “ New Flow.” Select Screen Flow. In Lightning Experience, it is found under Process Automation | Flows. However in this use case, we only expect to get a handful of files to associate to the contact so the likelihood that we will hit a DML limit is slim.ġ. *Note: Yes, having DML actions within a loop is frowned upon. This flow will: (1) show a screen for the user to provide the contact first and last name, (2) creates the contact, (3) show a screen with the file upload component, (4) query content document link object for the ContentDocumentIds associated to the contact, (5) take each ContentDocumentId through a loop, (6) get the ContentDocument information*, (7) assign a text template to a variable and (8) show the contact and file information on a screen with the ability to upload additional files or access the record link directly. ![]() The automation solution (screen flow) looks like this: You can view more information on this object in the SOAP API Developer Guide.įor our purpose, we are interested in two fields: Title (the title of the document) and File Extension (File extension of the document). You can view more information on this object in the SOAP API Developer Guide.įor our purpose, we are interested in two fields: LinkedEntityId (the ID of the linked object) and ContentDocumentId (the document Id).ĬontentDocument represents a document that has been uploaded to a library in Salesforce CRM Content or Salesforce Files. They are stored in several related objects but the two we will focus on are ContentDocumentLink and Content Document.ĬontentDocumentLink represents the link between a Salesforce CRM Content document or Salesforce file and where it’s shared. Let’s take a look at the data schema for Files. ![]() Then, she was able to determine that she is able to get this information in flow to show back to the users post upload. Solution: Addison had to first understand how Files were stored in Salesforce. She would like give her team the ability to quickly create a new contact and associate files to the contact and review the files that were uploaded. Samantha Smith is the Operations manager. Learn how to query the objects to retrieve the file’s filename and extension for use in flowīusiness Use Case: Addison Dogster is the system administrator at Universal Containers.Learn part of the data model for Salesforce Files.Here are a few lessons learned from implementing this use case: This can be achieved using OOTB flow by querying the documents, assigning the file title and extension to a text template adding it to a variable and then displaying that variable on a flow screen. ![]() Those flownatics who have used the OOTB file upload component know once the files are uploaded to the screen flow, that the files are not shown back to the user as a confirmation of the files uploaded. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |