This question is locked. New answers and comments are not allowed.
I am using Visual Studio 2008 with the latest release version of OpenAccess. The ASP.NET OpenAccessDataSource control is not persisting certain changes I make to a WhereParameter after running the wizard. To repeat, do the following:
1. Run the OpenAccessDataSource "Configure Data Source" wizard. At the filter screen, add a filter (mine is Integer-based). Set its default value to "0" and its source to "None." Click "Finish."
2. Make sure the OpenAccessDataSource is selected. In the "Object Inspector," click the ellipse button that appears when the "Where" property is highlighted. Change the source of the parameter created in step one to "Session." Give it a session key value. In my case, the session key is "company_id." Click "OK" to save the change.
3. In the designer, close the Page and reopen it. Once again, click the ellipse button that appears when the "Where" property of the OpenAccessDataSource is selected. Notice that the changes from step 2 were not persisted.
1. Run the OpenAccessDataSource "Configure Data Source" wizard. At the filter screen, add a filter (mine is Integer-based). Set its default value to "0" and its source to "None." Click "Finish."
2. Make sure the OpenAccessDataSource is selected. In the "Object Inspector," click the ellipse button that appears when the "Where" property is highlighted. Change the source of the parameter created in step one to "Session." Give it a session key value. In my case, the session key is "company_id." Click "OK" to save the change.
3. In the designer, close the Page and reopen it. Once again, click the ellipse button that appears when the "Where" property of the OpenAccessDataSource is selected. Notice that the changes from step 2 were not persisted.
5 Answers, 1 is accepted
0
Hello Brandon,
Serge
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
This indeed is unexpected behavior and will be further investigated. It is a problem in the design time of the OpenAccessDataSource and I am creating an entry for it in our internal issue tracker. I will notify you in this thread once the issue is resolved.
Please find your Telerik Point updated.
Best wishes,Serge
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Peter Huisman
Top achievements
Rank 2
Rank 2
answered on 21 Dec 2010, 02:50 PM
As the OP had not received notification from you in this thread: is this issue still open, or is it resolved?
0
Hi Peter,
The issue is still open. The priority of the fix for the OpenAccessDataSource design time issue seems to have been lowered as you can always specify the settings for the session parameter in the .aspx file where the definition of the OpenAccessDataSource is.
Still, this is no excuse for keeping the issue open. We will try to address it as soon as we can.
Regards,
Petko_I
the Telerik team
The issue is still open. The priority of the fix for the OpenAccessDataSource design time issue seems to have been lowered as you can always specify the settings for the session parameter in the .aspx file where the definition of the OpenAccessDataSource is.
<telerik:OpenAccessDataSource ID="OpenAccessDataSource1" runat="server" ObjectContextProvider="SilverlightOpenAccessIntegration.SofiaCarRentalDbContext, SilverlightOpenAccessIntegration" TypeName="SilverlightOpenAccessIntegration.Car" Where="CarYear == @CarYear"> <WhereParameters> <asp:SessionParameter DefaultValue="2010" Name="CarYear" SessionField="car_year" /> </WhereParameters> </telerik:OpenAccessDataSource>Still, this is no excuse for keeping the issue open. We will try to address it as soon as we can.
Regards,
Petko_I
the Telerik team
0
Peter Huisman
Top achievements
Rank 2
Rank 2
answered on 03 Jan 2011, 02:34 PM
In general, this is a problem that plagues many Telerik controls. The design-time wizard sometimes just doesn't update the .aspx code (this also goed for other RadControls).
0
Hello Peter Huisman,
We highly appreciate any feedback you may give us and any issues you detect during your development with our products will be taken into consideration. We are open to any suggestions for improvement you may pose. We are making a lot of updates with every distribution we release and be sure that most of the customers' requests are handled in a timely manner.
Feel free to express your opinion and contact us back, should you need any assistance.
Regards,
Petko_I
the Telerik team
We highly appreciate any feedback you may give us and any issues you detect during your development with our products will be taken into consideration. We are open to any suggestions for improvement you may pose. We are making a lot of updates with every distribution we release and be sure that most of the customers' requests are handled in a timely manner.
Feel free to express your opinion and contact us back, should you need any assistance.
Regards,
Petko_I
the Telerik team