Forum Discussion
Issue with calculated date range
Hi lisapduan ,
Apologies for any earlier inconvenience. Our testing confirms that the date range logic functions as intended and meets your original requirements.
FYI:
From your latest message, it seems a particular relationship in your data model is affecting the date context flow. This explains why the logic worked correctly when that specific table was removed.
While the DAX solution is robust, you may need to adjust your model setup slightly to ensure everything aligns perfectly.
I have also attached a .pbix file containing a simplified example of the working logic for your reference.
Regards,
Yugandhar.
Hi lisapduan ,
Has your issue been resolved, or do you require any further information? Your feedback is valuable to us. If the solution was effective, please mark it as 'Accepted Solution' to assist other community members experiencing the same issue.
This issue has not been resolved and put on the back burner due to other priorities. The issue seems to be more of a realationship issue. When we were backing tracking through the set up we noticed when 1 table was removed, what we were wanting to do worked. It is a critical table though so it has to be there. We are going to rebuild the model from scratch when we have time. The original was built by by someone no longer here.
Hi lisapduan ,
Apologies for any earlier inconvenience. Our testing confirms that the date range logic functions as intended and meets your original requirements.
FYI:
From your latest message, it seems a particular relationship in your data model is affecting the date context flow. This explains why the logic worked correctly when that specific table was removed.
While the DAX solution is robust, you may need to adjust your model setup slightly to ensure everything aligns perfectly.
I have also attached a .pbix file containing a simplified example of the working logic for your reference.
Regards,
Yugandhar.
