Menu Close

Tag: #365blogpostsin365days

{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:

{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:

{How to} Migrate to Dynamics 365 Customer Voice instead of Survey Monkey

uk365guy

Hello Everyone,

Today I am going to share my thoughts on how to migrate Survey Monkey to Dynamics 365 Customer Voice.

Let’s get’s started.

Migrating from Survey Monkey to Dynamics 365 Customer Voice involves several steps, focusing on planning, data migration and learning the new platform to leverage its capabilities effectively.

Dynamics 365 Customer Voice offers deep integration with other Microsoft Products, providing a seamless flow of data across your business applications. Here’s a guide to help you through the migration process.

1. Evaluate Your Current Usage of SurveyMonkey

Review your surveys: Assess all the surveys you have in SurveyMonkey, including active, inactive and templates, Understand the process of each and how they are used in your organization.

Analyze your data: Look at the types of data you collect, how it’s analyzed, and how it integrates with other systems. This will help in understanding how to replicate or improve these processes in Dynamics 365 Customer Voice.

2. Get Familiar with Dynamics 365 Customer Voice

Learn the basic: Before making the switch, spend some time learning about Dynamics 365 Customer Voice. Microsoft offers a variety of documentation, tutorials and training sessions to help new users get acquainted with platform.

3. Plan your migration:

Map your requirements: Based on your review of SurveyMonkey and understanding of Dynamics 365 Customer Voice, map out how your existing and needs translate to the new platform/

Data migration strategy: Consider how you will migrate your existing survey data. This might involve exporting data from the SurveyMonkey and importing it into Dynamics 365 Customer Voice or another Dynamics 365 application, depending on your needs.

Integration needs: Identify any integration with other systems(e.g., CRM ERP) and plan how you will achieve similar integrations with Dynamics 365 Customer Voice.

4. Set Up Dynamics 365 Customer Voice

Configure your environment: Set up your Dynamics 365 Customer Voice environment, including any necessary integrations with Dynamics 365 applications or external systems.

Recreate your surveys: Start creating your surveys in Dynamics 365 Customer Voice. Utilize its advanced features to improve your surveys, such as conditional logic, personalized questions based on respondent data, and integration points for triggering surveys based on certain actions in Dynamics 365.

5. Test and Implement

Pilot testing: Before going live, conduct pilot tests with a small group of users. Collect feedback on the surveys and the overall experience.

Training: Provide training for your team on how to use Dynamics 365 Customer Voice effectively, focusing on creating surveys analyzing data and leveraging integration.

Go live: Once testing is complete and you’re confident in the setup, start depoloying your new surveys through Dynamics 365 Customer Voice.

6. Monitor and Optimize

Collect feedback: Continuously collect feedback from both respondents and internal users to understand what’s working and what needs improvement.

Analyze and Optimize: Use the analytics tools in Dynamics 365 Customer Voice and Power BI to analyze survey data and make informed decisions to optimize your surveys and processes.

Additional Considerations

Compliance and security: Ensure that your use of Dynamics 365 Customer Voice complies with any relevant data protection regulations and that your data is handled securely.

Cost analysis: Compare the costs between SurveyMonkey and Dynamics 365 Customer Voice, Considering not only subscriptions fees but also the potential savings from improved efficiencies and integrations.

Migrating from SurveyMonkey to Dynamics 365 Customer Voice can significantly enhance your data collection and analysis capabilities, especially if you’re already using other Dynamics 365 applications. Careful planning and execution are key to a smooth transition.

That’s it for today.

I hope this helps.
Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Share this: