This article is contributed. See the original author and article here.
During the 1st quarter of 2024, D365 Sales conversation intelligence data will migrate from its current storage location (Microsoft provided storage) across to each customer’s Dataverse organization. This blog post describes this change and provides answers to questions raised by admins when preparing their organizations for this data migration.
Sales conversation intelligence data is the general term for any outcome of the processing of phone calls made through the embedded Teams dialer within Dynamics 365. This includes files, such as the audio recording file or transcript file, as well as all the insights collected during a call. Examples include:
Sentiment
Tracked keywords
Asked questions
Summary suggestions
Important: during the migration, no data will be transferred outside of your tenant.
Moving the data into Dataverse allows you to meet the highest data management standards, such as data encryption using Customer Managed Key (CMK) – and management of customer data using Lockbox.
The migration also allows for granular control over the conversation intelligence data: orgs can now allow access to specific types of data only for specific security roles. For example, the admin can assign privileges to the ‘sentiment’ entity in Dataverse only for sales managers. This granular control also allows for deletion of specific types of data while retaining others. For example, the admin can store sentiment data for only 1 month, while storing the transcript of the call for 1 year, and by this maximizing the Dataverse storage capacity.
Having conversation intelligence stored in Dataverse also allows organizations and 3rd party apps to consume the data per the organization’s needs. For example, organizations can create tailored dashboards and visualizations based on the data. Furthermore, the admin can allow third-party apps to access the conversation intelligence data and to provide extensible services based on it.
Storage location by type
The following table describes the storage location of conversation intelligence data before and after the change:
Current storage
Type of data
Before the change
After the migration
Microsoft provided storage
Files (recording, transcript)
Microsoft provided storage
Organization’s Dataverse1
Conversation intelligence insights
Microsoft provided storage
Organization’s Dataverse1
Your own Azure blob storage
Files (recording, transcript)
Your own Azure blob storage
Your own Azure blob storage2
Conversation intelligence insights
Microsoft provided storage
Organization’s Dataverse1
1 After the data is successfully migrated, it will be deleted from the Microsoft-provided storage.
2 No change. This data is not migrated.
After the successful migration of existing data, data from new calls will be automatically saved to Dataverse.
Action required by admins:
For all organizations:
Check the solution version (mandatory): Make sure you have the latest version of the conversation intelligence solution (msdyn_Conversation_Intelligence version 9.0.1.1139 or higher) installed in your organization.
Provide access to new Dataverse entities (mandatory): Make sure the relevant security roles have read and write privileges to the new Dataverse entities (see below a list of entities).
Make sure you have sufficient storage space in Dataverse (mandatory):
Database storage: Multiply the number of calls by 160KB.
File storage (only relevant for orgs previously using Microsoft provided storage): Multiply the number of calls by 0.93MB.
For example: if you had 20,000 calls, and you previously used the Microsoft provided storage, you will need to have 32GB of DB storage and 18.6GB of file storage for the migrated data.
Note: The above numbers are based on average call duration and number of insights per call. Actual sizes may vary.
Set a retention policy (optional): Previously, conversation intelligence data was automatically deleted according to the retention policy set by the admin in the conversation intelligence settings. By default, data saved into Dataverse does not have an automatic retention policy like this. If you wish to set a retention policy for your conversation intelligence data in Dataverse, you can do so by following this documentation.
For organizations currently using own Azure blob storage:
Set up Service principal (mandatory): To allow conversation intelligence access to your blob storage in a more secure way. See this article to learn more on this setup.
Opting out of migrating the existing data into Dataverse
By default, your existing data will be migrated to Dataverse. If you wish to opt out of the migration, (because your organization is no longer using conversation intelligence or you don’t want to migrate the existing files or insights for example), you will need to send an email, containing your first and last name and the organization ID to this email address: CI-data-migration@microsoft.com before January 31st 2024. The data of organizations which opted-out of the migration will be permanently deleted by April 1st 2024.
Frequently asked questions
Here are some answers for questions you might have on this process:
What will happen to my organization’s saved data? The data will be transferred from where it is stored today (Microsoft provided storage) to your organization’s Dataverse database. After verifying the transfer and customer confirmation, the data will be permanently deleted from the previous storage location (data will not be automatically deleted from your Azure blob storage). Note that data older than 90 days will not be migrated.
What type of Dataverse storage will be used? Conversation intelligence uses 2 types of Dataverse storage: File storage will be used for storing the recording and transcript files (unless stored in your org’s Azure blob storage), while DB storage will be used for storing the conversation intelligence insights.
What are the expected implications of moving the data into Dataverse?
Migrating data into your Dataverse will require free Dataverse storage space. See above on how to calculate the required storage space.
Who will have access to the transferred data?
Out-of-the-box security roles (such as Salesperson and Sales Manager) will automatically receive privileges to the new entities where the data is stored. If your org uses custom security roles, make sure you assign them with the required privileges for the new Dataverse tables as listed below. You can do this prior to the migration of the data. List of new Dataverse entities:
Conversation Action item
Conversation Aggregated Insights
Conversation Comment
Conversation Participant Insights
Conversation Participant Sentiment
Conversation Question
Conversation Segment Sentiment
Conversation Sentiment
Conversation Signal
Conversation Subject
Conversation Summary Suggestion
Conversation System Tag
Conversation Tag
Ocrecording
Recording
SCI Conversation
Sci Environment Settings
Sci User Settings
Transcript
Will users in my organization be able to continue using the conversation intelligence app?
Once the data is migrated into Dataverse, the conversation intelligence app will no longer work. The aggregated conversation intelligence data will be available through a new Power BI based dashboard.
How to opt-out of moving my organization’s existing data into Dataverse? You can opt-out of moving the existing data by sending an email to: CI-data-migration@microsoft.com before January 31st 2024. If you chose to do so, the existing data of your organization which is currently saved in the Microsoft-provided storage will be permanently deleted by April 1st 2024.
What’s next? If you don’t choose to opt-out, your organization’s conversation intelligence data will be transferred to Dataverse between February 1st 2024 and March 30th 2024. You will receive an email with a confirmation of successful data migration. After the moves to Dataverse, all new conversation intelligence data will be saved to Dataverse as well.
This article is contributed. See the original author and article here.
Frontline managers have gained greater control, on a team-level, over the capabilities offered in Microsoft Shifts.
With the latest releases now available on the Shifts settings page, we have made updates to improve the end-user experience for frontline manager and workers. The updates are as follows:
Open shifts
Previously, when the Open Shifts setting was off, frontline managers could create but not publish open shifts. Also, they could view open and assigned shifts listed on their team’s schedule (including when workers are scheduled for time off).
Now, when the setting is turned off, frontline managers can’t create open shifts and can only view on their team’s schedule the assigned shifts (including scheduled time off).
See the differences from the past and new experience for frontline managers:
Time-off requests
Previously, when the time-off request setting was turned off, frontline managers couldn’t assign time off to their team members; more over, frontline workers couldn’t request time-off.
Now, when the setting is turned off, frontline managers can continue to assign time off to their team members. However, frontline workers will not have the ability to create time-off requests if this setting remains off.
Your organization can leverage Shifts as the place where the frontline may view their working and non-working schedules despite not using Shifts as your leave management tool.
See the new experience for frontline managers:
Open shifts, swap shifts, offer shifts and time-Off requests
Previously, when any of the request-related setting toggled between on to off, frontline managers couldn’t manage previous requests that were submitted when the setting was on.
Now, frontline managers can directly manage previous requests on the Requests page while frontline workers can view status and details of their individual requests.
This article is contributed. See the original author and article here.
Introduction:
The start of the new year has brought a wave of exciting enhancements to the Demand Planning module in Dynamics 365 Supply Chain Management. We’re thrilled to introduce you to five groundbreaking features that will redefine the way you approach demand planning. In this blog post, we’ll look into each feature, highlighting their benefits and showcasing live demos hosted by the expert, Anders Girke.
Feature 1: Edit on Total Level
The new feature in our January release is the revolutionary “Edit on Total Level” functionality. This empowers planners to expedite their planning workflows through effective edits on a broader scale. Let’s swiftly explore the advantages:
✨ Edit on Total Level: Accelerate planning with efficient edits on a larger scale.
? Date Filters: Navigate and analyze data effortlessly.
? Distribute Proportional Over Time: Streamline workflows with proportional changes.
? Allocate Proportional Amongst Dimensions: Optimize precision in planning.
The second feature in our January release series is “Filter in Transformation.” This powerful tool allows precise data transformation for enhanced what-if analysis and forecasting on a focused dataset. Here are the key benefits:
? Perform What-if forecasts on a filtered sub-set of data
? Filter staging data prior to transformation
? Ensure secure performance
? Experiment with Dimensions to refine your planning
Witness the possibilities unfold as you perform What-if forecasts, filter staging data, ensure secure performance, and experiment with dimensions to refine your planning. Your demand planning just got a whole lot smarter!
The third installment of our January release series introduces “Comments.” This feature is set to transform collaboration and communication within the demand planning application. Key highlights include:
? Enhanced Communication: Provide detailed explanations for changes, fostering transparency.
? Real-time Collaboration: Facilitate consensus-building among team members.
Feature 4: System Administrator Role for Demand Planning
In this release, we introduce the pivotal role of the System Administrator for Demand Planning. This role is responsible for installing the app, assigning roles, managing teams, and overseeing critical operations. Highlights include:
? Role Level Access for Contributors: Empower limited users with the ability to view shared worksheets, create personalized views, and edit data within their permissions.
? Row Level Access Rules: Define conditions for specific tables, columns, and operators for unparalleled flexibility.
? Editing Demand Plans with Flexibility: Highlighting the power of role level access, added experience, and disaggregation in editing demand plans.
Get a sneak peek into the upcoming February release, emphasizing the balance between limiting filters for optimal performance and ensuring an exceptional user experience.
In conclusion, the recent January release of Dynamics 365 Supply Chain Management Demand Planning has brought forth a wave of transformative features, including “Edit on Total Level,” “Filter in Transformation,” and “Comments,” redefining the landscape for planners with tools that enhance efficiency and collaboration. The incorporation of the System Administrator role, Role Level Access for Contributors, Row Level Access Rules, and advanced security features positions the platform as a robust and secure solution for demand planning needs. With increased flexibility in editing demand plans and promising additions in the upcoming February release, Dynamics 365 is shaping a future of more streamlined and user-friendly demand planning experiences. This release marks a substantial leap forward, promising organizations worldwide a future characterized by smarter and more precise demand planning. As we embrace this evolution in demand planning, Dynamics 365 Supply Chain Management stands as a pioneer, leading the way with innovative features. Stay tuned for ongoing updates and enhancements that will continuously elevate your planning processes to unprecedented heights!
?North America Demand Planning Workshop?
Join us at the forthcoming Demand Planning Workshop, hosted at Microsoft’s state-of-the-art facility – Microsoft in Redmond, WA (98052). This event is tailored to introduce the innovative Demand Planning application to both our valued Customers and Partners.
This article is contributed. See the original author and article here.
We are updating our Microsoft Copilot product line-up with a new Copilot Pro subscription for individuals; expanding Copilot for Microsoft 365 availability to small and medium-sized businesses; and announcing no seat minimum for commercial plans.
This article is contributed. See the original author and article here.
Starting January 19, 2024, Microsoft Copilot in Dynamics 365 Customer Service will be automatically installed and enabled in your Dynamics 365 Customer Service environment. This update will install the case summarization and conversation summarization features. These features are available to all users with a Dynamics 365 Customer Service Enterprise license, and/or digital messaging or Voice add-on license for conversation summary enablement.
If your organization has already enabled Copilot in Customer Service, there will be no change to your environment.
Key dates
Disclosure date: December 2023 Administrators received a notification about the change in the Microsoft 365 admin center and Power Platform admin center.
Installation date: January 19 – February 2, 2024 Copilot in Customer Service is installed and enabled by default.
Please note that specific dates for messages and auto-installation will vary based on the geography of your organization. The date applicable to your organization is in the messages in Microsoft 365 admin center and Power Platform admin center. Copilot auto-installation will occur only if your organization is in a geography where all Copilot data handling occurs “in geo.” These regions are currently Australia, United Kingdom, and United States. Organizations where Copilot data handling does not occur “in geo” must opt in to cross-geo data transmission to receive these capabilities.
What is Copilot in Dynamics 365 Customer Service?
Copilot in Customer Service is a key part of the Dynamics 365 Customer Service experience. Copilot provides real-time, AI-powered assistance to help customer support agents solve issues faster. By relieving them from mundane tasks such as searching and note-taking, Copilot gives them time for more high-value interactions with customers. Contact center managers can also use Copilot analytics to view Copilot usage and better understand how it impacts the business.
Why is Microsoft deploying this update?
We believe this update presents a significant opportunity to fundamentally alter the way your organization approaches service by quickly improving and enhancing the agent experience. The feedback we have received from customers who are already using Copilot has been overwhelmingly positive. Generative AI-based service capabilities have a profound impact on efficiency and customer experience, leading to improved customer satisfaction. This update applies only to the Copilot summarization capabilities, which integrate with service workflows and require minimal change management.
Learn more about Copilot in Dynamics 365 Customer Service
This article is contributed. See the original author and article here.
Problem:
===========
Assume that you have tables with Identity columns declared as datatype INT and you are using Auto Identity management for those articles in a Merge Publication.
This Publication has one or more subscribers and you tried to re-initialize one subscriber using a new Snapshot.
Merge agent fails with this error:
>> Source: Merge Replication Provider
Number: -2147199417
Message: The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identit
Cause:
============
Identity range Merge agent is trying to allocate, exceeds maximum value an INT datatype can have.
Resolution
=================
Assume that publisher database has only one Merge publication with 2 subscribers, and your merge articles have this definition:
As you see from above diff_pub_range_end_max_used column is zero for tblCity.
When Merge agent runs depending on how many servers are involved it has to allocate 2 ranges for each.
In the example above we have Publisher and 2 subscribers and @identity_range is 1000. So, we will have to allocate range for 3 servers i.e., 3 * (2*1000) = 6000
Our diff_pub_range_end_max_used should be greater than 6000, only then we will be able to allocate a new range for all the servers.
To resolve the issue.
Remove tblCity table from publication.
Change the datatype from int to bigint and add this table back to publication.
Then generate a new snapshot. It will generate snapshots for all articles, but only this 1 table will be added back to the existing Subscribers.
Recent Comments