How To Fix /UI2/FDM220 - Tile &1&2: Custom Tile data could not be extracted for Tile Type &1

/UI2/FDM220 - Overview

• Message type: E = Error

• Message class: /UI2/FDM -

• Message number: 220

• Message text: Tile &1&2: Custom Tile data could not be extracted for Tile Type &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

/UI2/FDM220 - Details

• The SAP error message /UI2/FDM220 Tile &1&2: Custom Tile data could not be extracted for Tile Type &1 typically indicates that there is an issue with the extraction of data for a custom tile in the SAP Fiori Launchpad. This error can occur for various reasons, and here are some common causes, potential solutions, and related information:
  Causes:
  
  Missing Data Source: The data source for the custom tile may not be properly defined or may not exist.
  Authorization Issues: The user may not have the necessary authorizations to access the data required for the tile.
  Configuration Errors: There may be configuration issues in the tile definition or in the underlying OData service.
  OData Service Issues: The OData service that the tile relies on may be inactive, misconfigured, or not returning data as expected.
  Backend System Issues: There could be issues in the backend system that prevent data from being retrieved.
  
  Solutions:
  
  Check Data Source: Verify that the data