Menu Close

Author: uk365guy

{Customer Insights} Refer to copies of emails on the timeline easily

uk365guy

Hello Everyone,

Today I am going to share my thoughts on how we can share copies of emails on the timeline easily on Customer Insights new feature.

Let’s get’s started.

In Dynamics 365 Customer Insights, you can now easily reference copies of sent emails in the interaction timelines. This feature allows you to gain deeper customer understanding and visibility into previously shared communication with your customers.

Here’s how you can access this functinality:

1. Enable Viewing Emails on the contact timeline:

Go to Settings and select Feature switches.

Enable the show exact copy of sent emails feature toggle in the contact timeline section.

2. View Previously Sent Emails:

From the left navigation bar, select Contacts.

Choose the specific contact for whom you want to view previously sent emails.

On the Timeline(Located in the center tile on the Summary tab), you’ll find all previous interactions, including exact copies of the sent emails.

This enhancement not only helps you find more personalized experiences but also improve overall visibility, and auditing.

Feel free to explore this feature and enhance your customer insights.

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Share this:

Customer Insights – capture responses from external, third-party forms

uk365guy

Hello Everyone,

Today I am going to share my thoughts on capturing responses from external third party forms in customer insights.

Let’s get’s started.

You can now capture submissions from any third party forms on your website and automatically create new leads or contacts in Customer Insights – Journeys.

This new feature empowers you to better understand your audience, target them more accurately and follow up effectively.

Here’s how it works:

1. Capture Form Submissions: You can collect form submissions from any external forms.

2. Mapping Fields: Easily create Javascript with mapping of your form fields to existing entity attributes.

3. Embed the Capture Script: Embed the capture script into mulitple pages containing the same form.

The enhancements allows you to maximize the potential of your external custom – built forms without the need to recreate them in Customer Insights – Journeys.

Happy Capturing!.

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Share this:

Dynamics 365 Customer Insights Seamlessly onboard customer data from your Delta Lake with no data integration

uk365guy

Hello Everyone,

Today I am going to share my thoughts on preview feature related to the onboard customer data from your delta lake with no data integration on Dynamics 365 Customer Insights.

Let’s get’s started.

Let’s explore how you can seamlessly onboard customer data from your Delta Lake to Customer Insights without the need for data integration.

Business Value: Data that is already prepared and stored in your Azure Data Lake in the Delta Lake format can be directly attached in Customer Insights. This elimates the need for additional data movement and formatting. Here are the key benefits:

1. Faster Processing: By avoiding intermediate processing and data preparation, you accelerate the processing time, leading to more regular and current insights.

2. Reduced Operations Management: With no additional transformation pipeline required, you save effort and cost associated with data conversion.

3. Resilence and Fault Tolerance: Delta format is more resilient and fault- tolerant. For instance, simultaneous updates and reads to a data partition are handled effectively, resulting in fewer data ingestion errors.

Features Details: With this features, you can:

Attach Delta Lake Data: Easily attach your data stored in Delta Lake format as a data source in Customer Insights. No need for additional data movement or formatting.

Native Readability: Delta-formatted data can be read natively within Customer Insights.

Delta Lake Incremental Processing: Take advantage of incremental processing without any extra work. Data stored in Delta Lake format doesn’t require separate full or upsets folders.

To connect to data stored in Delta format from your Azure Data Lake Storage.

Remember, this seamless integratiob allows organizations to gain more frequent and up to date insights, empowering informed decisions and adaptability in dynamic business environments.

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)

#365BlogPostsin365Days

Share this:

{Do you know} Dynamics 365 Customer Insights Increase control and flexibility when attaching to data in Microsoft Dataverse

uk365guy

Hello Everyone,

Today I am going to share my thoughts on preview feature Dynamics 365 Customer Insights Increase control and flexibility when attaching to data in Microsoft Dataverse.

Let’s get’s started.

Certainly! Let’s explore how you can enhance your data management in Microsoft Dataverse within Dynamics 365 Customer Insights.

Improved Dataverse Connector for Customer Insights

The Dataverse Connector has undergone significant enhancements, providing you with more control and flexibility when importing data into Customer Insights – Data. Here are the key features:

1. Performance Improvements: You can now smoothly import large Dataverse tables into Customer Insights – Data, eliminating previous scale and performance limitations. This mean faster data ingestion and processing.

2.Selective Table Import: Say goodbye to read-only mandatory table selections! With the updated connector, you have full control over which Dataverse tables you want to use in Customer Insights. No more forced selections, pick only the ones relevant to your needs.

3.Column-Level Customization: Choose the specific column you want to process and output in Customer Insights. Tailor your data import by selecting only the relevant fields from your Dataverse tables.

4.Advanced Row Filters: Apply filters to exclude inactive records or include only those added or modified within a specific time frame (e.g., the last year). Fine tune your data selection based on your business requirements.

How to connect to Dataverse in Customer Insights

1. Navigate to Data > Data Sources.

2. Click Add a data source.

3. Select Microsoft Dataverse.

4.Provide a Name and an optional Description for the data source.

5. Enter the Server address for your Dataverse organization and sign in.

6. Choose the tables you want to import from the list.

7. Save your selection to start syncing the chosen tables from Dataverse.

Remember that Dataverse tables with change tracking enabled are visible, you can easily connect them to Customer Insights. If you encounter any issues, check the change tracking settings for your custom tables in Power Apps.

By leveraging these improvements, you’ll have a more efficient and customizable data integration experience.

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Share this:

Difference between Dataverse N:N vs Choice vs Manual N:N

uk365guy

Hello Everyone,

Today I am going to share my thoughts on Dataverse N:N vs Choice vs Manual N:N

Let’s get’s started.

Let’s delve into the difference between Dataverse N:N, Choice and Manula N:N relationships:

1. Dataverse N:N (Many to Many) Relationships:

Definition: In Dataverse, N:N relationship allows for a many to many association between two tables.

Hierarchy: Unlike 1:N (one to many) relationships, N:N relationships do not establish an explicit hierarchy between rows.

Configuration:

No Lookup columns or behaviors need to be configured.

Rows created using N:N relationships are considered peers, and the relationship is reciporal.

Storage:

A relationship (or intersect) table stores the data that associates the two tables.

This table has a one to many relationship with both related tables and only stores the necessary values to define relationship.

Custom column cannot be added to the relationship table, and it is not visible in the user interface.

Creation:

Choose the two tables you want to participate in the relationship.

Decide how you want the respective lists to be available within the navigation for each table.

Note that not all tables can be used with N:N relationships.

Designers:

Power Apps Portal: Provides an easy streamlined experience but lacks some special settings.

Solution explorer: Offers more flexibility for less common requirements.

You can also create N:N relationships by importing a solution or using Metadata Services.

Use Cases: Ideal for scenarios where multiple records from both tables need to be associated(e.g., Opportunities and competitors in Dynamics 365 Sales).

2. Choice Relationships:

Usage: Commonly used when dealing with a single table and static choices.

Configuration: Choice are predefined and do not involve complex relationships.

Example: If you have a dropdown field with fixed options(e.g., “High”, “Medium”, “Low”), you’re using a choice relationship.

3. Manual N:N Relationships:

Definition: These are created manually without relying on the built in intersect entity.

Configuration:

You create your own intersect entity to establish the many to many relationship.

Provide more control over the relationship behavior.

Use Cases: Useful when you need custom logic or additional fields in the intersect entity.

In Summary, choose the relationship type based on your specific requirements: Dataverse N:N for true many to many associations, choice for simple predefined options, and manual N:N when customizing the relationship behavior.

That’s it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Share this: