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. ..
try , -1 where you currently have ,1
Shortest possible answer: Your model is seriously messed up if that is the result.
Alas technically this is correct:
For 2018 the YAGO value IS 38638965. It's just your underlying model that's wrong.
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).
My date dimension... Couldnt find any issues. ..
I tried. It will just display the same 2017 value in 2016 also. Actually i want to display the value of 2016.
I made the Join to time dimension online . Also the time dim and measures created online without a restart. Can it be a problem?
used the time dim date column instead of deal date from fact in filter and criteria. It seems like worked .will update you soon.
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 ...
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
Should i have chronological key every level or only at the date level?
Explore how to build agents using code in AI Data Platform. We'll create an agent that examines and analyzes the contents of a Github repository and reports its findings. The session demonstrates how to use different developer tools to create agents including the AIDP extension for VS Code and Codex. Using these tools we…
The user icon in the upper-right corner of OAC (DV) is displaying more menu options for our non-admin users than we wish to display. We would like to restrict these to only "Profile" and "Sign Out" for regular users. Is there a way to customize these menu items? Especially if we can control this via security, that would be…
What is wrong with this code
Am I missing something or is there no way to search through previous posts to make sure I don't duplicate a question? All I see on the filter options are tags or status… a general search for a word or phrase would be helpful.
We were under the impression that when exporting a visualization in DV to CSV format hidden columns would be include from the grammar panel. This is not happening. See below for a screenshot showing 3 hidden columns that do not appear when exporting the pivot table to CSV. This seems to have worked a month or so back but…
Migrated RPD from obiee12c to OAS 2024. post migration when we try to access dashboards on OAS we are getting below error: State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000) State: HY000. Code: 43275. [nQSError: 43275] Message returned from OBIS…
