Bug 6163

Select Error: The model does not have a property that can map to column: ecn_code 06 May, 2021

Zhang JX
26 February, 2021
Product: PowerBuilder Category: DataWindow
Version: 2021 Beta Build: 1076
Classification: Appeon bug Publishing: Public
Priority: P3
Status: Closed Reason: FIXED
Kai Zhao @Appeon 29 April, 2021
#18
Hi Zhang,

Glad to hear that. I will close this ticket! If you have any further question please open a new ticket.

Regards,
ZhaoKai
Zhang JX 29 April, 2021
#17
(In reply to Kai Zhao @Appeon from comment #16)
Hi Zhang,

Good news that PowerServer 2021 beta (build 1150) is available for download.
The issue you reported has been fixed in this release. Please download and
install it to verify the issue you reported and let us know if any problems.
You can get the installer from our Downloads portal at
https://account.appeon.com/download (login required). 

If you are a PowerBuilder CloudPro user, the PowerServer 2021 beta license
is automatically added to your account, and you should have received an
email today notifying you. If you do not have a PowerBuilder CloudPro
license yet, you can apply for a trial after clicking the ‘Download the
Beta’ button on https://www.appeon.com/products/powerserver.
We welcome all feedback from you!

Regards,
ZhaoKai
Hi Zhaokai, Yes, I have deployed my application and confirm that this issue be solved in this Beta release. Thank you . JX
Kai Zhao @Appeon 29 April, 2021
#16
Hi Zhang,

Good news that PowerServer 2021 beta (build 1150) is available for download. The issue you reported has been fixed in this release. Please download and install it to verify the issue you reported and let us know if any problems. You can get the installer from our Downloads portal at https://account.appeon.com/download (login required). 

If you are a PowerBuilder CloudPro user, the PowerServer 2021 beta license is automatically added to your account, and you should have received an email today notifying you. If you do not have a PowerBuilder CloudPro license yet, you can apply for a trial after clicking the ‘Download the Beta’ button on https://www.appeon.com/products/powerserver.
We welcome all feedback from you!

Regards,
ZhaoKai
Kai Zhao @Appeon 04 March, 2021
#15
Hi Zhang,

Thanks for your further analysis. This is a known issue, and we are working on it. I can reproduce the issue with datawindow sql below and pass null to as_test. The work around is add ‘or  :as_test is null’ on our end.

SELECT test.id,   
         test.txt,   
         test.c_desc,   
         test.c_desc2  
    FROM test   
where left(c_desc,len(:as_test)) = :as_test

Regards,
Zhaokai
Zhang JX 02 March, 2021
#14
(In reply to Zhao Kai @Appeon from comment #12)
Hi Zhang,

You are welcome. We will fix both issues on GA version.

For the no data has been retrieved out issue, please make sure it is work
well on PB, if it is a PowerServer only issue, please open new ticket and
please provide a simple PB case to reproduce it to us for more study, thanks.

Regards,
ZhaoKai
Hi Zhaokai, No data issue solved. Problem with DWO where clauses '' vs null. added below [or :as_ecn_code = '' ] to be a workaround. understood such issue happened to webapplication, while we are using it for universal searching widely within existing application, please advise whether there is a better option or not to address this concern. Thank you. WHERE (dms_ecn_list.coy_code = :as_coy_code ) AND (dms_ecn_list.ecn_coy = :as_ecn_coy) AND ( left(dms_ecn_list.ecn_code , len(:as_ecn_code)) = :as_ecn_code or :as_ecn_code = '' ) AND ( dms_ecn_list.requestor_date >= :adt_date_from ) AND ( dms_ecn_list.requestor_date <= :adt_date_to ) AND ( left(dms_ecn_list.cust_code , len(:as_cust_code)) = :as_cust_code or :as_cust_code = '' ) AND ( left(dms_ecn_list.requestor_code , len(:as_requestor)) = :as_requestor or :as_requestor = '' ) AND ( dcs is null or dcs = '')
Zhang JX 02 March, 2021
#13
(In reply to Zhao Kai @Appeon from comment #12)
Hi Zhang,

You are welcome. We will fix both issues on GA version.

For the no data has been retrieved out issue, please make sure it is work
well on PB, if it is a PowerServer only issue, please open new ticket and
please provide a simple PB case to reproduce it to us for more study, thanks.

Regards,
ZhaoKai
Hi Zhaokai, yes, there is data being retrieved out when running from PB client/server accessing. ok, I will create a simple PB application and open a support case later. Thank you. JX
Kai Zhao @Appeon 02 March, 2021
#12
Hi Zhang,

You are welcome. We will fix both issues on GA version.

For the no data has been retrieved out issue, please make sure it is work well on PB, if it is a PowerServer only issue, please open new ticket and please provide a simple PB case to reproduce it to us for more study, thanks.

Regards,
ZhaoKai
Zhang JX 01 March, 2021
#11
PowerServer2021 Testing Issue5.pdf (71KB)

(In reply to Zhao Kai @Appeon from comment #10)
Hi Zhang,

Please go to PowerServer project > General tab to set the rebuild option to
'Full' to see if it is work well.

If this way still doesn't help, let's schedule a remote session to debug it.
We would recommend you to make the remote session during our working time
which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get the immediate help
from the other team if necessary. Regarding the tool to make the remote
session, we usually use GTM or TeamViewer, and TeamViewer is preferred
because its response is more quicker than GTM during the session, but we can
use the other tools that you think is better. Anyway, please let us know
when you can make the session and which tool you'd like to use for this
session.

Regards,
ZhaoKai
Thanks Zhaokai for the remote session supporting. 2 issues addressed during this remote session: 1. Error message: "The model does not have a property that can map to column" ==> identified issue with the "quote" when DWO using select column as 'column_name'. ==> by removing the "quote", no more error showed, however, no data has been retrieved out. ==> we shall wait for Appeon to solve this issue on GA release 2. Error message: "Timeout...." when retrieving data more than 30 seconds ==> add the "CommandTimeout:" 300 to connection-cache, no more such issue when retrieving time < 1 minute ==> got another error message "Get response http version failed" when retrieving time > 1 minute ==> we shall wait for APPEON to solve this issue on GA release Thank you. JX
Kai Zhao @Appeon 01 March, 2021
#10
Hi Zhang,

Please go to PowerServer project > General tab to set the rebuild option to 'Full' to see if it is work well.

If this way still doesn't help, let's schedule a remote session to debug it. We would recommend you to make the remote session during our working time which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get the immediate help from the other team if necessary. Regarding the tool to make the remote session, we usually use GTM or TeamViewer, and TeamViewer is preferred because its response is more quicker than GTM during the session, but we can use the other tools that you think is better. Anyway, please let us know when you can make the session and which tool you'd like to use for this session.

Regards,
ZhaoKai
Zhang JX 01 March, 2021
#9
(In reply to Zhao Kai @Appeon from comment #8)
Hi Zhang,

Thanks for reporting this problem! We reproduced it on our end and will do
further research to figure it out. We will keep you posted about the
progress. 

The quotas in datawindow SQL cause the issue, please temporary work around
the issue by removing them, for example:

select ecn_code as ecn_code 
......


Regards,
ZhaoKai
Hi Zhaokai, I have tried to remove the quotes(apostrophe), still got the same error. Thank you. Best Regards, JX
Kai Zhao @Appeon 01 March, 2021
#8
Hi Zhang,

Thanks for reporting this problem! We reproduced it on our end and will do further research to figure it out. We will keep you posted about the progress. 

The quotas in datawindow SQL cause the issue, please temporary work around the issue by removing them, for example:

select ecn_code as ecn_code 
......


Regards,
ZhaoKai
Zhang JX 26 February, 2021
#7
(In reply to Chris Pollach @Appeon from comment #6)
Hi Zhang;

  Interesting that you are using the PFC "Linkage Service"!

  I will now transfer this ticket over to the main Support / Engineering
team for their review & feedback on whether it might be a PFC issue.

Regards ... Chris
Hi Chris, Noted with thanks. We are using Pfc as the fundamental of our in-house ERP system development, and no such issue happen to most of modules(Sales/purchase order, accounting/production etc...). We have solved “build&deploy” error and incurred this error during testing stage... might report more case for the time being... Regards JX
Chris Pollach @Appeon 26 February, 2021
#6
Hi Zhang;

  Interesting that you are using the PFC "Linkage Service"!

  I will now transfer this ticket over to the main Support / Engineering team for their review & feedback on whether it might be a PFC issue.

Regards ... Chris
Zhang JX 26 February, 2021
#5
(In reply to Chris Pollach @Appeon from comment #2)
Hi Zhang;

  Is this error coming from SNAP vs PB or, is this an error on the
PowerServer "deployment" from PB to Snap (aka C#)?

Regards ... Chris
Hi Chris, This is an runtime error on the powerserver “deployment” from PB to Snapdev(aka c#). Thanks JX
Zhang JX 26 February, 2021
#4
to add on, It is a runtime error when running the deployed application, no such issue if running it from client-server environment.

JX
Zhang JX 26 February, 2021
#3
(In reply to Chris Pollach @Appeon from comment #2)
Hi Zhang;

  Is this error coming from SNAP vs PB or, is this an error on the
PowerServer "deployment" from PB to Snap (aka C#)?

Regards ... Chris
Hi Chris, No error during deployment process, but hit the error when running the application where retrieving a DWO - FYI, we are using Pfc linkage service on this window object. Thanks Best Regards JX
Chris Pollach @Appeon 26 February, 2021
#2
Hi Zhang;

  Is this error coming from SNAP vs PB or, is this an error on the PowerServer "deployment" from PB to Snap (aka C#)?

Regards ... Chris
Zhang JX 26 February, 2021
#1
PowerServer2021 Testing Issue4.pdf (137KB)

*Phenomenon:
Got error message: The model does not have a property that can map to column when retrieving data with DWO

*Reproduce Steps:
Refer to figure2 in the attachment, the DWO is using select column as 'xxxx' instead of normal select statement.

Remarks:
OS:
All
Platform:
All
Database Type:
Microsoft SQL Server
Database Version:
Azure SQL