Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
Hi Community,
I am getting an error in the Power BI service schedule refresh (the error is attached), my concern is why I am getting an error in the Power BI Service.
When I manually refresh the report from Power BI Desktop I don’t get any error.
For some days, I have been getting this error and after 10-15 days the error has been gone.
So, my question is, why am I getting these errors, and why did it disappeared after a few days?
Schedule refresh has started working without any change in the DAX.
I have attached the DAX for the reference
WeightedForecast =
GENERATE (
VALUES (DateTable),
FILTER(
msdyn_quotelinetransaction,
DateTable[Offset] > (msdyn_quotelinetransaction[StartDateFormated]-TODAY()) &&
DateTable[Offset] <= (msdyn_quotelinetransaction[EndDateFormated]-TODAY()) &&
DateTable[Full Date] <> "" &&
msdyn_quotelinetransaction[Transaction Class] = "Time" &&
msdyn_quotelinetransaction[Transaction Type] = "Project Contract" &&
(RELATED(quote[statecodename]) = "Active" || RELATED(quote[statecodename]) = "Draft") &&
RELATED(quote[statuscodename]) = "In Progress"
)
)
DailyForecast = SUMMARIZE(
WeightedForecast,
WeightedForecast[Full Date_WeightedForecast],
"TotalDailyForecast",
SUM(WeightedForecast[DailyHours]),
"MaxDailyForecast",
SUM(WeightedForecast[MaxDailyHours])
)
WeightedForecast =
GENERATE (
VALUES (DateTable),
FILTER(
msdyn_quotelinetransaction,
DateTable[Offset] > (msdyn_quotelinetransaction[StartDateFormated]-TODAY()) &&
DateTable[Offset] <= (msdyn_quotelinetransaction[EndDateFormated]-TODAY()) &&
DateTable[Full Date] <> "" &&
msdyn_quotelinetransaction[Transaction Class] = "Time" &&
msdyn_quotelinetransaction[Transaction Type] = "Project Contract" &&
(RELATED(quote[statecodename]) = "Active" || RELATED(quote[statecodename]) = "Draft") &&
RELATED(quote[statuscodename]) = "In Progress"
)
)
Any help would be appreciated.
Solved! Go to Solution.
Hi, @Siddhesh_Pal
Check here to see if the problem has been fixed. Please refresh and check to see if the problem still exists?
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @Siddhesh_Pal
This is a known issue. We have submitted it internally and are currently awaiting feedback. I will keep you updated on any progress. The issue can be mitigated by changing the CalendarAuto to Calendar function.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you @v-zhangtin-msft for the reply.
Please let us know if you get any updates.
Hi, @Siddhesh_Pal
Check here to see if the problem has been fixed. Please refresh and check to see if the problem still exists?
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @v-zhangtin-msft, the issue is already resolved.
I wanted to know why this issue has occurred.
Thank You.
Hi, @Siddhesh_Pal
The issue was caused by an incomplete code change that tried to address incorrect DAX blank row dependency propagation across multiple tables. Since it changed the way how the dependencies between different metadata objects and measures are calculated, some existing models started emitting a circular dependency error in previously valid model configurations. The issue was resolved by reverting the incomplete code change that caused the issue.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @v-zhangtin-msft
I have not made any changes in the DAX then and after some days scheduled refresh has started working.
User | Count |
---|---|
54 | |
31 | |
31 | |
30 | |
24 |
User | Count |
---|---|
46 | |
43 | |
16 | |
16 | |
14 |