I have just upgraded to v10 in our TEST environment, and notice that the Rankings panel is not updating the underlying table T_CUST_RANK correctly.
This is pretty bizarre behaviour - in v9 I can add a new ranking row and hit save and the values are saved in T_CUST_RANK, and by using SQL Profiler on the database I see that the line
INSERT INTO T_CUST_RANK ( customer_no, rank_type, rank ) VALUES ( 999, 1, 1500 )
is being run to directly update the table.
When I perform the exact same actions on the v10 environment, and the same line is observed through the SQL Profiler, but no update happens on the table.
More bizarrely, if I copy and paste the line out of SQL Profiler and run it from within a SSMS window, the table is updated correctly.
What makes this worse is that this is only happening for one rank_type in TR_RANK_TYPE - the other rank_types behave correctly.
Has anyone else observed any problem with the rankings table? The v10 upgrade script changed rank_type from int to smallint, but that was the only change in that area (that I could spot).
Any thoughts gratefully received.
That is strange behavior indeed. One thing to keep in mind when using SQL Profiler: the Errors/Warnings category of events is not included in the default trace profile, and have to be added manually. Perhaps another trace, with those events included if they weren't in your earlier ones, might display an error that would be helpful in determining the cause of this.
Thanks Steven for your reply.
I have re-run the trace with Errors & Warnings enabled, and there aren't any errors produced when saving the Ranking screen.