PB.NET - DW initial column values are lost!

[former_member329524]

Hello, al

I have just discovered this issue, doesanyone have a remedy?

I have a DW with a large number of columns (>30). Some of them have initial values set up.

When I change the select statement, I receive a message "Select change has forced update specification change" and then all initial values are lost.

I can see it in the painter itself - they just disappear.

Does anyone know what to do with it?
I am working with the latest build - 5629

Thank you

Arcady

[CobyKako]

Hello Arcady,

New Change Request 766642 has been created to report this defect with the .NET IDE

(I confirm it works with the Classic environment !!!)

I'll also create a SAP KBA for that purpose shortly.

Please look at my reply on incident 651339 to determine if is really blocking your development.

Thanks

Jacob

[CobyKako]

Hi Arcady,

Quick update: SAP KBA 2036168 was just released:

http://service.sap.com/sap/support/notes/2036168

Thanks

Jacob

[former_member329524]

Actually, this also happens on a very small select as well.

This is getting urgent, any idea how to make it stop?

[Former Member]

Hi Arcady,

I'm seeing the same behavior in 12.5.2.5006.

One workaround I've found is to change the default value on the column in the db painter. The initial value is displayed on the validation tab of the column properties window in the db painter. The dw painter appears to be getting the initial values from pbcatalog tables whenever this happens.

Hth,

Mark

[former_member329524]

Hi, Mark

Thanks for your help, but it is unlikely that my developers will remember to change all default values for all fields in all tables in the DB painter.

And this is not really a solution, since the same column might have different initial values in different DW's.

Is there a way to severe the link altogether between the DW and the catalog tables (at least forthe initial values)?

[Former Member]

It's a workaround not a solution. There may be a flag you can set in the pb.ini to tell the dw painter to stop getting the default values from the catalog tables in the db but I don't know it.

Another option is to edit the sql of the dw in syntax mode instead of using the painter. The upside to that is you don't have to go back and reset the update properties of the dw.

[CobyKako]

Hello Arcady,

I'm afraid but could not reproduce your issue using a small DataWindow SELECT statement .

Firstly, I tested your scenario using the PowerBuilder Classic IDE by following these steps:

a) Create a Grid DataWindow whose SELECT statement is based on tables "department" and "employee" from default EAS Demo DB V125 database.

I've chosen dept_id, dept_name for department table and emp_id, emp_fname, emp_lname, state for employee table.

Please note that state column has a default intial value "A" at design time.

b) Save the DW and change its SELECT statement (menu Design > Data Source...) to add additional columns: street, city, state, zip, code.

You should see something like that

But intial value for state column remains unchanged and is not lost !!!

Then I tested same scenario in the .NET IDE:

c) Migrate existing PowerBuilder classic target to WPF

d) Repeat steps a) - b)

Oddly, I don't get a message like you mentionned: "Select change has forced update specification change"

and initial value is still there for state column.

Could you please retest the above and send me the instructions to recreate your behavior?

P.S.

I would say that if it used to work in the Classic environment, it should work the same way with the .NET IDE

I got your incident 651339 and will update it shortly with the above infos

Thanks

Jacob

[former_member329524]

Hi, Jacob

I followed your procedure and here are the results:

1. The initial value of the column needs to be set manually in the painter (in case of our application this is always the case, since we do not work with PB catalog tables). So, I set it to 'B' and it was lost after the select change.

2. I close and open the painter before changing the select statement (this way I simulate a change of DW after a long period after it's creation).

Here is the screenshot befroe the sql change

Now I add the 3rd field from the deparmtnet table. I got a warning message

And then the initial value was gone:

[CobyKako]

Hello Arcady,

Issue has been recreated on the PB .NET IDE.

This works with the Classic IDE, so I think you discovered a bug.

I'm going to create a Change Request and let you know of its number.

Regards

Jacob