How To Fix /UI5/APP_API100 - Node &1 in provided JSON content is not a primitive string

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI5/APP_API -

• Message number: 100

• Message text: Node &1 in provided JSON content is not a primitive string

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 /UI5/APP_API100 - Node &1 in provided JSON content is not a primitive string ?

  The SAP error message /UI5/APP_API100 Node &1 in provided JSON content is not a primitive string typically indicates that there is an issue with the JSON data being sent to the SAP UI5 application. Specifically, it suggests that a node (or property) in the JSON object is expected to be a primitive string, but it is not. This could mean that the value is either an object, an array, or is missing altogether.
  Cause:
  
  Incorrect Data Structure: The JSON structure does not match the expected format. For example, a property that should be a string is instead an object or an array.
  Data Type Mismatch: The application expects a string value, but the provided value is of a different type (e.g., number, boolean, object).
  Missing Values: A required string value is missing, leading to the application interpreting it as a non-primitive type.
  
  Solution:
  
  
  Validate JSON Structure: Check the JSON content being sent to ensure that all nodes are correctly formatted as strings where required. Use tools like JSON validators to help identify structural issues.
  Example of correct JSON:
  {
      "name": "John Doe",
      "age": 30,
      "city": "New York"
  }
  
  
  Check Data Types: Ensure that all values in the JSON object that are expected to be strings are indeed strings. For example, if a property is supposed to be a string, make sure it is not an object or an array.
  
  
  Debugging: Use debugging tools or logs to inspect the JSON data being sent to the application. This can help identify which specific node is causing the issue.
  
  
  Review API Documentation: Refer to the API documentation for the specific UI5 application you are working with to understand the expected data structure and types.
  
  
  Error Handling: Implement error handling in your application to catch and log such errors, which can help in diagnosing issues in the future.
  
  
  Related Information:
  
  SAP UI5 Documentation: Review the official SAP UI5 documentation for guidelines on data binding and JSON structure.
  JSON Schema: Consider using JSON Schema to define the expected structure of your JSON data, which can help in validating the data before sending it to the application.
  Testing Tools: Use tools like Postman or Fiddler to test API calls and inspect the JSON payload being sent.
  
  By ensuring that the JSON data adheres to the expected structure and types, you can resolve the error and ensure smooth operation of your SAP UI5 application.