Export and Import | EvoluteMessage

Import and Export

Available on version 2.3.3+
Package Tiers: Freemium, Basic, Advanced.

This article will show how to export and import Templates/Messages/Data Sources from one org to another org. This is useful when you want to move records from Sandbox to Prod or vice versa.

Currently we can only export/import one component each time, we don't have yet a way to export all the components at the same time and its dependency.

The export button is available on each component in the Dashboard. Click on the 3 dots and you will see the Export button.

Example:

Now, it will prompt for you a popup where you can click on the link to download the .csv. The .csv is in a format where you can use the import from the EvoluteMessage or the Salesforce Wizard Import.

Once, you click on the link .csv, it will trigger the download and you can save that anywhere.

Import Message

Now that we have the .csv file, we have 2 options to import that back into Salesforce, which are:

- EvoluteMessage Import

- Salesforce Data Wizard

The EvoluteMessage current has its limits where we cannot update records, we can only insert records.
Salesforce has no limits, you just need more clicks to import and you need to know what you want to do if it is update or insert a new record.

Let's show how the Import in EvoluteMessage works.

If you have exported a message, you need to go to EvoluteMessage Dashboard to import, if you have export a Data Source, you need to go to EvoluteMessage Data Source Dashboard to Import.

Here we are at the Message Dashboard, where we can see the import button.

Click on it, and it will show a popup. Click on the icon to select a file.

Click on the icon to select a file.

Once you have drag a file or selected a file, you can click on import.
If you look for the code that you have imported, you should see the new message in there.

As you can see above, I have imported the same message twice, and as we have said, we don't have an option to update a message on EvoluteMessage yet.

In this case, for the update, you actually would need to delete the old message and leave only the new message. We should not have 2 evm-code with the same code.

In Data Source, we actually thrown an error, which forces you to delete first then import.

Currently on version 2.3.3, if you delete a message, you will need to go to your Page where you drag and drop the message and update the message, because the Id has changed.

Limitations

Here are some limitations that I mention before and I will leave here as bullet point.

1 - We cannot update Message or Data Source
Work around:

For Message you will need to delete the old Message, then you will need to go to each Page and link that again.

For Data Source, you will be blocked to create 2 Data Source with the same code, so you can delete that, and just import the new Data Source, you don't need to link with your messages because we are using the Data Source Code(ds-###) to link the message with the Data Source.

2 - We don't import and export your Page metadata

When you drag and drop a Simple or Advanced Evm Component into your Lightning Page or Digital Experience Page, we are not responsible to export and import that. We suggest you to use the salesforce change set to move your pages which would move the Evm Components(Simple and Advanced). Although currently, in v2.3.3. we have the Id on those component and if you move from one place to another you will need to link the message to the right id(message) into the target org.

2 Improvements we will do soon on this:

1 - Change from Id to Code, so you can move metadata easily and as long as the evm code is on the org, it will work.

2 - Track into the Message, where the message is hosted, currently into the Message, you have no visibility which page the message was added, if it iwas in a lightning page or digital experience. We intend to enable a track where you can see where the message was added.