Hi Stimulsoft team.
I found that in the .Net Core version, there is a problem with the ViewDataForm (the button in the upper right corner of the control). The Form can be popped up, but there is no data, but there is no problem with the function in the .Net version.
After checking the source code, I found that the classes in the Stimulsoft.Report.Web\Viewer directory in the .NetCore version are not referenced in the project. Can you handle it?
The version I use is Stimulsoft Dashboard Web NetCore 2020.5.2
NetCore ViewDataForm
-
- Posts: 6245
- Joined: Tue Mar 20, 2018 5:34 am
Re: NetCore ViewDataForm
Hello,
We need some additional time to investigate the issue, we will let you know about the result.
Thank you.
We need some additional time to investigate the issue, we will let you know about the result.
Thank you.
Re: NetCore ViewDataForm
Hello,
Sorry, maybe we did not exactly understand your question. Could you explain your issue in more detail?
Please send us a sample project that reproduces the issue for analysis.
Thank you.
Sorry, maybe we did not exactly understand your question. Could you explain your issue in more detail?
Please send us a sample project that reproduces the issue for analysis.
Thank you.
Re: NetCore ViewDataForm
As shown in the figure, in the .net core project, the ViewDataForm does not display data and the script is wrong, but there is no problem in the .net project. I purchased the source code version. In the Stimulsoft.Report.Web\Viewer directory, the references on both sides are inconsistent Caused the problem, the .net project cited several scripts
- Attachments
-
- 20210106111724.png (9.57 KiB) Viewed 3172 times
-
- 20210106111800.png (9.47 KiB) Viewed 3172 times
-
- 20210106101855.png (17.76 KiB) Viewed 3172 times
-
- 20210106102224.png (37.51 KiB) Viewed 3172 times
-
- 20210106103335.png (25.74 KiB) Viewed 3172 times
-
- Posts: 6245
- Joined: Tue Mar 20, 2018 5:34 am
Re: NetCore ViewDataForm
Hello,
The issue is fixed. The fix will be available in the next release build 2021.1 on the next week.
Thank you.
The issue is fixed. The fix will be available in the next release build 2021.1 on the next week.
Thank you.