You are a Dynamics 365 Sales administrator. You configure a forecast template that uses the Forecast category as a starting point for a layout for the sales team. The sales manager wants the value of the Lost column to come from the Total Detail Amount instead of the default value because the revenue is always driven by the items. You need to make the change. What should you do?
Since the sales manager wants the Lost column in the forecast to reflect the Total Detail Amount, which is item-driven, you should update the Amount column in the existing forecast layout.
By editing the existing forecast and changing the source for the Amount column to the Total Detail Amount, you can ensure the forecast accurately reflects item-based revenue calculations without needing to create a new forecast or add calculated columns.
A company plans to use server-side synchronization to synchronize emails, tasks, and appointments between Microsoft Exchange and Dynamics 365 Sales.
The salespeople want to know when their emails will be synced.
You need to describe the server-side synchronization frequency for the salespeople.
How should you describe the frequency?
Server-side synchronization typically syncs at equal intervals, which can be configured in Dynamics 365. These intervals determine how often data is synchronized between Microsoft Exchange and Dynamics 365 Sales, affecting emails, tasks, and appointments.
The synchronization frequency can be adjusted by the administrator but operates at consistent, regular intervals by default.
A large construction company uses Dynamics 365 Sales to manage their sales pipeline.
All future jobs are logged in the system as opportunities. Depending on the type o( work, some opportunities close faster, and others take longer due to dependency on the third-party vendors.
The sales team does NOT currently use the "On hold* option, as it does NOT provide enough details.
When working with open opportunities, the sales manager wants to know whether opportunities are pending permits or require asbestos removal.
You need to ensure that a salesperson can only select the "Pending Permits" or "Asbestos Removal" option when working with their opportunities to indicate the deal is taking longer.
What should you do?
Understanding the Statuscode and Statecode Columns:
In Dynamics 365 Sales, opportunities have two primary columns related to their status: statecode and statuscode.
The statecode defines the primary state of an opportunity (e.g., Open, Won, Lost).
The statuscode provides more granular reasons associated with each primary state. For example, within the 'Open' state, you can have various reasons such as 'In Progress,' 'On Hold,' etc.
Modifying Status Reasons for Open Opportunities:
The construction company wants to indicate when opportunities are delayed due to specific external factors. To accommodate this, they need specific status reasons like 'Pending Permits' and 'Asbestos Removal.'
By adding these as status reasons under the 'Open' state, you enable sales team members to select these options directly from their current status options.
Steps to Add New Status Reasons to Open Opportunities:
Navigate to Solution: Go to the Dynamics 365 Sales app, then to Settings > Customizations > Customize the System.
Locate the Opportunity Entity: In the default solution, find and expand the 'Entities' list, then select 'Opportunity.'
Edit Statuscode Values: Within the 'Opportunity' entity, select 'Fields,' then find and edit the statuscode field. Here, you can add new options under the 'Open' status. Add 'Pending Permits' and 'Asbestos Removal.'
Publish the Changes: After adding and saving the new status reasons, publish the changes so that they are available to users.
Verifying Custom Status Reason Visibility:
Ensure the new options are available on the Opportunity form for selection.
Test by opening an Opportunity and confirming that the 'Pending Permits' and 'Asbestos Removal' options are available under the Open status reasons.
By following these steps, the sales team can now use specific status reasons to indicate why certain opportunities are delayed, providing clearer visibility into the sales pipeline's status.
The analytics team at your organization has created Power Bl reports that enrich data about your accounts from Dynamics 365 Sales with data NOT contained in Dynamics 365 Sales. The Power Bl reports are referenced by your executive leadership as the primary source of truth about account success metrics. Sales leadership has requested that sales users can see these insights about the accounts they have access to within Dynamics 365 Sales. You need to enable the insights to be available to sales users in Dynamics 365 Sales. What should you do?
To make Power BI insights available within Dynamics 365 Sales, specifically contextualized for accounts, you should embed the Power BI report with contextual filtering. This ensures that the report dynamically adjusts based on the specific account record a user is viewing.
Embedding with contextual filtering enables sales users to see account-specific insights directly within the Dynamics 365 interface, improving accessibility and relevance.
A company is implementing the Dynamics 365 Sales mobile app.
The company requires setup of several push notifications for sellers who use the app.
You need to create the push notifications.
Which feature should you use?
Understanding the Requirement:
The company wants to send push notifications to sellers using the Dynamics 365 Sales mobile app. This requires setting up automated notifications triggered by certain events or conditions.
Solution - Using Cloud Flows:
Cloud flows in Power Automate are ideal for creating automated workflows that can trigger push notifications based on events in Dynamics 365.
Power Automate provides connectors for Dynamics 365 Sales and mobile notifications, enabling the setup of push notifications without requiring custom code or plugins.
Steps to Create a Cloud Flow for Push Notifications:
Go to Power Automate and create a new Cloud Flow.
Set up a trigger based on a Dynamics 365 event (e.g., when a record is created or updated).
Add an action to send a push notification to the user's mobile device.
Customize the notification message and publish the flow to activate the notifications.
Using Cloud Flows in Power Automate enables dynamic push notifications for mobile users, providing timely updates to sales team members based on real-time data changes.
