I'm working with a migration over to PowerServer 2022 R3. The previous version they were running in was PB 2017 R3.
This datawindow in question was working just fine in the old version of PowerServer.
This datawindow has two visible columns. One column is a code column. Column name is option_code. The second column is that same option_code column that is used to place a drop down datawindow in. That dddw shows a value based on what that code is.
When we run the application in PB Classic, it works just fine.
However, when we run it in PowerServer, nothing retrieves.
We are successfully setting the transaction object. However, it just returns zero rows.
I'm wondering if something might be causing an issue with the use of a column more than once.
Or if the name of the column in the dddw matching the column name in the main datawindow could cause a problem.
Any thoughts would be appreciated.
So now I have some additional info. We threw the datawindow that used a dddw away and built a new datawindow that did a join to the secondary table. So now the datawindow is just two columns coming from two separate tables. There are no column names that match.
The retrieve on the PowerServer side still brings back zero rows. We even added a command button that sets the transaction object again against the datawindow and fires the retrieve. (In case it was a timing issue on the construction of the window).
This datawindow just won't retrieve in the new environment.
The name of the datawindow control is dw_standard. The datawindow object name is d_purchase_body_selection.
Now my next thought is, are we possibly dealing with a keyword that is stepping on something over on the C# side of things.
Any thoughts would be appreciated. I'm even considering just renaming the dw control to see if that might clear this up.