Customized export option is not working in dashboard reports in OAS after migrating from OBIEE12c

Question

Hi,

Recently we have upgraded the BI server from 12c to OAS. After reports migration to OAS, we have an issue with customized export option.

we have created customized export option in one dashboard using java scripts. by using that same script, able to export in obiee12c but whereas in OAS it is not working as expected.

I need someone help here, how to achieve the custom export option in OAS reports, it could be greatly appreciated if we have solution for this.

Regards

Gopi

Federico Venturin - Oracle · Answer

Hi @User_DCJG6 ,

Your script is a customization that you (or someone else) wrote for OBIEE 12c. It has NOT been provided by Oracle as part of the tool, and certified to work in OAS.

As I already wrote, several things are different in OAS compared to OBIEE 12c. I would check whether the functions and classes referenced in your code are still available in OAS (e.g. saw.menu.popupByRefObj, saw.stopEventPropagation, NQWMenuItemWIconMixin class, etc.) and eventually fix them as required.

Gopi Krishna P · Answer

Hi Federico,

That java script was there in OBIEE 12c existing reports we just migrated those reports from OBIEE 12c to OAS as a part of migration. I am logging in using WebLogic. this Script passed as a text in dashboard and also "Contains HTML/JavaScript/CSS Markup" option enabled for that text.

same is working in BI12c but not in OAS. Below is the script.

Federico Venturin - Oracle · Answer

Hi @User_DCJG6 ,

Even if OAS looks mostly the same as OBIEE 12c (at least for Classic Analytics and Publisher), a lot of changes happened under the hood, and these can impact existing customizations.

There is no magic button that will make your customization works again, and we can't help without knowing how the customization has been implemented.

Did you implement it as a weblogic application? If so, did you remember to deploy it in the new environment as well? Is your customization based on API calls? Did you check that the endopoint and the syntax are still the same in OAS? Is your customization processing the HTML of the page? This has probably been updated compared to OBIEE 12c, so it's first thing I would suggest to check