Backend export Crystal Reports to PDF - visual-studio

I'm newbie to Crystal Reports and would like to know, which way to go.
My challenge:
A web-service consumer asks for a PDF on a specific report (name of RPT-file).
The called web-service shall generate report output as PDF and send it to the consumer.
The machine, where the service shall run, has an installed service "SAP Crystal Reports Server 2016".
Actually I'm using Visual Studio 2019 and "Crystal Reports for Visual Studio 13 SP27".
I'm thinking of an implementation in C#.
I tried lots of examples but none seems to be basis for my challenge.
Am I on the correct track?
Any hint is welcome...

Related

which reports service should I use?

I am working on Visual Studio 2010 , developing a windows app.
I want to create some simple reports. I am confused about which reports should I use in the application.
The reports which are available in the Visual Studio or the crystal reports.
what are the advantage of report over each other ?
I am working on reports after long time so, can I get some simple links, so I can understand workflow of it.
Crystal Reports seems well documented, more ressources available than Microsoft Reporting
Huge API in CR (just try to print a Microsoft Reporting-report without preview, that's ridiculous!)
Crystal Reports somehow slower than Microsoft Reporting with huge amount of data
Designing reports against custom BusinessObjects is really worse (Wizard isn't even able to "see" objects in another project!) in Crystal Reports
Crystal Reports's preview integration into our apps is much better than in Microsoft Reporting (just try to make your own toolbar!)
Microsoft Reporting's integration in the dev environment is superior to CR (which's habit to implement it's own DB-connection is bad taste)
Both seem to lack designers, our users can use at runtime from within our apps (not external!) to manipulate reports which we prefer to store in the DB (seems to be quite easy with Microsoft Reporting as it's only XML to be stored!) for better managability and deployment.

Visual Studio 2005 Reports and Windows 7

We have recently upgraded to windows 7 and have noticed that there are compatibility issues with my previous version of MS visual Studio 2005.
From taking a look around the web I believe that this issue is due to SP1 for Windows 7. My organisation will not get rid of SP1 just for one or two developers so I need to figure out a work around.
This is the issue...
I have an old MS visual studio website that has a report located on the home. This report was created in MS VS 2005.
Other versions of Visual Studio in have are 2010 and 2012. I have tried to convert the 2005 report into 2010 and this does state that it has been converted but I still cant open or do anything with the report. My 2005 web site is too large to convert or move into 2010 and we can still maintain this 2005 site by opening this up in 2010. It just seems to be a problem with the 2005 report.
I'm running out of options to make a simple change to a report. Anyone else got any ideas? I have even tried to create this report in 2010 and then add this to my 2005 site but this doesn't work.
Regards
Betty.
You say a report and then say that it is a whole site? Why not run a second site in tandom? Make a whole new site and name it differently like
http:// (servername)/Reports2012
Then put reports there. You cannot open a converted report in a site that is for a prior version, you can view it in Microsoft Business Intelligence Studio, BIDS, which is an add on to Visual Studio. If you can upgrade but cannot view it there, there is something wrong with the language file potentially. I would then make a copy of it in the old 2005 BIDS, then take that copy and see if you can upgrade that and if it will work. If that STILL does not work you could make a test report in BIDS 2010(SQL 2012 works on VS 2010, yes weird but true) to assure you can create reports there. Many times people try to open SQL Server 2012 Reports on VS 2012 and it won't work. You need 2010 add on you can find it under All Programs>MS SQL Server 2012>SQL Server Data Tools(They made the naming very confusing as it opens up and display BIDS, but calls itself 'Data Tools' under the programs). Every other version of SSRS lines up with that year of SQL Server to that year of VS. Not 2012.
If the report upgrade still does not work, yet you can create a run a new report fine; I would suggest potentially opening up the file dircectly. Your projects in a Reports solution generally have a file '(something).rdl' that RDL is the actual file and is just XML markup of the language. This is a last resort as you are essentially trying to do manually what the upgrade is failing to do in the xml. You merely copy a working report, and then paste the parts of the old report into their correct sections. Ensure the XML is valid as well.
If you cannot manage that to work you will need to recreate the report from scratch.

Crystal Reports Viewer 2011 crash

We are developing an application which generates reports in .rpt format. When we open the various types of report using Crystal Report Viewer 2011 all of them work fine except for one, which causes Crystal Report Viewer to crash ( - [Internal Error DataViewL573] ).
The application is built with Visual Studio 2005. The reports are generated with the Crystal Decisions plugin.
I have two reports; One that loads fine in the Viewer (GOOD.rpt), and one that causes it to crash (BAD.rpt).
Does anyone know of any quick avenues of investigation outside of taking apart the report construction process itself? Are there any known issues with the viewer that I should be aware of?
Cheers,
Lordmonkey.
It is probably a "corrupted" report. Not all Crystal runtime engines are created equal.
See this KB article:
http://www.jeff-net.com/support/index.php?/Knowledgebase/Article/View/16/0/my-crystal-report-will-not-run-whats-the-problem

What is the difference between Query Studio and Report Studio in Cognos?

What is the difference between Query Studio and Report Studio in Cognos?
Could anyone explain me in detail?
Thanks in advance.
Query studio is lightweight add hoc web report writer that allows semi-power users to build ad-hoc reports via the Cognos web portal using prepared data content published to the web portal. Users can sort/filter change font size, do some grouping and aggregation... and save their reports. How ever this report writer is lightweight in that you don't have strong capabilities over presentation format and layout.... in comes report studio which is the enterprise report development tool which can develop pixel perfect reports that have a high degree of interactivity complex condition/conditional layout processing etc... Report studio can edit query studio reports as well. So sometimes users save their Query studio reports but ask for developers to tweak them to get desired appearance/functionality. Both application generate XML files that are stored in the Cognos Repository.

Debug a report using Visual Studio

I have a problem with my SSRS report when it runs from Dynamic ax 2012. I debugged it and I found out that the problem is with my SSRS report that I created in Visual Studio. I want to debug it there, but when I want to "Attach to process" I can't find ReportingServicesService.exe, because my Report Service is located on another server.
Please help me: what should I do to debug SSRS reports in Visual Studio?
I have SQL Server 2008, Visual Studio 2010, and ax 2012.
The problem is that I didn't write any code in my report: I just use a data provider in my report, but debugging the data provider code shows that the problem is in my report.
A way you can test your report is to create labels with the parameters values and othes, just to be sure that the filters or the calculated values are ok.
I'm afraid that what you seem to want is not possible: there is no way to set breakpoints in reports and debug them like you would a regular .NET app. You haven't specified what type of problem you're facing, but in general you'll have to resort to more basic "debugging" techniques:
In some cases binary search may be your best bet
If you have a clue on where the problem lies you may be able to debug that part seperately (say the data shown is incorrect, so you could debug the query seperately, in a different tool such as SSMS)
As mentioned by #Rednaxel you can use "printf-debugging" to check parameters, expressions, etc.
If you've narrowed down the problem but can't find a solution you can always ask a question about that problem here, of course.

Resources