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

Resolved Not able to edit object from the UFA(unsupported feature analysis) report

  1. Issue
0
Votes
Undo
  1. Team BFMS
    Team BFMS
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 27 March 2019 17:53 PM UTC

Hi, 

 

I migrated the current application to web and performed unsupported feature analysis. Since some part of code can be ignored as they are unsupported, I am trying to open the object by right clicking(refer screenshots)  on the objects in the summary of the UFA report itself. It opens up a new session with that object open in the power-builder but not able to connect to the database base. But if i open a new session in the power builder i was able to connect to database. Is there anything that i need to enable in order to make it work?

Please check the screenshots that i attached.

Attachments (1)
Refer_images.rar
Apache (httpd) Reverse Proxy configured to PowerSe...
NVO variables visibility in WEB apps.
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 27 March 2019 19:02 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi;

  When opening up the PB IDE from an external link (like the UFA report), the IDE will normally try and connect to the last DB Data Source that was active via the DB Profile you last used.

  I just tried the UFA under PB2017R3 MR01 (build 1880) and the open of the related object class worked properly.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Team BFMS
Team BFMS Accepted Answer Pending Moderation
  1. Wednesday, 27 March 2019 19:28 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Chris,

When i converted to web i happened to see the path of the code pointed to somewhere else UnsupportedTool(C:\Program Files (x86)\Appeon\PowerServer 2017 R3\Toolkit)(please refer screenshot web_migr.jpg). Is that a good sign? I was able to connect to this through power-builder IDE even though the path is changed. But as per your explanation it has to connect to the last Data Source that was active via DB profile that we last created. It is still not working through UFA.

 

Thankyou,

Naveen

Attachments (1)
web_migr.JPG web_migr.JPG
Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 27 March 2019 19:44 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Yes ... opening an object from the UFA looks weird as the PB IDE source seems to be coming from the "PS Toolkit's" location and not from the original "WorkSpace's" location that you would expect. However, if you open an object from the UFA, modify it (for example add a simple comment) and then save ... when you re-open the original App's "WorkSpace" in the PB IDE and look at the object that you just modified via the UFA, you will see that the proper object was modified in the primary WorkSpace's location.

I know ... looks weird!

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 27 March 2019 20:47 PM UTC
What version & build of PB are you using?

FWIW: I tested this on W10
  1. Helpful
Team BFMS
  1. Team BFMS
  2. Thursday, 28 March 2019 12:28 PM UTC
It is Appeon Powerbuilder 2017 R3 Build 1880.

Operating System Windows 10
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 28 March 2019 14:18 PM UTC
Weird ... No DB Connection issues in my environment (same as yours) in the PB IDE launched from UFA.
  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.