I have a Crystal Report (version 11.5) that uses bookmarks. When the report is exported to pdf, it creates a bookmark for each branch of the "group by" clause. This is implemented by checking a check box in "File->Export->Report Export Options".
I have a sub report that I insert into the main report. It has a different "group by" pattern than the main report. I want the bookmarks from the sub report to also show up in the main report.
Is there any way to do this? What I'm trying to accomplish is different levels of bookmarks in the output pdf. For example, my main "group by" has 5 fields so I get 5 levels of bookmarks. In some cases, I only want 2 levels of bookmarks so that is why I pulled this out of the main report and into a subreport hoping I can get bookmarks with different levels.
So far the best situation I found merges two pdf files. Each will have a different grouping. This is not ideal, but it works.
Related
I am trying to run a ESS job that will create two files as output. My requirement is to create an extract file and another file that shows how many records are present in the extract file. I know how to create the extract file by writing the select query , but how do I find the count in the first select query and send it to another file ? These two files should be generated when I run the same ess job.
One report should be created after another
If you haven't seen it, I believe that this document going over creating reports in BI can assist - https://docs.oracle.com/cd/E28280_01/bi.1111/e22257/create_rpt_jobs.htm#BIPUG188
Specifically section 4.3
I am using VFR reader to display my pdf's. I need to extract the Table of Contents on a button click and display it in a tableview then it should lead to the respective pages while tapping on each.
Parsing the PDF Table of Contents is actually not extremely hard. You can use a tool like Apple's PDF "Voyeur" to see the structure or something like Adobe Acrobat's Preflight Browser:
You see that the "Outline" is a fairly simple tree that can be parsed using the various CGPDF* functions. The challenge here is to also parse the destination/action type. PDF doesn't make things too easy and doesn't give you a page number, instead usually you will find a linked named destination. This can be resolved by cross-referencing another table, it's best to look this up in the PDF spec. This is of course just one of the options, it can also be that the destination is one of the > 10 action types that rage from GoTo over named actions (e.g. Next Page) to JavaScript (e.g. this.pageNum = x). In the image above you see a classical GoTo action with the longer string being the named reference.
There are also some other special cases, notably for older latex documents and some pages from the PDF 1.1 spec that did things a bit differently, so be careful about implementing all corner-cases of the PDF spec to not get surprises later on.
Outlines sometimes also include URI actions, so at least implement that type as well. And they can also have font styles and color, so you won't ever get bored. Been there, done that in our commercial PSPDFKit PDF SDK for iOS and Android.
I recently customized the structure of filter exports to Excel following the instructions found at https://developer.atlassian.com/display/JIRADEV/Customising+JIRA+Excel+Output. This is great if you want to change the look and feel of the exported excel file.
However, how would I achieve conditional formatting based on status of exported issue set. For example, I would always like to see the "Closed" issues in Green color and "Ready to Test" items in Yellow. How do I achieve this?
Expected outcome
You could also use the Traffic Light add-on to create a custom field with the chosen color.
https://marketplace.atlassian.com/plugins/de.polscheit.jira.plugins.traffic-light_status
This is less distracting than coloring an entire row I find.
Use the Better Excel Plugin to export JIRA issues to custom Excel spreadsheets.
Important difference: these are real Excel files (XLSX format), unlike the HTML tables produced by the built-in Excel export feature.
You can use so-called tags to implement custom behaviour in the template. These are similar to HTML or JSP tags. In your case you should use the jt:style tag to specify the fill-background-color and fill-pattern properties, and wrap it in a jt:if condition.
Disclaimer: I'm a developer working on this plugin.
We have a huge number of Page Reports created using ActiveReport (*.rdlx files)
We use them from our ASP.NET MVC web appolication.
All captions and other stuff were initially created on English
Now we need to add a multilanguage support there so, somehow we need all existing texts be inserted in resource file and so we can then add translations
Is there a way to achive this task quickly, without going to each report field and manually extracting it into resource file?
Documentation says that once you change Language property, resource files will be created, but seems it is not working for XML reports, or there shouldbe a trick
For the reports designed with Code-behind, resource files are created pretty much the same as if you will create a Windows form... but I fail to find out how to do this for XML reports.
Page Reports support a localization; however it doesn't do so with a resource file.
This is mentioned off-hand in a single sentence on the page about Localization with ActiveReports 7.
Setting up a localized value in a Page Report is done the same was as you do in a Section Report. Simply change the report's Language property and then set new textbox values. At report runtime the appropriate value for the textbox will get used.
As I mentioned above, this doesn't generate a separate .resx file; instead if you inspect the resulting .rdlx you'll find a custom dd:LocalizationResources element is created that specifies the language setting and the new values for report elements.
The Localize property you are referring to in the documentation and in the code-behind reports are for the code-based "Section Layout" Reports but won't work for XML-based "Page Layout" reports (if you look at the generated code for the report, you'll see that the designer is just generating a bunch of code to localize the report).
Since code-behind reports support custom code or you can add references to another DLL you can write a simple function to localize captions. There is a good example of localizing this for .rdl reports here, you can use exactly the same approach with the ActiveReports' .rdlx files.
During that initial configuration of the report to be localizable you'll either have to manually change each static string to a Code.LocalizedValue call or maybe you could write a simple script to find each //Textbox/Value elements and replace it with a similar call. A simple script with a combination of xpath and regex could do help you automate the initial configuration of the report. To localize something other than a Textbox Value in the report (e.g. report parameter, labels/bookmarks), you'll need to replace the text of a different element than the Textbox Value but the concept is the same.
Of course, I am assuming you are localizing the static strings in your report. If you want to localize the values from the database then you'll have to do that differently (comment if you need help and I'll explain).
I recently upgraded to Excel 2010. I was working on a spreadsheet and wrote some code and went to save it and I get this box that pops up. I'm not sure what to do.
From Office 2007 on, Excel has two different file types: XLSX and XLSM. The former is just data and formatting without macros or anything "dangerous." The latter allows macros and other programmatic functionality. The reason for the split is mainly security as each one has a distinct extension and icon to better inform the user on whether or not the file could potentially contain dangerous content.
In this instance, you need to click No, then in the Save As... options select "Excel Macro-Enabled Workbook." That will give you the full functionality of the original document.