How To Fix FDT_CORE358 - Element type has been changed from '&1' (active version) to '&2'

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 358

• Message text: Element type has been changed from '&1' (active version) to '&2'

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_CORE358 - Element type has been changed from '&1' (active version) to '&2' ?

  The SAP error message FDT_CORE358 indicates that there has been a change in the element type of a field in a data model or a form. Specifically, it states that the element type has been changed from one type (denoted as &1, which represents the active version) to another type (denoted as &2). This typically occurs in the context of SAP Forms and Data Transfer (FDT) where data structures are defined.
  
  Cause:
  
  Data Model Changes: The error usually arises when there are changes made to the data model or the structure of the form that are not compatible with the existing definitions. For example, if a field was originally defined as a string and is now defined as an integer, this inconsistency can trigger the error.
  Version Mismatch: If there are multiple versions of a form or data model, and one version is being used while another version has been modified, this can