1. Gururaja Udupa
  2. PowerServer
  3. Friday, 12 January 2024 14:23 PM UTC


We have a base datawinow control uo_dw where we override the SetTrasObject function to handle few additional
process before setting the transaction object for the control. This method accepts transcation object as input Parameter

As per the PowerServer help, if a transaction object is defined as an argument of a function,
PowerServer will get a different transaction name from PowerBuilder.

The provided solution was to Define the transaction object as an instance variable or global variable

Referance: https://docs.appeon.com/ps2022/TransactionName.html

In our case, we are connecting to multiple databases from different places and we set different transaction object based on the databases

Setting instance variable or global variable may not be the feasible solution for us.

Is there any other solution or workaround for this issue?

Thanks,

Gururaja Udupa

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 12 January 2024 16:05 PM UTC
  2. PowerServer
  3. # 1

Hi Gururaja ;

   For PowerServer, you will need (I think based on my terse understanding of your App) to have a unique Transaction object mapping for each DBMS / DB instance that your App is using and map these via different DB Cache setting in PS. For example:

HTH

Regards ... Chris

Comment
  1. Gururaja Udupa
  2. Friday, 10 May 2024 05:50 AM UTC
Changed our workflow/code logic to resolve the issue.



Thanks,

Gururaja Udupa
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 10 May 2024 13:56 PM UTC
Thank you for the update & great news that the workflow change resolved your issue! :-)
  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.