The examples are based on the sample Access database provided by option when installing Interactive Reporting on a Windows platform, using the Interactive Reporting database connection file Sample.oce.
For these examples, the users BRIO and VIEW&PROCESS require access to data that is denied to the rest of the users. These two users both belong to the group AMERICAS, which corresponds to a region of the same name. However, the user BRIO is a corporate officer who should be able to see all data.
Only one piece of data will be accessed in the course of these examples: the amount sales column from the sales fact table. The examples are more far-reaching than this might seem.
Screenshots for these examples come from theInteractive Reporting documents to which processing restrictions are applied, and from the sample Interactive Reporting document, row_level_security.bqy, mentioned earlier. For the screen shots from the sample Interactive Reporting document, the columns in the BRIOSECR table follow in a top down, left to right manner for the most part with the fields on the screen. Deviations from this will be noted where possible. In particular, though, note that the UNIQUE_ID column is not shown in this sequence of fields, appropriate to its optional role to the functionality of the software, although it is used behind the scenes by the sample Interactive Reporting document.
Figure 8, Database Layout Showing Possible Joins shows the layout of the data in the database, to illustrate the possible joins as intended by the database designer.
Figure 9, Data Model in the Published Interactive Reporting Document shows the data model in the published Interactive Reporting documents.
