I remember when performing in-place upgrade to OAS 2024, we encountered same errors, which has been caused by "obsolete" config stuff in instanceconfig.xml in <Alerts> section- which needs to be removed - exactly as @RVohra has pointed above with reference to note, which gives you a guidance.

@Branden Pavol Thanks for this Tableau resources. Seems pretty flexible. Although we (as customer) wouldn't use this functionality (our fiscal year is equal to calendar year), I am voting for this idea, could be useful and would help to slightly mitigate the difference in functionality compared to Tableau.

@Branden Pavol How you would "automate" different start of Fiscal Year in this scenario ? For "astronomical" calendar (year always beginning 1.1.) , this is crystal clear, but for fiscal period hierarchy you definitely need to maintain your own "calendar" dimension table, which includes your fiscal period specifics and…

@Avinash Krishnaram-Oracle Avinash, thanks for providing update. But when looking at the details of implementation, but I can't help to ask: Isn't this too complicated, wouldn't be better/simpler (certainly from the end user's point of view, I don't know how from the point of view of implementation effort) to allow…

@Kartik Mali-Oracle What you pointed in your Idea is a pain point, we are fighting on our OAS environments (when "migrating" from Dev to Prod) for pretty long time (seamless incremental deployment of DV objects between environments , which comes hand in hand with better form of internal Ids of DV objects) and I am pointing…

Could anyone from Product Mgmt ( @Benjamin Arnulf-Oracle, @Bret Grinslade - Oracle Analytics-Oracle) explain, why status of this Idea (after some inquires/discussions within user community) has been changed from "Planned" (this status has been set in January 2024) to "Needs Votes" ? I think we deserve the explanation.…

@User_SD8BZ Your fresh Idea is duplicit to this one: https://community.oracle.com/products/oracleanalytics/discussion/10686/view-selector-feature-in-dv-similar-to-obiee which is in Planned status - so pls, drop your Idea and give vote to this one. Thanks.

@Bret Grinslade - Oracle Analytics-Oracle Hi Bret, thanks, from your answer it is clear that this "versioning" Idea is not part of planned "Unified Catalog" feature. But this Idea is in "Planned" status since January 2024 (as already pointed) and this is (I guess) pretty long time to be included into product roadmap ,…

@Benjamin Arnulf-Oracle Hi Ben, latest product roadmap from September 2025 is not very specific for this particular functionality. As pointed by @Patrick Koob , it could be part of "Unified Catalog" feature, but it is not clear. So having better idea, what "Unified Catalog" includes and what not (ands whether it covers…

@Pravin Janardanam-Oracle Thanks for confirmation, I appreciate it. Is it the same case for Ideas I have created and has been put into Planned status recently:…

@Pravin Janardanam-Oracle Pravin, thanks, great to hear it will be implemented. One question: Will it get into January 2026 OAC release to have this in OAS 2026 ?Otherwise we would have to wait till OAS 2027 - which is incredibly long period to wait…. Thanks

@Rick195 Actually implementation of this feature will give us in web based Semantic Modeler similar level of "comfort" as we used to have in BI Administration Tool. So all features/functionality missing in Semantic Modeler and are present in BI Admin Tool and makes your metadata developer live easier should be transferred…

Hi, I cannot speak on behalf of Oracle, but in general "Classics" represents more governed/enterprise approach (tided together with more sophisticated data modelling in so called Semantic Model - which btw can be leveraged in DV and vice versa "agile" modeling in DV data sets can be leveraged in "Classics") whereas DV is…

@Ancy Paul-Oracle Why don't you simply bind date/datetime column (which you want to default to current date) in dashboard filter with system defined parameters Current Date/Current DateTime (https://docs.oracle.com/en/middleware/bi/analytics-server/user-oas/system-parameters.html) - those parameters are having values, you…

@thorpw Glad to hear, it is working. I have been fighting with making it running as well. Documentation has gaps in that sense (basically variables mentioned in bullet "2 Set the environment variable required by the Oracle Analytics Server Platform" in Doc needs to be set during OAS startup to work correctly). I hope, that…

Ok, in this case I recommend opening SR with Oracle support and try to solve it with them. In normal circumstances this should work, so apparently this issue is connected with your OAS environment (and possibly configuration, database against which your data set is created). It should not be an Idea for product…

Hi @Kartik Mali-Oracle , as I already written EVALUATE function used in analysis (calculated column) , which is created based on DV data set, is working in our OAS environments perfectly. I don't understand what you mean by "DV datasets as Subject Area" ? I am not familiar with wording - do you mean ordinary data set…

@thorpw And have you set env variable OAS_FORMATTED_EXPORT_ENABLED=true correctly ? It needs to be set during a startup of the whole OAS instance to be effective (not just in script, starting NodeJs process. We placed it in shell script «Domain Home»/bin/setUserOverridesLate.sh.

@Kartik Mali-Oracle How did you come to conclusion, that : " EVALUATE function is not working on the analysis which are created on dataset as subject area" ? Just to make clear - do you mean in analysis, which is created out of data set (as opposed to creation out of Subject Area) ? If this is what you meant, than EVALUATE…

@Luis E. Rivas -Oracle Since you marked this Idea as "Delivered" pointing to new feature launched in OAC September 2025 release : "LLM-Based Column Name Recommendations in Oracle Analytics" I would like to ask : Is this feature (as it relies on LLM) going to be available in OAS as well? My guess is that the answer will be…