Tiles, Groups and Catalogs

This section provides an overview of the most common errors that may occur for tiles, groups and catalogs and gives you information on how to analyze and solve the issue.

Table 1:
Issue	Possible Reasons	Possible Solution
A tile is displayed with the error “Cannot load tile”.	An administrator deleted the tile from the catalog which is referenced by a group. Case 1: An end user personalized the group (e.g. by moving, deleting or adding tiles) Case 2: After deleting the tile, the administrator did not clean up customized or configured groups which use the tile.	Case 1: The end user needs to manually delete the orphaned tile. To prevent this issue, an admin can switch off the personalization of groups. See Editing Groups. Case 2: You can use Fiori Launchpad Checks (transaction /UI2/FLC) to identify the orphaned tiles in groups. Delete these tiles in the SAP Fiori launchpad designer. Note In general, tiles which may already be used in groups should not be deleted from catalogs.
A tile is not displayed.	There is no matching target mapping (semantic object/action) or device type. You can use Fiori Launchpad Intent Analysis (transaction /UI2/FLIA) for error analysis.	Make sure the target mapping configuration is correct. See Configuring Target Mappings.
	The tile is a reference tile and the reference is broken because the original tile was deleted. You can use Fiori Launchpad Checks (transaction /UI2/FLC) to identify broken references.	Broken references cannot be restored. The tile needs to be recreated.
	An admin has added a tile to a group. End users cannot see the new tile because they personalized the group.	The end user can delete the personalization in the SAP Fiori launchpad by resetting the group content. See Personalizing the Home Page To prevent this issue, an admin can switch off the personalization of groups. See Editing Groups.
A group or catalog is not displayed.	The catalog or group is not assigned to a PFCG role. You can use Fiori Launchpad Checks (transaction /UI2/FLC) for error analysis.	Assign the group or catalog to a PFCG role. See Assign Tile Catalogs to Roles.

General Tips

The following guidelines help to avoid some of the issues mentioned above:

Do not delete published tiles but adapt existing tiles to their new purpose or delete/change the target mappings which the intent of a tile is referencing.
Admins do not fully control the lifecycle of personalized groups. Since this can cause issues, you should consider switching off the personalization of groups to prevent end users from removing or editing them.
See Editing Groups.