Discover how to extend Dynamics 365 CRM roll-up fields to calculate total sales over 30, 60, and 90 days intervals, overcoming limitations with calculated fields.
In Microsoft Dynamics 365 CRM, roll-up fields are powerful tools for aggregating data across related records. However, users may encounter challenges when attempting to segment these aggregations based on time intervals using calculated fields. This article provides a solution to this common problem.
Problem Description
A roll-up field has been created to find the total sales for each customer. The goal is to further break down this data into 30, 60, and 90 days intervals based on the customer’s join date. The challenge arises when the system does not permit the use of a calculated field for this segmentation.
Solution Explanation
To achieve the desired segmentation of the roll-up field without using a calculated field, consider the following workaround:
- Instead of one, create separate roll-up fields for each time interval (30, 60, and 90 days).
- Apply filters within the roll-up field definitions to include only the records that fall within the respective time frames.
- If the roll-up field does not support the necessary granularity, use workflows or Power Automate to perform the calculations and update the fields accordingly.
Frequently Asked Questions (FAQs)
Question: Can I use calculated fields for time-based segmentation in roll-up fields?
Answer: No, calculated fields cannot be used directly within roll-up fields for this purpose. Use the workaround provided.
Question: What if the roll-up field does not support the required filters?
Answer: Use workflows or Power Automate to calculate and update the fields based on time intervals.
Summary
Segmenting roll-up fields by time intervals in Dynamics 365 CRM can be accomplished by creating separate fields for each period and applying appropriate filters or using automation tools to handle the calculations.
Disclaimer: The information provided in this article is for educational purposes. Always test solutions in a non-production environment before implementation.