As this was recognised as a bug and deemed fixed I would log an SR providing a detailed test case, this should give you leverage to get a rapid resolution.

Also, but I never tested this, I do not see why you could not set up a master detail solution to get multiple analyses to all listen to the same channel. But as I say, I have not tested this idea.

The trick I have used in the past is to have a hidden dashboard prompt which 'catches' (no added plumbing required) the drill action on the main report, having the drill pointed at the same dashboard page for any of the reports which is correlated, on the hidden dashboard prompt setting a presentation variable which is the…

Amen to that. I believe that as a developer / architect the worst thing I can do is deliver exactly what they ask for...

Good morning Christian. What do you think it would take to stake the writeback 'vampire', there seems to be an inordinate amount of interest in it recently!

Hi, you can have multiple fields in the column area and you can create calculated columns in the pivot table, so yes, in more than one way you can have multiple columns. What is your exact requirement, exactly what are you trying to achieve?

!!!! @user1137177 Martin / Christian are suggesting you change your display name; - Click on your username in the top right hand corner of the page, click on edit profile, go to display name, change it to 'Whatever You Like but not user1137177'

And check this out to get a clue on why it is failing; - https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=qew10ui6m_4&_afrLoop=546784445028864#FIX OBIEE 11g: Writeback Does Not Display Detailed Errors in Front End. (Doc ID 1360106.1)

This is definitely a failure to update being logged?? type="update"><success/></writeBackResponse>[[

One other thought, can you also use something in your analysis or browser 'developer features' so you can see the values of '@{c685ec171e5828393}' at runtime?

Also, what version of OBIEE are you using?

And do you get anything in the log when it fails? And is caching off for the analysis with the writeback? And are all other things equal when it works and doesn't work; - user, browser, data?

Have you tried testing the same insert / update statement directly against the DB when it fails to rule out data types / lengths / constraints etc as an issue? And at the risk of repeating myself (1 minute before Christian ) have you thought of using Apex or similar tool that is fit for purpose for data insert /…

Do yourself a favour, drop the dead donkey and use Apex for this, it has the kind of fully formed functionality you are looking for.

Simple, but not what he is after, this would yield 2 lines for Simloa and Donnel, he only wants 1 line each...

Depending on your logical model you may also be able to create a measure in the rpd for this by creating a max based measure on effective date and then associating that with the ID by pinning it in your dimension hierarchy to that level; this is why I say depending on your logical model. On your description, you might be…

A good analogy on a number of levels

Rotten?? That would make a nice three letter acronym, the RMP; "Rotten Model Paradigm" ;-) As in; - Looks like you have a real RMP there...

But if; - Fact -> Time Dimension Where -> is fact.time_key = Time.Key And filter is; - Time.Year = '2018' (or whatever descriptor) Then OBIEE will NOT do full table scan on fact table and access will 'lead' by smaller time data set. Unless something is badly wrong with your data model....

The short answer is 'no', join order is not relevant. Type of join, yes, but you can specify that in the logical layer when joining logical tables. OBIEE will use metadata configured in the rpd, like levels and no of elements to optimise your queries. And of course the best foundation for speed is report against a data…