Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Issue with datastore updates in Web API

  1. Issue
0
Votes
Undo
  1. Miguel Alzate
    Miguel Alzate
  2. PowerServer
  3. Saturday, 29 July 2023 14:39 PM UTC

Greetings to the entire Appeon community!

I am having the following issue: When creating a datastore with a simple SQL (for example, SELECT * FROM tecno.employee) and performing UPDATEs on this datastore, in client/server it works correctly, but, with PowerServer, it tells me that the employee table does not exist; somehow, it is suppressing the tecno qualifier from the employee table in the Web API.

Any idea what could be causing this inconsistency?

I am using PowerBuilder and Runtime version 2022 Build 1900.

In advance, thank you very much for any collaboration received.

Power cleint Implementation Issue
AppConfig.json question
Accepted Answer
Miguel Alzate
Miguel Alzate Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2023 13:33 PM UTC
  2. PowerServer
  3. # Permalink

I resolved the issue by doing the following modify to the datastore after created:

ds_1.modify("datawindow.table.updatetable='"+<table_to_update>+"'")

with table_to_update properly qualified.

Hope this helps others.

Comment
There are no comments made yet.
Responses (3)
Jay Hastings
Jay Hastings Accepted Answer Pending Moderation
  1. Wednesday, 14 August 2024 16:41 PM UTC
  2. PowerServer
  3. # 1

I have something similar where my datastore updates running through the IDE but fails on the Web.  It gives no error.  I've run through the debugger and get the same....

if ids_customerproductdata.Update(TRUE, FALSE) <> 1 then

 

 

A database error has occurred.--


Object : n_busobj_customer

Database error code: -1

Database error message:


No changes made to database.

 

 

 

I had this once before and fixed it by recreating the datastore.  Now I have it on another one.  This is code migrated from a 20+ year old app.

Any ideas?

 

Thanks

Jay

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Saturday, 29 July 2023 15:46 PM UTC
  2. PowerServer
  3. # 2

Hi Miguel;

  The most likely cause of that is the DB mapping in the PS project where it's the wrong instance and / or the UserID specified does not have enough DB rights. Thus, no web API is built for that table & it fails at runtime.

Regards... Chris 

Comment
Load more comments
Miguel Alzate
  1. Miguel Alzate
  2. Sunday, 30 July 2023 01:57 AM UTC
In effect, the entity is properly qualified as "TECNO.EMPLOYEE" in the scheme and, in fact, the datastore was created with the SQL sentence "SELECT * FROM TECNO.EMPLOYEE". However, the UPDATE passed to the DB engine goes without the "TECNO" qualifier.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Sunday, 30 July 2023 02:07 AM UTC
Oh, oh - that sounds like a possible "bug"?
  1. Helpful
Miguel Alzate
  1. Miguel Alzate
  2. Monday, 23 October 2023 18:32 PM UTC
Maybe.
  1. Helpful
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.