Like
Share
ReportMoving Pre-defined Dynamic Text in Customer Insights - Journeys
To address the challenge of how to move pre-defined dynamic text between environments, you have three effective options.
Picture 1. Data sample for Predefined Placeholder
This method is the simplest and most streamlined approach to import pre-defined dynamic text. If your business operates within multiple Business Units, it's the ideal choice.
In this method, we recommend the Out-of-the-Box (OOB) Import data - Import data in model-driven apps - Power Apps | Microsoft Learn.
Picture 2. OOB Import tool.
The Power Make Portal provides the import capability - Import or export data from Microsoft Dataverse - Power Apps | Microsoft Learn. Because this method does not support OwnerID field for import it's not the primary choice, you may use this option to import pre-defined dynamic text without assigning an owner. Understanding when and how to use it is crucial to make the most of this option.
Picture 3. Power Make portal Import tool.
For businesses that lack Business Unit (BU) scope requirements for export, the Configuration Migration Tool becomes the recommended choice. This tool offers advanced control over the import process and allows you to manage the import of pre-defined dynamic text effectively. Get a step-by-step guide on importing pre-defined dynamic text using this tool.
Pre-defined dynamic text in Dynamics 365 Customer Insights - Journeys is your key to highly personalized messages. It enables you to drive engagement and create tailored communications. However, to ensure that this level of personalization is consistent across different environments, you can leverage these options to move pre-defined dynamic text. Depending on your business structure and requirements, you can choose the method that aligns best with your needs, taking control of your pre-defined dynamic text and enhancing engagement and personalization in every communication.
Resources:
Dynamics 365 CI Journey ALM Best Practices: Getting Started
Introduction
Dynamics 365 Customer Insights - Journeys is designed to deliver highly personalized messages to your audience. The key to this personalization lies in pre-defined dynamic text, also known as placeholder text. These placeholders are automatically replaced with recipient-specific details when the message is sent, transforming generic communications into tailored experiences. Placeholder text is defined by environment, and some customers may prefer to establish these placeholders in a development or test environment before deploying them in production. Currently, this functionality is not included in Dataverse solutions by default. This means that you will need to move it using Content Lifecycle Management (CLM) to make it a seamless part of your solutionResolution
Personalize content using pre-defined dynamic text - Dynamics 365 Customer Insights | Microsoft Learn provides a comprehensive guide how to create, manage, use pre-defined dynamic text in personalization for Emails and Text.To address the challenge of how to move pre-defined dynamic text between environments, you have three effective options.
Data Preparation
When working with pre-defined dynamic text in Dynamics 365 Customer Insights - Journeys, there are a few key considerations you should be aware of:- Understanding Pre-defined Dynamic Text: Pre-defined dynamic text is a vital component that allows you to personalize your messages. It is a part of the Dataverse: Pre-defined dynamic text is allocated in Predefined Placeholder (msdynmkt_predefinedplaceholder) table in Dataverse;
- Creating Pre-defined Dynamic Text: If you need to create new pre-defined dynamic text, it's essential to do this directly within the Dynamics 365 interface. Don't attempt to create or set up new pre-defined dynamic text in an Excel or CSV file. This is because there are specific rules to follow during the creation of these records.
- Existing Custom Pre-defined Dynamic Text: If your organization already has custom pre-defined dynamic text, you should know how to manage and handle it within your source environment.
- Exporting Data: To work with pre-defined dynamic text effectively, you should be familiar with how to export data. These resources will help you learn more about this process:
- Importing Data: When working on data import file:
- The import should contain at a minimum: Namespace; Is Built In; Placeholder Label; Placeholder Type; Description; Owner; Placeholder description; Business Unit*;
- Column Considerations: While you shouldn't modify columns like Namespace, Is Built In, Placeholder Type, and Placeholder description, you can make changes to the Business Unit*, Owner, Description, and Placeholder Label if necessary.
- Managing Multiple Lines: If you need the same pre-defined dynamic text to be available for different Business Units*, you can easily achieve this by copying and pasting existing lines in your Excel or CSV file and then setting different Business Units* and owners for each line.
- Unique Description: It's important to note that Description (msdynmkt_description, which is the primary name column) must be unique. This means each description should be distinct; otherwise, you'll encounter errors during the process (Reason: Bad Request, Header x-ms-client-request-id ---, Predefined placeholder with this namespace and friendly name already exists.)
Picture 1. Data sample for Predefined Placeholder
Option 1: Out-of-the-Box (OOB) Import
This Option is recommended for Customers with Business Unite Scoping enabled.This method is the simplest and most streamlined approach to import pre-defined dynamic text. If your business operates within multiple Business Units, it's the ideal choice.
In this method, we recommend the Out-of-the-Box (OOB) Import data - Import data in model-driven apps - Power Apps | Microsoft Learn.
Picture 2. OOB Import tool.
Option 2: Power Make Portal - Import without Owner
Suitable for Specific Scenarios.The Power Make Portal provides the import capability - Import or export data from Microsoft Dataverse - Power Apps | Microsoft Learn. Because this method does not support OwnerID field for import it's not the primary choice, you may use this option to import pre-defined dynamic text without assigning an owner. Understanding when and how to use it is crucial to make the most of this option.
Picture 3. Power Make portal Import tool.
Option 3: Configuration Migration Tool
Recommended for Customers without BU Scope.For businesses that lack Business Unit (BU) scope requirements for export, the Configuration Migration Tool becomes the recommended choice. This tool offers advanced control over the import process and allows you to manage the import of pre-defined dynamic text effectively. Get a step-by-step guide on importing pre-defined dynamic text using this tool.
Conclusion: Harness the Power of Pre-defined Dynamic Text
Pre-defined dynamic text in Dynamics 365 Customer Insights - Journeys is your key to highly personalized messages. It enables you to drive engagement and create tailored communications. However, to ensure that this level of personalization is consistent across different environments, you can leverage these options to move pre-defined dynamic text. Depending on your business structure and requirements, you can choose the method that aligns best with your needs, taking control of your pre-defined dynamic text and enhancing engagement and personalization in every communication.
Resources:
Dynamics 365 CI Journey ALM Best Practices: Getting Started
*This post is locked for comments