-
sw pt
- PowerServer
- Wednesday, 24 June 2026 01:23 AM UTC
Product: PowerServer 2025 R2 (PowerBuilder 2025)
I have a PowerBuilder Non-Visual Object (NVO):
$PBExportHeader$uo_test_api.sru
global type uo_test_api from nonvisualobject
end type
public function string of_hello (string as_name);
Return "Hello " + as_name + ", PowerServer Web API is working!"
end function
This NVO is used in my PowerBuilder application and works correctly after deployment to PowerServer runtime.
Goal:
I want to expose this method as a REST API so it can be called externally, for example:
POST /api/uo_test_api/of_hello
Body:
{
"as_name": "John"
}
Expected response:
"Hello John, PowerServer Web API is working!"
What I observed:
- After PowerServer deployment, Swagger does NOT show any endpoint for this NVO
- Only DataWindow / service-related APIs are visible
- I cannot find any direct REST endpoint mapping for this NVO method
Questions:
1. Is it possible in PowerServer 2025 R2 to directly expose a PowerBuilder NVO method as a REST API?
2. If direct exposure is not supported, what is the recommended way to expose this NVO business logic as REST API?
3. Does PowerServer automatically map NVO methods to REST endpoints when they are used in the application (window or entry point)?
4. If wrapping is required, what is the best practice architecture (service NVO, ServerAPIs controller, etc.)?
5. Is it required to manually translate PowerScript (NVO logic) into C# in order to expose it as a REST API in PowerServer 2025 R2?
What I tried:
- Called NVO from PowerBuilder window (works in runtime)
- Checked Swagger UI after deployment (no NVO endpoints appear)
- Reviewed ServerAPIs output (only generated service/datawindow APIs exist)
Any clarification on the correct architecture would be appreciated.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.