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

Resolved Appeon workarounds PBL objects need their own workarounds for PowerServer?

  1. Advice
0
Votes
Undo
  1. Thomas George
    Thomas George
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 2 March 2020 20:52 PM UTC

Hi,

 

I'm trying to workaround a PowerBuilder/PowerServer migration issue, and I have a general question- Why is the code in the appeon_workarounds.pbl not compatible with PowerServer? For instance, I'm looking at the appeondatastore object, method of_getdatainfo(), and I see the code doing things Appeon doesn't support like use of GOTO's. 

I'm pretty sure the Unsupported Features Analysis tool flagged several other incompatibilities, too, in the various objects. I took my appeon_workarounds.pbl from the PowerBuilder 2019 R2 beta install of PowerServer.

This seems a bit ironic. Am I missing something?

 

Thanks,

Tom

 

Appeon Server 2016 Number of Digits?
Cannot run appeon debugger on Powerbuilder 2017
Who is viewing this page
German Hidalgo Palacios
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 March 2020 19:43 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Thomas;

   FYI: For Ticket #4210 and your test case, its working great for me ....

Note: Your test DWO was from PB 10.5. I edited its source code to state v 19 and then deployed it to PS.

         release 19;

Regards ... Chris

FWIW: I have been using External DWO's for ages with various PS versions without any issues.

 

Comment
Thomas George
  1. Thomas George
  2. Wednesday, 4 March 2020 17:44 PM UTC
Did you scroll to the right and look at the change_1, change_2, and change_3 columns? Because the columns that are visible in your .png looked the same in both for me, too.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 4 March 2020 18:32 PM UTC
Thanks Thomas ... Yes, it's only when you scroll way to the right that you see the column mismatch start to happen. Thanks for that tip! The related ticket is now over to Engineering.
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 March 2020 07:10 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Thomas,

The object appeondatatore is a built-in object of PowerServer and appeon_workarounds.pbl simply provide a interface for the users. And this object won’t be deployed when deploy application use Toolkit. There is no appeondatatore.js file existing, and there is no related record in the UFA report. Please use it directly in your application.
Anyway, since its PB script uses the script not supported by PowerServer declaration, I will forward it to the development team for consideration of modification. Thank you for your feedback.

And the script below is supported, which works well on our end. Please open a support ticket in the support portal and provide a test case for us. Many thanks in advance!
https://www.appeon.com/standardsupport/

ls_OptimizerChangeoverDisplayData = lds_changeover_list.Describe("datawindow.data")


Regards,
ZhaoKai

Comment
There are no comments made yet.
Thomas George
Thomas George Accepted Answer Pending Moderation
  1. Monday, 2 March 2020 21:15 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Chris,

 

I have a function that returns a reference string arg that contains the data in a datawindow in the format needed for ImportString(). It currently does:

ls_OptimizerChangeoverDisplayData = lds_changeover_list.Describe("datawindow.data")

which appears to not be supported by PowerServer, because it returns an empty string when there really is data. So I was thinking I could do a dw.SaveAs() and save as text, read the file back, then delete the file, and then I found the appeondatastore class's of_getDataInfo() was already doing this, but I couldn't use it as-is because of the GOTO's.

 

Tom

 

Comment
mike S
  1. mike S
  2. Monday, 2 March 2020 21:30 PM UTC
Describe("datawindow.data")

is supported. see datawindow object properties in the PS help



  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 2 March 2020 21:33 PM UTC
Hi Tom;

FYI: I have sent a query over to the longer term PS support guys to see what the actual story is about these old classes.

FWIW: I just use the plain old DC/DS.Describe("datawindow.data") in my frameworks. Does that not work in your app? If not .. does DS/DC.Object.DataWindow.Data work?

Regards ... Chris

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 2 March 2020 21:08 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi Thomas;

   Those objects (appeondatawindow, appeondatastore, etc) are from an old "Appeon For PB" (the old product name for PowerServer) release circa 2005.

   What feature(s) of those object classes is your application trying to still use them for vs a real DS / DC?

   FWIW:  These object classes even go back before I started with PS in 2008 and I have never had to use them.

Regards ... Chris

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 3 March 2020 14:34 PM UTC
Yes, a NULL row could throw your code into "never, never land". ;-)
  1. Helpful
Thomas George
  1. Thomas George
  2. Tuesday, 3 March 2020 16:30 PM UTC
OK, I see why I have no rows, and I think I found a bug in PowerServer. Unless you know of datawindow limitations with external datawindows. Here's what's happening: My filter is returning no rows because PowerServer appears to be getting confused with the data in my datawindow. If I save the datawindow to Excel just before filtering, in the PB IDE, my Excel fine looks fine, but in PowerServer, my Excel file has my data "shifted" several columns to the left, which is causing my filter to fail (return no rows).



When I say "shifted", I mean data set for some columns appears under different columns in the export. So I don't think the bug is in the saveAs(), but rather somehow internal to the datawindow in PowerServer, because I have the same problem with Filter() that I have with SaveAs().



In my specific case, my external datawindow has 263 columns. I made a small sample app I plan to submit as a bug test case in which I insert a row, set data for columns 2, 4, 5, 6, 134, 135, and 136. When I save it to Excel, my data for columns 134, 135, and 136 actually lives in columns 45, 46, and 47.



Should I submit the case?

Tom

  1. Helpful
Thomas George
  1. Thomas George
  2. Tuesday, 3 March 2020 18:03 PM UTC
I just submitted this as a bug, #4210.



https://www.appeon.com/standardsupport/track/view?id=4210

  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.