Forum Discussion

khizerk's avatar
khizerk
Frequent Visitor
3 years ago

Issue when turning on time intelligence

Hi,

 

Uptil last month data load, I had time intelligence enabled in data load and everything was working fine.

This month's data load has a few additional rows. However, data refresh would run out of memory. So I turned off time intelligence for data load and the data refresh works fine. Turning on time intelligence on data load freezes Power BI (on the settings screen). Keeping time intelligence turned off is produced weird results, where visuals are including transactions subsequent to the date selected in the date slicer. 

 

I have a standard date table connected to different fact tables as shown below:

 

Any tips on troubleshooting this?

Tips and Tricks

2 Replies

  • jdbuchanan71's avatar
    jdbuchanan71
    Super User
    3 years ago

    khizerk 

    If you have a well defined model you should always disable auto date/time and use your models calendar table.

    Auto date/time is only for models that don't have a calendar table.  Leaving it on can greatly increase the size of your model for no benefit.  Take a look at this video from Guy in a Cube titled "Reduce Power BI dataset size by 60% with one checkbox?"  that talks about this topic.
    https://www.youtube.com/watch?v=RnDdDlozcdo&t=116s&ab_channel=GuyinaCube

     

  • khizerk's avatar
    khizerk
    Frequent Visitor
    3 years ago

    Thanks, I have turned off auto date/time but my memory usage issues still persist, primarily due to a iterative calculated table.

     

    To reduce the memory consumption of the model, I want to supply part of the calculated table which relates to previous months as a offline table via import mode (Table A) and have the calculated table only calculate values for the current month (Table B). I am then trying to merge Table A and Table B via a union in DAX to create a virtual table (Table C).

     

    However, I am running into a roadblock when trying to execute the following code:

    VAR TWRX = PRODUCTX (
                VALUES ( TableC[TransactionDate]),
                [TWR]  
            )
     
    I cant qualify TransactionDate field when referring to Table C since Table C is a virtual table. The above function used to work ok and produce the desire result when Table B was performing calculations for all historical months and I was using the following code, since Table B is physical table:
    VAR TWRX = PRODUCTX (
                VALUES ( TableB[TransactionDate]),
                [TWR]  
            )
     
    Any ideas on how to resolve this?