Page History

...

1. Protect the restaurant with a preset object privilege.
   
2. Disable those privileges for the role, the restaurants of which should be made inaccessible.
   
3. As a result, the role users will not see those restaurants, for which they do not have privileges. The method works for all preset interactive and web reports. !
4. This method might not work for custom reports. In this case, you need to adjust the value selection request for the Restaurant parameter — parameter — just copy the request for the same parameter from any predefined report. To do this, open the report parameters and edit the SQL request.
   Image Added
5. For the parameter, you can create a list of values, from which the user will select the required ones by setting the relevant filter flag:
   Image Added
   This list is created via an SQL request in the parameter settings.
6. In the parameter settings of the created report data set, specify the same request for the Restaurant parameter, as in the data sets of the predefined reports for the same parameter. The request for the Restaurant parameter in predefined reports is intentionally configured in a manner considering the availability of restaurants to the user according to privileges.
   Image Added
   

Troubleshooting

Connection issues

• Error: You are not authorized

19.12.2019 17:22:01.743> [LOG]User

...

 entered incorrrectly    
19.12.2019 17:22:02.080> [LOG]You are not authorized

...

   
19.12.2019 17:22:12.893> [LOG]After registration: code 2, Server re-registration
19.12.2019 17:22:28.217> [LOG]After registration: code 2, Server re-registration

Reason: In the Feature Server connection settings, no database user is specified.
Solution: Open the IRReportsFSPrj.ini file, and in the connection_string field, specify the correct connection string with a username and a password. For example:

...

Issues concerning SQL collation

Possible Error: " Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Lithuanian_CI_AS" in the equal to operation".

As a result, some IA reports may become non-functional.! As a solution, check

Solution: Check the sorting settings of the SQL server and the DB itself (Fig. 34see the figure below). After that, re-create the STAT aggregate databases.In order to re-create the aggregate DBs, proceed as follows:1.

1. Stop the

...

1. FeatureServer
2. Execute the following script in the main database: UPDATE [dbo].[DBInformation] set [DBVer]=0 where [Alias] = 'Agregates'

...

1. Delete all aggregate

...

1. databases (STAT)

...

1. Launch the

...

1. FeatureServer.

Fig. 35. Database properties — sorting parametersImage Added

Issues when importing the report from an XML file

If problems of such kind arise, the error may read as follows: "Possible Error: Could not find stored procedure 'RPL8_GET_CURRENT_DATABASE_GUID"
The issue problem is related to caused by the absence of certain tables and procedures. You should perform

Solution: Perform the following scripts:

USE [RK7]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[RPL8_TRANSACT](
 [ID_INC] [int] IDENTITY(1,1) NOT NULL,
 [GUID] [uniqueidentifier] NOT NULL,
 [SERVER_GUID] [uniqueidentifier] NOT NULL,
 [DTS] [datetime] NULL
) ON [PRIMARY]
GO
CREATE PROCEDURE [dbo].[RPL8_GET_CURRENT_DATABASE_GUID] 
(@SRVGUID uniqueidentifier OUTPUT ) 
 AS BEGIN 
 SET @SRVGUID = NEWID() 
 END 
GO

...