I have no idea where to post this because the redesign as made things much more difficult.I had book marked the following because BusinessObjects Web Intelligence is my primary area of interest...https://community.sap.com/t5/c-khhcw49343/SAP+Business...
BusinessObjects BI 4.3 was released almost four years ago, but my company upgraded from 4.2 just over a year ago and we are still learning and figuring out the particulars of the new interface. We did a subsequent patch a couple of months ago and are...
We upgraded from BusinessObjects environment from 4.3 SP02 Patch 8 to 4.3 SP03 Patch 8 one month ago. It went relatively smoothly with no major issues discovered yet. We had begun targeting 4.3 SP03 Patch 5 about 6 months ago, but one week before we ...
We have all seen questions with sample data provided as text like this...ID | Some Description | Some Date | Some Number1 | Whatever… | 1/15/2024 | 1502 | Something else… | 1/31/2024 | 2003 | Still more… | 2/1/2024 | 500Or in a table...
We have 4.3 SP03 Patch 5 installed in our test environment. I came across an odd issue in Web Intelligence which I have reduced to this. In a free-hand SQL query when prompting for a date I do not get the calendar by default. Instead, I get this…
...
I cannot figure out how to get the current date as the default value, but it seems you don't need that.This is working for me...@Prompt('DatePrompt','D',,Mono,Free,Not_Persistent,{'1900-01-01'})If you do not associate a table, you will get the same e...
Can you provide more details on how you envision using this? Do you just want to prompt for a date value and not actually use it to filter on anything?
What is your DDL statement?Web Intelligence is a reporting tool. I both would not expect DDL statements to work and would expect them to not work. In other words I am not surprised they do not work and I would be alarmed if they did. Imagine the chao...
This isn't just a 4.2 to 4.3 change. We are on 4.3 SP03 Patch 8 in our production system and the use case you are describing generates the following message...Not sure exactly with which patch this changed, but now it is as you are seeing.It would be...
