Calendar date prompts

Question

I am on 11.1.1.5. I am creating two calendar date prompts begin date and end date for an analysis. I want to be able to generate some kind error message or warning if the user tries to enter a date smaller than begin date in end date prompt. How can I do this?

Answer 1

@Amith, no the link would not accurately satisfy the OP's need. What if the user chooses a valid date (i.e., in the allowable date range), but the report produces no records? The customized "No Results" message, would say, "Please choose a valid date value" and would be incorrect.
user12301184 wrote:
I am on 11.1.1.5. I am creating two calendar date prompts begin date and end date for an analysis. I want to be able to generate some kind error message or warning if the user tries to enter a date smaller than begin date in end date prompt. How can I do this?@user12301184, what you need to do is this:
1) Create a small report that returns rows if the dates selected in the dashboard prompts are in the valid range, and does not return rows if the dates chosen are outside the range.
2) In the dashboard, move a Section to the workspace and put your main report there. Click on Section>Properties>Guided Navigation and have OBIEE point to the small report created in step 1 with the radio button "Display when report returns rows" checked off.
3) Move another Section to the workspace and put a Text object in the Section. Click Section>Properties>Guided Navigation and point to the same report, but this time choose "Dispay if the report returns no rows."
4) Now in the Text object, put your customized message, "Please choose a valid date range."
5) Finally, in the report itself, you can customize your "No Results" view to say, "There are no records to display for the date range selected."
To summarize, according to the OP's criteria, there are two reasons why the report wouldn't show rows: one, specifically because of the invalid date range; and two -- not explicitly stated, but true nonetheless -- when the report itself produces no rows even though the date range is valid.
My solution takes into account both scenarios. It doesn't give a potential wrong error message like so many applications do when the scenarios are not thought out completely.