Complex view in universe

[former_member961369]

Hi Guys,

I am using one complex view to create one report. But the report filters are not working, the LOVs of filters are keep on loading. Any suggestions to overcome this issue.

Are the indexes not working through view?

Any help appreciates.

Thanks,

Bhaskar

[former_member4998]

Hi...

Best Practice that has been applied is that LoV objects are created in the Business Layer, unless is it necessary to bring it in the Data Foundation layer (when being used by e.g. Derived Tables).

Parameters and LOV’s that are created in the Data Foundation are available, but not maintainable in the Business Layer. The can be recognized by the fact they show “(inherited)” after their names in the Business Layer.

These settings enforce different behaviour on report level when a prompt is defined on these objects

[former_member961369]

Still we are using BOXI 3.1

My question is why the LOVs are taking much time.

For a better explanation:

We have created a view in DB for a specific report usage. All the fields in the report are from the view only. So the report we need add some prompt filters to it.

Issue: For a specific report prompt filter LOVs are not refreshed quickly and even keep on refreshing...

don't know where it's going wrong.

[Former Member]

Why are you writing a view for a specific report? That's not best practice.

If your view is slow, speak to your DBA about tuning it.

[former_member182521]

Agree with mark here. Creating a report based on a view is not in line with the best practices.

Alternatively you can create a Materialized view and you can refresh the MV based on your data refresh of your Database tables. As your report is created on top of view, Your LOV's could also be created using the same view. Is'it it?

[former_member961369]

Yes, LOV's are also created based on View. But now i am thinking to point the LOV's to the other reference table.

What do you think?      Hope this will work.

[former_member182521]

Absolutely. refer the actual table used in view instead of view.