-
Segment Estimate function should be one of the main features and work normally without return error
Segment Estimate function should be one of the main features and work normally without return error "Resource not found msdyn_PreviewSegment"
-
User be to customize the title and button in Duplicate Detection Window
User be to customize the title and button in Duplicate Detection Window. Customization XML need to provide section to customize button and title of Duplicate Detection window
-
Agent Presence need to set as away or busy after calls end
Agent Presence need to set as away or busy after calls end.
-
Email column remains editable despite read-only settings
- Email column remains editable despite read-only settings
- Email column is not showing the updated value when using the setValue() method in JavaScript.
-
Copilot Studio styling will be able to override the LCW dafault styling
Copilot Studio styling will be able to override the LCW default styling
-
Activating Segment in Sales Accelerator
They need this outer join condition between lead/custom entity (with M:N relationship).
But they are not using assignment rules - so this extra conditions cannot be applied on assignment rule's entity filter
But customer will update sequence and will apply this condition between sequence steps.
Outer join need to be available for Sales Segment condittion.
-
Enabled Copilot for customer insight journey in GEO CAN
Enabled Copilot for customer insight journey in GEO CAN. The feature is enabled by default for all supported geos, without needing to enable it in feature switches.
Unfortunately, CAN is not a supported region. We support NAM, GBR, IND and OCE only at the time being. We will update the docs to reflect that.
-
Teams and Users record owner should be clearly different
Teams and Users record owner should be clearly different. There should be one more to modify the record owners access for Teams members. There should be the feature to turn on or off the record owner across Teams.
-
Translation for record's value
The record's value can be able to translate when user changes the system languages base in the personalize setting.
Here is a good example. The Booking Status values from the Resource area. This is a supporting table and additional values have been added. But since the Name content is data, the values don't translate to Vietnamese. There are many supporting tables in Field Service like this and I'm looking for a strategy for how a user with Vietnamese as their language can have Vietnamese translations of these values.
-
Overflow handling time process need to be reduce under 30 secs
Overflow handling time process need to be reduce under 30 secs
