Introduction #
In the last section, we learned about how to import base 64 string data with attachment files stored in the Attachment object. And now, we learn how to import binary data with attachment files stored in the Content version object in Salesforce. In this section, we are learning about How to import binary data to ObjectContentVersion in Salesforce. About import to ContentVersion in Salesforce, We are doing the same as import to ObjectAttachment in Salesforces, but we use different mapping.
How to import binary data to Content Version #
Pre-require #
-Create MetaData provider and repository for the upload message type
-Connection destination and create an adapter
-Create Integration and Inbound Interface
Step1: #
We need to have a Repository to upload structure for do mapping. How to create a MetaData provider, repository, and upload the message type we can refer to the following guide https://docs.skyvva-dev.com/docs/skyvva-administration-guide-v2-41-lightning/repository/ for metadata provider.
[su_box title=”Note” box_color=”#2a8af0″ title_color=”#000000″] First, we need to upload the XML structure that is the same as the data we want to import to Salesforce. [/su_box]
-Go to Repository Detail and click the button Upload File.
-Choosing file type to upload and click Button save. which means we create Message Types.
-Scroll down to see Message Types.
Step 2:
#
We go to the Agent control board (old) to the connection destination. How to use the Agent control board (old). (Please refer https://docs.skyvva-dev.com/docs/tutorial-v2-41-lightning/how-to-use-agent-control-board/ ).
-Connection Destination in Agent Control board
Step3: #
Create an Adapter in the Agent control board (old), and We need the Adapter to transfer the data from one System to another system or computer. Here’s an example below.
-Go to Adapter on Agent Control Board (old).
-Click the New Button to create an Adapter.
-After that, fill in the name, type, direction, status, properties, and click the button save. Follow the example below.
#
Step4:
we need an Inbound Interface for import data to Salesforce.
-Create Integration and Inbound Interface with Message Types that we had uploaded.
-Put an adapter, MetaData Provider, Repository, Message Type, and click button save.
-We do mapping, which is a collection of key-value pairs where each unique key maps to a single value. (Please refer https://docs.skyvva-dev.com/docs/tutorial-v2-41-lightning/how-to-use-mapping/).
-We need to do formula on-field IsMajorversion.
• The example of mapping the below is about How to import Binary data into ObjectContentVersion in Salesforce.
-Double Click on the IsMajorVersion field. We do formula and write the word “false” and click Test Formula and save it.
[su_box title=”Note” box_color=”#2a8af0″ title_color=”#000000″] When we import binary data by content version that means the attachment has not existed in ObjContentDocument, So when we import Account with attachment make sure that attachment does not exist in ObjectContentDocument. Example: We want to Push data that has Account and Attachment, but the attachment had already in ObjectContentDocument, so when We processed Account will not have attachment because attachment already exists in ObjectContetDocument. [/su_box]
-After that, go to the Agent control board (old) =>Select Integration.
-Select the Interface tap, choose the interface, and click the Button PROCESS INTERFACE.
-Go to Monitor to see the result.
-Here are Accounts that imported.
Summary #
In this tutorial, we have learned about How to import base 64 string data to ContentVersion in Salesforce. There are four steps to import Binary data to ObjectAttachment in Salesforce such as upload structure for getting Message Types, Connection Destination, Create Adapter and create an inbound interface for mapping to make sure that Source name is ContentVersion. So this function is helpful for User who wants to import binary data to ObjectContentVersion in Salesforce. On the next page, we will learn How to import files to Account business by using ContentVersion.
