Steps to reproduce:
- Create a stored procedure with the following definition:
SQLCREATE PROCEDURE usp_reportDebug
@parameter1 AS INT,
@parameter2 AS DATE
AS
BEGIN
- Use the Reporting Demo Application to bind to it.
SqlDataSource - It is not possible to convert parameter value from DateOnly to DateTime
created a month ago
(modified a month ago)
Answers approved by DevExpress Support
We have addressed the issue described in this ticket and will include a fix in our next maintenance update. Should you need to apply our fix prior to official release, you can request a hotfix here.
Important Notes:
- Hotfixes may be unavailable for Early Access/Beta builds or updates set for release within a week.
- .NET only: in the NuGet Package Manager, use your personal NuGet feed and check the "Include prerelease" option to view the hotfix package in the "Updates" tab.
- v24.2.5Download Official Update
Comments
(2)
Hi, I too have this issue while trying to update a stored procedure name in my report.
No i am unable to use my report.
When do you expect this to be resolved?
Rombaut,
This will be resolved in the upcoming update for v24.2 which is already in the pre-release phase, but the complexity of some fixes we applied requires thorough testing. As always, we strive to ensure our products meet the highest standards, and we will publish the build once it passes all tests and security scans.
Note: the new release will be v24.2.5, as we decided to cancel v24.2.4.
The .net framework and .net core are the standard. They will exist without DevExpress.
DevExpress is auxiliary - you need to make your software work with the standards provided.
The attitude expressed "this is a .net framework issue" is very poor.
It behooves DevExpress to address the issue.
This and other recent attitudes and issues belie a company that will fail.
@matthew,
It looks like there is some misunderstanding. What you see is simply a piece of additional information, stating that the given bug is only reproduced with the old runtime. This is just a clue to our R&D team as well as to those who may stumble upon the same (or similar) issue. However, considering that some may migrate to the new runtime, as well keep create predefined reports in Visual Studio Report Designer (which still targets the full .NET framework internally), we agree that this note can be found confusing and therefore should be removed.
To avoid any misunderstanding: the fix for the above is coming. We'll reply there once it's there. You'll also receive an automatic e-mail notification on any status changes.
Note that you're welcome to share additional details about your particular case, such as the database engine you use, the affected report layout, and the error you encounter when running it. We'll be happy double-check everything and confirm whether it matches the case being discussed here.