There are different approaches to organizing folders on the MS SQL Server Reporting Services. One of them is to group reports on topics or modules and grant access to all users of iScala. The advantage of this approach is in simplicity, but the disadvantage is that anyone can view any report. In this article I will share a more complex, but much more «advanced» way to organize folders and access not only to the reports in them itself, but also to restrict access to data in these reports.
In the picture below you can see the folders associated with the department numbers (in iScala this is the accounting dimension 1 «Department»):
Every employee has access to the shared folder «Departments», but inside it only in the folder of his own department. In other words, in the folder 1002, for example, only employees of the Front Office department have access, and other users are not allowed to it. The reports themselves (the originals) are in a separate folder where users do not have access, but we can create «Linked Reports» in the departmental folders, which are a kind of shortcut to the main report, but they have their own set of parameters. To create such linked report, you need to do the following:
- Choose the original report and click on the item indicating the drop-down menu. Next, select the command «Create Linked Report»:
- Copy the name of source report as the name of the linked report and click the button «Change Location»:
- Select the folder where you want to place the linked report and click «OK»:
- After you return to the linked report creation form, click «OK»:
- The report server will generate the associated report. But we still need to change the parameters, for which we need to go into the «Manage» mode. To do this, click on the report title in the navigation line:
- After switching to the «Manage» mode, go to the parameters tab:
- This picture most interesting 🙂
In the report there is a parameter with the department code (Accounting dimension 1 in iScala).
- As a result, users of department 2301 will see only a set of «their» warehouses, and warehouses of other departments will not see:
- And for the financial department, the hidden parameter «Dpt» is set to «*» and users of this department will be able to see all warehouses
You can read additional article about automation of creating linked reports in case of complex folder structure (sorry, in Russian only) «Автоматизация создания связанных отчётов при сложной структуре»
If you have any questions, do not hesitate to ask:
Other procedures and articles in English:
- Scala/iScala и электронная отчётность в России | Scala/iScala and e-reporting in Russia
- Добавлено описание структуры таблиц БД iScala 3.3 / A description of iScala 3.3 DB tables structure has been added
- Структура таблиц / Table structure Epicor iScala 3.3 (x64) — 3.3.0419
- Looking for the perfect ERP system. iScala’s strengths and weaknesses
- About different approaches to implementing iScala one more time
- Структура таблиц / Table structure Epicor iScala 3.2 (x64) — 3.2.0317
- AFR: Как сделать расчёт значения в столбце зависимым от номера строки? :: AFR: How can I calculate the value in a column dependent on the line number?
- Query execution failed for dataset ‘DataSet0’
- Структура таблиц / Table structure Epicor iScala 3.1 — 3.1.0511
- SQL Server: OLE Automation Procedures
- Знаете ли Вы, что? Новая фишка в последней версии AFR: перенумерация строк :: Do you know that? The new feature in the latest version of AFR: renumbering rows
- Multi Level Approvals for Requisitions: How it works?
- MSRS channel — what to use instead in case of very old version of Scala/iScala?
- How to add a document template for MSRS Output Channel
- Заявление / Memorandum
- Deploy existing AFR reports on another server
- How to delimit user access on the Reporting Server?
- Standard steps when working with the «Purchase Order» module
- Изменение структуры таблиц iScala 3.1 по сравнению с iScala 3.0 FSP4 / Table structure changes between iScala 3.0 FSP4 and iScala 3.1
- История изменения структуры таблиц разных версий iScala / Tables structure changes history from iScala 2.2 SR2 to iScala 3.0 FSP4
- Процесс создания отчёта фиксированной формы с помощью Epicor AFR :: The process of creating a fixed-form report using Epicor AFR
- The most common mistake when working with AFR reports
- Структура таблиц БД / DB Tables Structure: Epicor iScala 3.0 FSP4 — 3.0.4267
- AFR: что это такое, из чего состоит, с чем взаимодействует? :: AFR: what is it, what does it consist of, what it interacts with?
- Usage of external tables with primary data. How to design Daily Budget Report.
- How can I create an AFR report in 2 currencies using fixed rate?
- How to create AFR report with daily budgets from iScala?
- Типы проводок Главной Книги :: General Ledger Transaction Types
- Reporting tools usage survey
- Sent PO electronically to Supplier’s FTP site
- Requisition Management module quick user guide
- What can you get from your iScala by using new technologies?