As there is not much documentation to be found on business views; I'm trying to figure the pro's and con's on using business views. E.g. is it possible to leave fields behind from the original master(s) in the business view master? Is other kind of filtering possible rather than on DBA? Further I noticed that defined fields disappear after the master editor closes? When would you use a business view and when a reporting object?

This message has been edited. Last edited by: SWES,

Hi SWES,

Off the top of my head... Business Views are great if you want to leave fields out of your view that maybe the users don't have access to, or you just don't want them to use; you can "reorganize" the fields you include into user friendly folders if you have a lot of fields; you can give fields user friendly names so end users can find what they need quickly. Business views would be available to the users as any other master file and would be useful for those users that can totally create their own reports and graphs from scratch.

Reporting Objects, on the other hand, are designed more for directing users to a specific data source; certain selections (where statements) can already be made for them behind the scenes in the RO that they can't change; the report/chart can already be started for them giving them a base or head start on what they need; Filters can be added that they can just select from. Reporting Objects are great for users that you don't want creating reports and/or charts from scratch.

That is what I can think of quickly... I am sure other bright Focal Pointers can come up with even more differences and reasons to use one or the other.

Good luck!

Thank you for your reply Emily. It helped me getting to understand the difference between the two better. I also found out in the technical documentation there is more info about applying filters and creating defines on business views.

Thanks again,
Stephan