If you edited the column properties it should display fine in the graph. However, if it doesn't, you can also go to Edit graph properties -> Titles and Labels -> Formatting of data markers -> Number Format and set the currency symbol there as well, it should do the trick.

Can you put here a screenshot of how you defined the columns in your dashboard prompt?

Create 2 variable prompts like the one in image below, one for pv_startdate and one for pv_enddate. Then, create a report where you have a filter such as the one below. Put everything in a dashboard, it works fine.

Hi, First of all, why are you using 2 variable prompts and not a normal column prompt? Do you only have a calendar date column or do you also have a start date and end date columns? For your 1st query, if you use a normal column prompt with your calendar date column, you can just set the operator to "is between" and just…

I'm not really sure about what you have but assuming you have a dashboard prompt with the column year, set a presentation variable for that column (pv_year) and then in the report, for the columns you want, set the column heading as @{pv_year} and @{pv_year-1}. It should pick up the values from the prompt and set them…

If you have reports with tables already created and you just want to make sure that new columns are not added to the existing views, you can do that in the analysis properties (see image below).

Assuming you have a date column you can use, just create a dashboard prompt with that column and in the choice list values choose the option "SQL Results" and use the following query (built the example in sampleapp V506). SELECT "A - Sample Sales"."Time"."T00 Calendar Date" FROM "A - Sample Sales" WHERE ("Time"."T00…

Get the physical query of a report you built and said it retrieves data. Do the same for a pre-built report and compare the queries. Identify the differences between them and go from there, you need to narrow it down, hard to say what the problem is otherwise.

That piece of your log already suggests that you probably not have the correct DB and/or schema configured in your RPD. It says that the table doesn't exist so it isn't issuing a query to the correct schema. Not sure what you followed in the Oracle documentation but you need to make sure that whatever you have defined in…