on 2023 Nov 16 9:04 AM
I have 2 actions for my S/4HANA sales orders, both on the same tenant using the same destination.

The pre-existing action -- meaning before the new action interface in the lobby -- works when I test it.

But I get a schema mismatch issue with the one I just created now, using the same API and parameters.

For example, for TotalNetAmount it is expecting a number:

But in the API it is returned as string, and apparently cannot be converted.

In the old action, the schema for totalNetAmount is a string, and therefore works OK.
Why is that and what can I do?
Request clarification before answering.
I'm actually experiencing the same with BAPI's. Some fields expect a number, but a string is given .. In this case it was the "ROW" in the return table that was causing a lot of problems in the generated type for the return table.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daniel,
While this issue is being checked by the development team, you can use the below workaround.
Delete the problem causing field eg TotalNetAmount of type number and add back a same named field with the right type of String.
Steps:
1. In Output tab, select the problematic field ( TotalNetAmount ) and click on Remove
2. Click on Add. Before adding back a new field, permanently delete TotalNetAmount from the Available fields list
3. Under Add, under new field add field TotalNetAmount of type String under the node of d/results



Regards,
Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks ... if I have only 1 or 2 such fields, than OK, but I'm worried this will be true of every number field, and you know there are hundreds of potential fields.
Anyway, I will do the workaround for my limited number of fields, but I'll keep the question open -- please update when there is a response from dev.
| User | Count |
|---|---|
| 10 | |
| 7 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.