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.
Reference:
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.

Reference:
Add Products:
After units are created, add products to the catalog. Each product will have an associated unit and a description that defines it within the catalog.
Ensure products are added with complete details to enable proper pricing and discounting later.
Create Price Lists:
Next, create price lists that define the pricing for products. Price lists can be specific to regions, customer types, or other criteria and are essential for associating products with prices.
A price list is necessary for assigning product prices, enabling you to link prices with discount lists in the subsequent steps.
Add Price List Items:
Add price list items to assign specific products to price lists and set their prices. This links each product with its pricing based on the price list created earlier.
It allows flexibility to have different pricing structures for the same product across multiple price lists if needed.
Create Discount Lists:
Finally, create discount lists to apply quantity discounts on products. Discount lists define percentage or flat rate discounts based on purchase quantities, which can then be applied when products are added to sales orders or quotes.
This step ensures that sellers can apply quantity-based discounts, meeting the requirement for the product catalog setup.
By following these steps in the specified order, you can set up a product catalog that includes units, products, price lists, price list items, and discount lists, allowing sellers to manage product pricing and apply quantity discounts effectively.

Correct:
* Recalculate the forecast
Incorrect:
* Recalculate the opportunity.
* Update the Opportunity Forecast Category Mapping process.
Open the Opportunity Forecast Category Mapping Process workflow. You can customize or deactivate the workflow according to your organization's requirements.
Note:
Example of forecast recalculation methods
Let's understand the different methods with an example. Consider a scenario where you have a forecast with 4 quarterly periods and an annual period.
Assume that you're currently in Q4. The following table shows when and how the forecast data is updated for different scenarios and periods.
--
Dynamics 365 Sales, Recalculate forecasts manually
You want the forecast data to be up-to-date to make informed decisions. Forecast data is automatically recalculated at regular intervals. However, you can trigger a manual recalculation when you want to recalculate the forecast data immediately. You can also trigger a manual recalculation for past and future periods as they aren't automatically recalculated.
Recalculate and refresh forecast data manually
1. Open the forecast. Verify the Last updated timestamp on the command bar to know when the forecast was last recalculated successfully.
2. Select Recalculate data.
A notification appears at the top of the screen, confirming the recalculation. Recalculation happens in the background, and you can continue to work while recalculation is in progress.
3. After the application recalculates the forecast data, a notification appears to refresh the data.
On the notification, select Refresh page.

Understanding the Base Unit in Dynamics 365 Sales:
In Dynamics 365 Sales, the base unit represents the smallest quantity or measurement used to sell a product or service. It serves as the foundational unit within a unit group, which allows you to define how a product can be measured and sold in various quantities.
All other units within the unit group are defined in relation to this base unit. Therefore, it should represent the smallest quantity possible, ensuring flexibility in defining larger units or multiples based on this standard.
Selecting the Base Unit - Why the Lowest Quantity?
Choosing the lowest needed unit ensures that any other units, whether they are multiples or larger groupings, can be accurately calculated in relation to the base unit. This approach allows you to accommodate various selling quantities and ensures precise calculations across different unit types.
For example, if the lowest unit is a single item, you can then configure units such as a dozen, box, or case based on this base unit. This provides consistency and accuracy in pricing and inventory management.
Reference:
Benefits of Using the Lowest Needed Unit:
Configuring the base unit as the smallest measurable unit enables flexibility and supports various sales scenarios without restrictions. It simplifies the management of units and ensures that other unit variations align correctly in the product catalog.
By setting the base unit to the lowest quantity needed to sell the product or service, you establish a robust foundation for building out the unit group and accommodating different sales quantities in Dynamics 365 Sales.

Correct:
* Recognize that when you enable Dataverse search, it is enabled for all model-driven apps.
Turning on Dataverse search allows global search in all model-driven apps in that environment and allows generative AI experiences to work.
Incorrect:
* Ensure that any tables you wish to display results from are included in the model-driven apps.
* Ensure that you add columns to the search criteria by editing the Advanced Find view for each table.
Reference:
https://learn.microsoft.com/en-us/power-platform/admin/configure-relevance-search-organization