- Jeff Gibson
- PowerServer
- Tuesday, 27 August 2024 07:45 PM UTC
PowerBuilder 2022 R3 Build 3356
SQL Server 2022
We have an application that when a cloud project is being built in PowerServer, it in turn triggers stored procedures that start processes that are a part of the audit/logging process for their billing module.
The stored procedure that is being inadvertently fired is tied to a datawindow within their environment.
My question is this...
When a cloud project is being built and deployed (this is when this database action is getting inadvertently fired), and the Web-API's are being built out for the datawindows/stored procedures. Are the stored procedures being executed by the process, by design? We were under the impression the datawindow/stored procedure would be interrogated, not fired.
We can duplicate this, because the table that is having data placed in it, is empty when we start the build/deploy process.
Any thoughts on getting around this would be greatly 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.