Hi all,
Thanks in advance for taking time to help on my issue. So we have a dim - Status which has different categories such as 1) to be approved, 2) rejected and 3) approved. There is a specific measure which shows as 'approved' in the db (which is correct) but as 'to be approved' in the cube. I have tried to rebuild the cube so as to refresh the data but still the status won't change to 'approved' . Could anyone provide their invaluable guidance on this issue? Thanks again.
Cheers
Have you look at the view data contents in transformer to make sure it's the correct value before it's being placed into the cube?
Actually, I don't have a whole lot of experience with Transformer so when you ask me to "look at the view data contents in transformer" - are you asking me to check he scope of the model? Thanks in advance.
In Transformer, go to View and then click on Data Source viewer.
You can also right click on your data sources and select Data Source viewer.
everything seems to be fine with the values...I have infact re-created the cube at a new location...and re-published the cube and package but the data (status) not updated. Please advice.
It sounds like it's something in the DB. Are you sure you're looking at the correct source when running your Select statements against the DB?
Take the cube sql, make sure the source of the cube and your query tool are the same, add a line in the Where clause such that you're only looking at the specific, problem creating measure and look carefully at the DB results
Are you looking at the values in the data source viewer? Thats whats going into your cube.
Try Arsenals advice, you've got something in your DB that doesn't sound right.
How do you know the status is updated?
I have checked in the database myself and it is true that the value is accurate there (in DB) but not in the cube.
If you use the data source viewer in Transformer, is the data correct there? That would give you a start to check if the difference is before it gets to transformer or after.
My guess would be the report you are pulling the data out of the db with is messing with values.
tw;arsen brings up a good point - are you using a report to generate the cube and if so, is the report itself showing the correct results?
If you're using a package, then are the concerned query subjects showing the correct results?
In other words, you have to look at the cube source SQL and run that against the DB and see what the source SQL is bringing up
So sorry for coming back so late with the response.....was buried......the issue was in the underlying db.......someone had to explain the db arch which was updated and not many were known about the major changes.....anyways....thank you very much all for your time.
Cheers