Year ago measure — Oracle Analytics

Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Year ago measure

Received Response
171
Views
25
Comments
Sunny86
Sunny86 Rank 6 - Analytics Lead
edited Aug 13, 2024 5:55PM in Oracle Analytics Cloud and Server

Hello All,

Trying to configure Year ago measure. Previous year same date data. But instead of that it is showing values for year 2018 instead of 2016. ..

pastedImage_0.png

pastedImage_1.png

pastedImage_2.png

pastedImage_3.png

«13

Answers

  • Robert Angel
    Robert Angel Rank 8 - Analytics Strategist

    try , -1 where you currently have ,1

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Shortest possible answer: Your model is seriously messed up if that is the result.

    Alas technically this is correct:

    pastedImage_0.png

    For 2018 the YAGO value IS 38638965. It's just your underlying model that's wrong.

  • Gianni Ceresa
    Gianni Ceresa Mod

    Hi,

    I'm kind of curious to know what your model looks like as I hardly imagine how it is possible in a correct model to have a date like "10/10/2017" on the same row as "2017" AND "2018"!

    So I would say your "year ago" is fine and it's your model wrong (or weird) and your "Deal date" is not part of your time dimension, so you can't expect OBIEE to make a year ago on something not being linked to the time dimension (as you see it works on the year column).

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    My date dimension... Couldnt find any issues. ..

    pastedImage_0.png

    pastedImage_1.png

    pastedImage_2.png

    pastedImage_3.png

    pastedImage_4.png

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    I tried. It will just display the same 2017 value in 2016 also. Actually i want to display the value of 2016.

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    I made the Join to time dimension online . Also the time dim and measures created online without a restart. Can it be a problem?

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    used the time dim date column instead of deal date from fact in filter and criteria. It seems like worked .will update you soon.

  • Gianni Ceresa
    Gianni Ceresa Mod

    You have a "deal date" column in your fact table? That's what I meant by weird model. If you made the right joins in the model you don't need to keep a "deal date" column as this one is supposed to be equal to the day column of your date dimension. So get rid of it and you avoid the mistake.

    And you see once you take the right date it works as it was already working fine before ...

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner 
    3295595 wrote:deal date from fact in filter and criteria

    Deal Date on the Fact.....and that doesn't scream WROOOOOOOONG at you in the loudest possible manner?

    Dates go into a dimension. That's dimensional modelling 101 from back in the 90s.

    Edit: AND your Year level doesn't even have a chronological key...swell

  • Sunny86
    Sunny86 Rank 6 - Analytics Lead

    Should i have chronological key every level or only at the date level?