You can set it in DV > console > System Settings > Portal Path, just enter the path of the dashboard you want to use. And you can't change the behavior of the "Home" link in the top main menu in OAC : the homepage of the product is a different thing than the "starting page" you can set in "My Account" (or with the Portal…

I see what you are looking for and it's absolutely valid (and that's the default behavior of classic prompts in general for the same exact reason you said: to not change visualization, and the relative queries fired, till the filters are all set). Seeing a bit where DV comes from, I suspect it isn't an existing feature,…

edit: OP first reply was that my request for more info was pointless and not helping him at all. Now he did decide to provide more details and "look good" in the forum after this reply was posted (his reply at 21:16, my reply at 21:21 and him editing his reply at 21:32 CET). I will do as said and stay away from his thread.…

You say who is member of what group, what these groups are supposed to allow their members to do, what is the ideal behavior and then apparently complain about the current behavior. But what does your current security model looks like? Because yours is an extremely focused question on your own specific security model, but…

I would say these settings have no impact on DV. They are the settings for classic prompts that required to change the OBIPS config file (instanceconfig.xml), something that isn't possible in OAC and that's why they added these settings into the DV Console System Settings page (a way to change the things that can only be…

Of course you can't pass 'Jul-21' to your filter on "Accounting Period" if that was expected to a number 1-12. But if your time dimensions know how to handle the conversion, you can use a filter on "Month-Year" = 'Jul-21'. I would say that the problem is anyway not there: my report has 60 unions No idea what your analysis…

Yes, 2 LTS is what I had in mind as that's the only way in the RPD to get a union result. Otherwise you can of course build a view or a unified table in your database, but if have that option you probably wouldn't be asking :D

The physical tables can be 1, 2, 10 or how many you want. It's up to you to decide how to model them, to give them a role. Of course if you have data problems (missing way of connecting things) even modelling isn't going to help you. But otherwise it doesn't matter if it's the same table or not, as long as you have enough…

Model your table in the RPD as having 2 sources, one targeting the first column and one targeting the second column. The tool will do the job of doing the 2 queries and joining the results together.

First build solid foundations before to add extra floors on top? 100%! But I don't know why when I see DV I can't stop thinking at this...

Another proof that DV is not a replacement for "Classics" and it's time to stop forcing using DV just because it's the only piece being developed (trying to catch up with 15+ years of "Classics" doing the job perfectly).

when I select Jul-21 in drop down of dashboard prompt, then Period Number 6 should be returned to my analysis for further calculations in the criteria. That's a business rule you should cover in your model somehow. The tool is smart but doesn't do any magic. How is it supposed to know that July 2021 means period number 6?…

Sure, add a calculation. It is only inside the workbook and doesn't need a dataflow, and let you do a bunch of things, including pointless things like this example of a sum of 2 numbers coming from some attributes.

Classic can be embedded just like content of OBIEE has been embedded in the past 10 years. Security is of course always something you have to deal with and worse case you will see the login screen first. The DV way is totally different and things have been developed around to make it embeddable, while classic is more a DIY…

@davidkhala-Oracle when you did check the logs, didn't you find messages like the following? [VALIDATION] [ERROR]:Password contains invalid characters [VALIDATION] [SUGGESTION]:Ensure password contains only alphanumeric, underscore (_), dollar ($) or pound (#) characters configuration Failed. Exiting configuration due to…

Can you report it as a bug? Technically the database accept '-' in a password, but it must be quoted. This makes me say that it's a limitation in the application and a design choice to use unquoted passwords, excluding '-' and a number of other special characters. Because of that, I do expect the application to check if…

Sadly I don't have one because I don't have a CSI allowing me to open SRs for on-premises products, I only have a few for cloud products (but I can't really report a RCU bug for OAC as it will not be accepted). I did send all the details directly to a PM (@Alan Lee - Oracle-Oracle ) in March 2022 who passed it to the team…

Just a last comment: if your database has compressed tablespaces and the RCU try to create the schemas on those, it will fail. There isn't an error saying it's because of compressed tablespaces but it just fail to create some objects in the BIPLATFORM schema and therefore rollback everything else. I did report the bug…

The RCU is located in ORACLE_HOME/oracle_common/bin/rcu , you can find details on how it does work by command line in the OBIEE 12.2.1.4 doc (as the RCU didn't change much, it's only the content of the schemas that evolved):…

True, in a full install with a separate execution of the RCU. That's the process to follow if you don't have a SYSDBA account. The issue is that the marketplace image does use the implicit call for the RCU creation when calling config.sh, that's also why it doesn't show much details of what the RCU is doing and really…