You just need to create a series of Conditional Action Links - one for each condition this way you'd only have one link displaying as required for each condition.

Look at Boris Dahav's blog post right at the bottom.

@Thomas Dodds, couldn't have put it better myself (I tried!).

Excellent! Please mark answer as correctto help others who may have a similar problem.

If you are a developer then you have every right to have access to Catalog Manager. it is one of the OBIEE Development Client tools. All you need is accessible from Catalog Manager

You'll need to do a search on an offline copy of your catalog using catalog manager:

A workaround would be to simulate the View Selector by creating a Dashboard Variable Prompt which effectively is a drop-down with values for each of your views. This variable prompt will in turn populate a presentation variable which should have a value for each view. This presentation variable will then be used in section…

have you checked the BI Server log file? There should be some errors in there which should give you some kind of guidance. You can paste the excerpt of the log file in the post which can be found here: <obiee_home>/user_projects/domains/bi/servers/bi_server1/logs

you can get that information in Catalog Manager

It might be easier for you to explain your issue with some screenshots.

Are you migrating directly from 11.1.1.5 to 12c? Oracle's 11g - 12c migration documentation states that the migration should be done from 11.1.1.7 and above. I would strongly recommend that you upgrade to 11.1.1.7 or higher 1st before the migration and see if this corrects these issues that you are experiencing.

Sounds like you need to model your data warehouse to include slowly changing dimensions to capture changes to dimensional attributes. https://en.wikipedia.org/wiki/Slowly_changing_dimension

haven't been following previous conversations but I would stringly suggest listening to the advice given to you by @Gianni Ceresa and @Christian Berg

You'll need to add a WHERE clause to the Logical Table Source of your Logical Fact to ensure that the query will have the D2 WHERE clause even if D2 attributes aren't part of report/query

That’s correct. The joins are defined in the physical layer and the logical joins just define the type of - inner join,left outer, right outer, full outer for example.

The most important thing to note about multi subject area reporting is that both subject area must be derived from the same logical business model. Your other question about the common fields. Well, from a user perspective, it would make sense for the columns to have a common name across subject areas although there is no…

Maybe you need to go one level down in the catalog path so that you're in the folder that has the "root" folder as a sub folder - just checking...

You could duplicate the column in the repository and exclude the descriptor ID from the duplicate.

I would suggest that you remove all filters from the logical query that you’re trying to seed. This will ensure that all requests are covered for all possible filters for all users.

11.1.1.7 is only certified to work up to Windows 7 (11.1.1.7.0) Certification Matrix - Oracle @Christian Berg wrote an article on this: https://dimensionality.ch/2017/05/06/installing-oracle-bi-on-windows-7-8-10/