Repository content check list for BI Services compatibility

This section shows a check list of rules that a BI Services repository must follow. A BI Services compatibility check is performed in a BI Services environment in two cases:

A repository database is registered in a BI Services environment, that is, the Repository Service creates a repository registration. If the repository does not pass the BI Services compatibility check, the registration will not be created and an error message is shown.
Whenever a repository worker connects to the physical repository database for the first time, a check ensures that the BI Services rules are not broken after the repository was registered in the BI Services environment as you still can connect to it from an on-premise environment.

If the repository content does not follow these rules, the connection to the repository in a BI Services environment cannot be established:

The repository must not be linked to the user management of another repository.
No role must have the permission Total Control except the Supreme Administrator built-in role.
No user may have assigned the Supreme Administrator built-in role except the System user.
Only database interface version 1.14 must be enabled to prevent on-premise applications to access the repository while it is being used in a BI Services environment.
The repository may only use authentication system providers that are supported by BI Services. Besides Basic authentication, supported authentication system providers are Windows and Infor Federation Services.
The Repository Permission Management roles and the User Management roles (SSO roles) have been merged into Repository Roles in BI Services. To use the repository in a BI Services environment, matching pairs of Repository Roles that have identical names in the Repository Permission Management and the User Management must exist. A Repository Role is consistent, if a role with the same name exists on Repository Permission Management and User Management level.
The same users and groups must be assigned to the matching pairs of roles on Repository Permission Management and User Management level.
Each project can contain up to one OLAP Permission Management, one Application Studio report catalog, one Dashboard Catalog, and one DataLink Model.
A Dashboard Catalog must exist in each project.
The project must contain one single default language.
Any project must not contain a Financial Consolidation, Visual Framework, or Office Plus report catalog.
Project roles, report catalog roles, Dashboard Catalog roles, and OLAP roles have been merged into Application Roles in BI Services. To use the repository in BI Services, matching roles that have identical names in all nodes of a project must exist.
All matching roles that build an Application Role must be assigned to the same users and groups as the project role.
It is allowed to have one single OLAP role. It is not allowed to have an OLAP role and the same role on one other role level. The role must exist either on all role levels or as a single OLAP role.
It is not allowed to define the Edit permission without the Delete permission and vice versa in all nodes of a project, because the two permissions have been merged into the Edit permission in BI Services.
If the Administer permission is given in any role, all matching roles must contain it as well.
The repository must contain the Administration application, which allows to administer the repository in the web. Use the Farm Expert tool to add the Administration application to the repository when registering the repository to the Farm.
The repository must contain users who have the Farm Administrator role. Use the Farm Expert tool to add the Farm Administrators to the repository.
The repository must contain users who have the Repository Administrator role. Use the Farm Expert tool to add the Repository Administrators to the repository.
The repository must contain users who have the Application Creator role. Use the Farm Expert tool to add the Application Creator role to the repository.