Hi, I've encountered the problem that Infragistics's controls break CR (crystal report) reports.
When the control (WebDataTree) is present on the page, the CrystalReportViewer doesn't build the report.
After two hours of investigation I can provide some details and I hope somebody will explain why it happens and how we can solve or workaround this problem.
CR(Crystal Reports) renders script inside div that build the report (dynamically creates html).
The piece of page related to CR without WebDataTree on the page looks as following:
div id="ctl00_Content_reportViewer" script type="text/javascript"
script type="text/javascript" <!-- bobj.crv.writeWidget( ...
But when WebDataTree is present on the page it looks as following: div id="ctl00_Content_reportViewer"
That explains why the report is not built (because script is not even launched)
The question is why Infragistics's controls do this needless work? optimization by removing line carriages?
Please comment?
Hello AlexanderZh,
I'll be looking into this issue and find out why this is occurring. I will be able to give you a little more information by the end of Wednesday.
Hi, Michael!
Michael, are there any information on my problem?
Alexander
Konstantin,
Was this fix put into an SR? We are using 2011.1 SR 2238. We have the exact same problem. At this time, I'm having to revert back to the UltraWebMenu from the WebDataMenu to have Crystal Reports working.
Hi Alexander,
We've located the source of this issue. The fix for it would be available in the next service release. We appologize for the delay.
Hello Alexander,
I apologize for the delay in updating you on this.
I have created a support case for you with an ID of CAS-82442-N34793. The matter has been determined to be a development issue and has been logged in our tracking system with ID: 103718.
I will leave this case open and update you with any new information. You can view the status of the development issue connected to this case by going to the “My IG” tab on our website, hovering on the "My Support Activity" dropdown and selecting the "Development Issues" tab.
Please let me know if you have any questions.
Your sample works correctly with our latest internal builds. I've submitted a Development Issue to log this and to keep you updated. I will be able to give you another update sometime tomorrow.
If you have any questions or concerns, please let me know.
Thank you for the sample. I was able to reproduce the issue with this, although I'm not really sure why this is occurring. I'll forward the sample to Konstantin so he may look into it.
If you have any further questions, please let me know.