Narrative View ‘Contains HTML Markup’ Broken in OBIEE 11.1.1.3

Posted on November 26, 2010 by Paul McGarrick
Filed Under Answers, Narrative View, OBIEE 11g

You may have noticed that the ‘Contains HTML Markup’ checkbox within a report narrative view has no effect whatsoever in OBIEE 11g. According to Oracle this is a known bug and will be fixed in 11.1.1.4.

In the meantime, as a workaround, you can edit your instanceconfig.xml and disable the hardening for cross-site scripting. Add this tag in the <Security> section:

<HardenXSS>false</HardenXSS>

Bounce the Presentation Server and you should be good to go.

Comments

7 Responses to “Narrative View ‘Contains HTML Markup’ Broken in OBIEE 11.1.1.3”

  1. er on November 30th, 2010 9:58 am

    great!

  2. Samrat Mitra on December 7th, 2010 12:51 pm

    Hi,

    Can you give me the BUG ID from metalink that Oracle says it is a bug? I need it as part of my documentation to explain to a client…

    Thanks,
    Samrat Mitra

  3. Paul McGarrick on December 7th, 2010 1:33 pm

    It’s bug ID 10144565. [more info here]

  4. Samrat Mitra on December 7th, 2010 1:53 pm

    Hi Paul,

    Thanks for sending me the Bug ID, much appreciated!

    Added the suggested tag in the instanceconfig.xml file and am waiting till I can replace it in test environment…

    Also, do you know if OBIEE 11g still has the ‘Guided Navigation’ feature that was present in the 10g version? I used the feature to prevent reports from showing data after initial load of the dashboard. Its strange but I don’t see this feature in OBIEE 11g anymore…

    Best Regards,
    Samrat Mitra

  5. Paul McGarrick on December 7th, 2010 4:29 pm

    Hi Samrat

    I never had much need for guided navigation in 10g but I believe you can achieve the same results in OBIEE 11g by putting a condition on a dashboard section. When the condition evaluates to true the section will appear.

    Paul

  6. Samrat Mitra on December 7th, 2010 5:53 pm

    Hi Paul,

    Regarding the condition on the dashboard section : I agree with you that the condition should work.
    Hope I am not taking too much of your time but allow me to give a short example:

    I have a main report of columns say a,b and c and the report is prompted for a and b on the dashboard prompt.

    To not allow the report data to come on the screen on the first load of the dashboard, I will make a small intermediate report with columns a and b from the main report, and then I will filter a and b of this intermediate report to values not present in the report datasource.

    I will place this intermediate report below my main report for testing my logic.

    When I load the dashboard page, the main report runs on the condition that the intermediate report rowcount is greater than 0 which is false as intermediate report returns nothing.

    But when I select the values from a dashboard prompt on top for these two columns, the filter values get over ridden by the selection made now.

    So Intermediate report returns results and hence condition for main report section is true, hence it should appear! but…it doesn’t.

    Atleast not on the 64 bit version, but on the 32 bit OBIEE11g version, this does work.

    I have raised an SR for this but to no avail till now,

    Best Regards,
    Samrat Mitra

  7. Paul McGarrick on December 7th, 2010 7:10 pm

    Hi Samat

    The way you describe it – with different behaviour between 32 and 64 bit architectures – it certainly sounds like a bug.

    Anyway, I wonder if you could achieve a similar end result without all the hassle of an intermediate report…

    Create your report with columns a, b, c as usual. Set a and b to be filtered using presentation variables. You can set a default value for these variables in the filter criteria. I.e. something like @{variable_a}{‘Please make a selection’} and the same for b. Make your dashboard prompt as usual but make it set 2 presentation variables instead of being a standard, column prompt.

    When the report attempts to run, nothing will come back initially because of the default values don’t exist in your database so you will get no results. However, in OBIEE 11g we have the ability to change the default text of the ‘no results’ view (Criteria tab > Edit Analysis Properties icon). You could insert a nice custom message in there which says something like ‘Please make some filter selections and try again’, or you could leave this blank if desired.

    This is all theoretical and I haven’t tried a proof of concept so apologies in advance if this approach doesn’t work. I think it will be fine.

    Good luck,
    Paul

Leave a Reply