cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Build Apps - Rest API config display issue

smckenna
Explorer
226

Hi, im just interested to know if this is a broader issue.  I noticed that i cannot click on any of the Rest API integrations and see their configuration. The firebase and OData ones work.  However my older REST API direct integration ones no longer allow me to click on them to update the configuration.   I noticed that there is a new format called "Universal REST API integration" which seems to work.   If i need to migrate my APIs to the new version - i cant set my configuration unfortunately.  Appreciate any help.

@Dan_Wroblewski  - wondering if the older API format is being depricated.

Old

smckenna_0-1747205890826.png

New

smckenna_1-1747205989168.png

 

 

 

 

View Entire Topic
Dan_Wroblewski
Developer Advocate
Developer Advocate

I am told it is a regression that will be fixed in an upcoming release (no promises, of course)

smckenna
Explorer
0 Kudos
Thanks Dan, appreciate the follow up. Yes thats the issue, I cannot open or modify, it seems like a wise move to not clone and re-build with the new universal versions moving forward. I use NGROK to access local server functionality while testing and therefore often update the URLs on old APIs.
Josephrezende
Explorer
0 Kudos

Hello Dan,

I know this issue is recent and the team cannot promise resolve this but when the old REST was working I configure relative paths to accommodate multiple endpoint of the same database, e.g.: my.api/communication/all and my.api/communication/user, both endpoint retrieve a list of record and I set the relative path like this: my.api/communication/{path} to set the path when making the API call.
But since the old API stop working this issue also crashses when building the application because os the same relative path, the error below is from a error log I got after trying build to web:

...
Error: Command failed with exit code 1: node --max-old-space-size=12000 /app/current/node_modules/next/dist/bin/next build
⚠ Invalid next.config.js options detected:
⚠ Invalid input at "env.supportRelativePaths"
⚠ Expected string, received boolean at "env.supportRelativePaths"
⚠ Expected undefined, received boolean at "env.supportRelativePaths"

How can I proceed? 

smckenna
Explorer
0 Kudos
Thanks Dan, I can now get back into the legacy REST configuration, looks like a fix was applied. Cheers Steve