If the code of this view doesn't work directly as source for a dataset in OAC, I would call it a bug. Because you weren't returning JSON objects (or the view would also not work when used in OAC), and it's the dataset definition having a bug in not being able to handle something correctly, and also not being able to report…

@User_0K99C , What product are you using? OAS or OAC? If you are on OAC you don't really have access to anything, but if you are in OAS you should still be able to see some kind of logs maybe telling you what's going on.

The question has been moved in the OTBI category. Being a "content" question, you could also consider asking in the Fusion forum if you find a matching category ( ).

Hi, Could you please share product name and version? Based on your reply the question can be moved to the right category, or you can be pointed to the forum covering the product you are using (if it's a Fusion product).

@User_T2LGL , As Arjun mentioned, this is not the right forum for your product. You should find a forum covering your product and post there (this question can't be moved there because it's a different forum instance). Other forums you could explore to see if they cover the product you have a question about are:

@User_W0H93 , Yes, "classic" (everything /analytics) didn't really change. All the permissions and privileges is the same and behave the same.

Because you are on OAS 2023 already, how about upgrading to OAS 2024? You could then consider using the Semantic Modeler instead of the Model Administration Tool. Just make sure your RPD is "compatible" (currently only relational sources are supported), but if it is, it will make your release / promotion of code a lot…

Thanks @Lisa O'Kelley for the details. The question has been moved to the Publisher category so you can get a better answer.

You said "report" a few times: is this a Publisher report? Or is it an agent and your "report" is an analysis?

Ok, so you are on OAC and are trying to write that as a filter in a "classic" analysis. The thing is that you are writing Oracle Database SQL syntax, but the filter in a "classic" analysis does speaks LSQL. You simply have a language mismatch: you are using the wrong syntax, the wrong languages. In a filter you can only…

EBS isn't really covered in this forum but in two of the "parallel" forums. Try asking there. The question seems to be about data or EBS processes, therefore those forums will definitely be able to provide you more answers.

Nobody here can see your screen and know what you are doing, how, where. You should consider providing a minimum of context. Things like a product name and a version to start with, where you tried to enter that expression etc.

OAS 2022 is out error correction support dates, you should consider upgrading to a supported version (OAS has a lifespan of about 2 years, a version is supported a year after the release of the next one, and it is being released on a yearly base). Your source is Essbase? And the exact same MDX query is generated by the 2…

What Steve said … It isn't the XML of the analysis generating duplicates, it's more mistakes in the modelling, wrong logical keys and things like that, generating a different query. For example: does your RPD contain any warning or error? There shouldn't be any, you should fix them to start with a "clean" state, then…

Hi @User_5TZYH , As long as you didn't modify those tables manually, the way they are created by the RCU is covered by the OAS license. They are "product's tables", the RCU does create them the way it needs them. Of course it doesn't mean you can start using compression for free on your own tables, you don't have a license…

I imagine the question was meant to know if a "cheat" workaround could be achieved by using a pivot instead of a table. Still, the folder heading (by default being the presentation table name) doesn't exist as a concept in DV for now. For that one visualization example you posted, the cheat will work, but having to make up…

Hi, To be fair I never tried. That type of objects can't be created anymore, there are good chances the code has been fully removed. I imagine they will just be "unknown" kind of objects. I don't expect them to display anything useful (no data), and probably an error of "unknown" object could be visible in the page. But…

Hi, If you ask about a Fusion product, you should ask in (there are many categories, find the best match). This forum is for Oracle Analytics.

As far as I know, in a DV workbook the table and pivot visualization do not have the concept of "folder heading".

Everything you can do in OBIEE can be done in OAC: "classic" didn't move (except for OSSM that isn't there at all anymore). Therefore just do the exact same thing. Or maybe by "OAC reporting" you mean a DV workbook?