Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi,
I am getting poor performance form PBI Desktop with the following measure:
Aging = DATEDIFF(AVERAGE(TDate_creation[date creation]),today(),year)
I tried at first to create a custom column but the editor would not accept the syntax of DateDiff.
The table containing the date of creation contains rows that are NULL, could this be the reason?
Or is the issue with the measure?
Solved! Go to Solution.
I created a new column direclty in PBI Desktop using:
aging = DATEDIFF(TDate_creation[date creation],today(),YEAR)
The performance is now back to normal.
I created a new column direclty in PBI Desktop using:
aging = DATEDIFF(TDate_creation[date creation],today(),YEAR)
The performance is now back to normal.
@Cyrilbrd , You should be able to create a new column like , in the table TDate_creation
Aging = DATEDIFF(TDate_creation[date creation],today(),year)
or a measure =
Aging = AverageX( TDate_creation ,DATEDIFF(TDate_creation[date creation],today(),year) )
Thanks, I was able to figure it out.
All works fine now.
It is often confusing however to figure out if the editor, or the desktop or a measure works best... imo