Hide if condition implementation b/n OBIEE 12c and OAS 6.4

User_0MYT7

Recently migrated OBIEE 12c into OAS 6.4. Presentation columns with hide if condition defined in OBIEE 12c rpd works fine when used in column prompt at run time and users will be able to enter/select values from those columns even if the hide if condition evaluates to true and the columns are not visible in presentation table when accessed from answer. However, it throws assertion failures when used in OAS.

Error Code OAMP2OPY:ACIOA5LN - Assertion Failure

Is there any difference in handling hide if condition b/n OBIEE 12c and OAS 6.4?  

User_0MYT7

Thank you for the updates.

Issue resolved after updating the HideHiddenMetadataInViews parameter to false in the instanceconfig.xml file.

<SubjectAreaMetadata>

<HideHiddenMetadataInViews>false</HideHiddenMetadataInViews>

</SubjectAreaMetadata>

[Deleted User]

If you are getting assertion failures on something which used to work best raise an SR immediately.

Your OAS 6.4 is (2022 version) is close to becoming outdated with the upcoming release of OAS 2024.

EzequielC-Oracle

Hi @User_0MYT7

To enhance your experience and foster meaningful interactions, we encourage you to personalize your profile by setting up a display name and uploading a profile picture. Your display name will be how others recognize and engage with you in discussions, while a profile picture adds a personal touch to your forum presence.

Take a moment to update your profile with a display name and an image representing you. Let's create a vibrant and engaging community together!

Regards,

Ezequiel.

User_0MYT7

@Christian Berg we did an in-place upgrade from OAS 6.4 to OAS 2023 however we still see the assertion error with the following additional error messages:

Assertion failure: ErrorCalendaroControlTypeExpectCalendarDataType at line 4800 of project/webviews/promptview.cpp

The same error was logged under the obips/logicerrorreports/sawserver_logicerrorreport_promptview_cppline_4800

Anyone encountered similar issue? If yes, how did you resolve it?

Gianni Ceresa

I would say to do what Christian suggested before already: raise an SR.

Mostly when something references a .cpp file, that's a direct SR.

[Deleted User]

Beaten by Gianni. If it throws the same error in 2023 then raise an SR. .cpp's are their resort we can't really do anything on the forum level.