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.

Define a forecast model
Define the entities that must be used to generate the forecast.
1. In the General step of the Forecast configuration page, define the fields that should be used for the forecast.
[Steps 2 to 6 omitted]
7. Select a Rollup to hierarchy relationship.
This step establishes a relationship between the rollup and hierarchy entities. Each forecast template starts with a default rollup to hierarchy relationship:

Choose different values to support your organization's specific requirements if needed.
Note: Select a template
The fastest way to create a forecast is to use a template. The template that you select defines how the forecast groups data.
On the Forecast configurations page, select one of the following templates:
Org chart forecast: Rollup columns and projections are based on your organization's reporting structure. This template uses the Manager field of the User entity for the hierarchy.
Product forecast: Rollup columns and projections are based on the product hierarchy.
*-> Territory forecast: Rollup columns and projections are based on the sales territory hierarchy.
Reference:
https://learn.microsoft.com/en-us/dynamics365/sales/define-general-properties-scheduling-forecast

Reference:
Increase the Number of Sodas at No Additional Charge: Increase the quantity of sodas in the line item To add sodas without impacting the price, sales staff can simply increase the quantity of sodas in the line item. This approach allows flexibility within the bundle without altering the overall bundle cost, which remains fixed.
Increase the Number of Sandwiches and Charge the Price List Price for Each Additional Sandwich: Add another line item for sandwiches with the default price To charge extra for additional sandwiches, the staff should add another line item for sandwiches. This line item would use the default price from the price list, ensuring that any additional sandwiches beyond the initial bundle are charged accordingly.
This allows the base bundle to remain consistent while additional items are billed separately based on the standard price list.
By following these guidelines, the sales staff can effectively manage the product bundle within opportunities, maintaining pricing consistency while allowing flexibility for additional items as required by the client.

For users to pin views of Dynamics 365 Sales records in Microsoft Teams, Enhanced Microsoft Teams Integration must be enabled. This feature allows users to seamlessly work with Dynamics 365 records within Teams and ensures proper synchronization between the two platforms.