Adding to what Roland said, you can setup REST services that pass JSON back and forth using the ImportJSON and ExportJSON  methods, similar to how EA Server did it back in the day with GetFullState and SetFullState blobs.  The JSON can contain all of the state info or can be just plain JSON.  It's also nice using JSON if you ever end up replacing the PB client, your service layer can stay basically the same (minus passing state in the JSON)

For the READ operation, your service will do a retrieve, then ds.ExportJSON and return the JSON

CREATE and UPDATE operations will take JSON from the client and use ds.ImportJSON, then ds.Update() (Note: the JSON will contain the state info so the ds will know if it needs to do inserts or update.

DELETE is easy, just take a key id value and do a Delete with SQL in your service.

KR

Yes, something simpler, with no changes in the way we used to update the dw, would have been better.

Say

sqlca.dbms = 'REST ...'
sqlca.URL = 'x123.com'   or 
sqlca.dbparm = 'x123.com'   [  somewhere inside dbparm ]

and no changes in the dw_1.update() statement.  

Happiness Always
BKR Sivaprakash

REST is more of a design philosophy than anything technical. In practical terms it is using HTTP to transmit JSON formatted text between a client and server.

PB 2017 helped by adding JSON import/export to the DataWindow/DataStore and by adding the HTTPClient object.

Hi, Sorry, the webinar was not meant to be an in-depth or complete tutorial.  There is only so much that can be covered in short time.  Anyway, what you are outlining is not a problem, but of course you need to make changes to the existing code on the client.

Basically, you would move the embedded SQL and related logic from the client into your new C# Web API.  We provide a SQLExecutor object to execute the SQL in C# using the DataContext (equivalent to transaction object in PowerScript).  With the SQLExecutor, only minor changes required to the syntax of your embedded SQL.