1. Shawn Davis
  2. PowerServer
  3. Friday, 2 September 2022 15:24 PM UTC

Sorry if this is a dumb question. I've been away from PB coding for a couple years now and trying to get back up to speed, especially on the new PowerServer functionality.

When I deploy PS for an app does that also essentially give me a web api that I can use elsewhere? Like to use with a MS Office javascript add-in?

Or do I need to create another one as a separate step?




Accepted Answer
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 May 2023 16:52 PM UTC
  2. PowerServer
  3. # Permalink
Adding to what Francisco said, you can maintain a single set of DataWindows for both your PowerServer project and Web API project. So you develop your PB project as usual, compile with PowerServer (so the entire app is Internet accessible), and then use SnapDevelop to generate the standalone Web API for integration purpose (such as MS Office example you gave).
There are no comments made yet.
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 September 2022 15:34 PM UTC
  2. PowerServer
  3. # 1

Hi Shawn,

Unfortunately, the Web APIs generated on a PowerServer deployment are not mean to be used this way. Thus, their interface specification is not publicly available. You could definitely try and inspect the calls to the Web API to try to forge your own interface, but since this is not supported, breaking changes could be introduced without warning.

If what you want is access the DataWindow objects on your app from different locations you can migrate these DataWindows to C# with SnapDevelop and quickly scaffold a Web API so that you can access those APIs from whichever client you wish.

Hope this information helps


There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.