vchiem

Issue:We need to concatenate two fields 'firstname' and 'lastname' into one field using Jaspersoft MongoDB Query language. How can this be achieved ? Solution:The following MongoDB Reference: https://docs.mongodb.com/manual/reference/operator/aggregation/concat/index.html has usages on how to perform a concatenation of string fields. You can use the $concat operator within the aggregate operator. Example for TIBCO JasperReports Server version 7.5: { collectionName : 'address', aggregate : [ { $project : { fullname : { $concat: [ "$firstname", " - ", "$lastname"] } } } ] }[/code] Related Articles:https://community.jaspersoft.com/wiki/jaspersoft-mongodb-query-language

Issue:Upon importing a catalog the follow error was encountered: 2020-09-14 17:43:48,476 ERROR ImportRunnable,pool-14-thread-12:78 - Import failed: com.jaspersoft.jasperserver.export.service.ImportFailedException: Import failed. Reason: error getting schema...Caused by: com.jaspersoft.jasperserver.api.JSProfileAttributeException: Substitution error in resource /organizations/MYORGANIZATION/Domains/lm/Learning_files/Learning.xml, field . Attribute 'User_xxxxx' is not defined in the Entire hierarchy.[/code] Solution:The error is based on a non-existent attribute, 'User_xxxxx'. Add the profile attribute to the 'superuser' account prior to importing the catalog file since 'superuser' was the user whom performed the import.

Issue:We are trying to export and import reports with scheduled jobs between different TIBCO JasperReports® Server environments of the same version. For one specific report with a scheduled job, the following error was thrown upon importing: 2020-09-09 11:20:39,311 ERROR ImportRunnable,pool-14-thread-1:78 - Import failed: com.jaspersoft.jasperserver.export.service.ImportFailedException: Import failed. Reason: provided zip file is not valid JasperReports Server export file.[/code] However, when the report was exported without the scheduled job included, the import was successful. What can be the reason for this error ? Solution: The error message is an indication that the exported zip file does not have the structure expected for the import to successfully import the catalog. After analyzing the contents of the exported zip file, the cause was identified to be due to a corrupted scheduled job. Upon inspecting the path structure in the zip file, for this specific job it has the following path: ..reportJobsorganizationsAT08_SALES_TEST This is not aligned with the organization name referenced in the other paths. It should be 'AT10_SALES_TEST' and not 'AT08_SALES_TEST'. How the scheduled job got to this corrupted state is unknown but it was in a Disabled state with a jobid of 3 so it is possible the scheduled job itself had a problem. A corrupted scheduled job leads to a corrupted file structure of the exported catalog and the import failed to process. The suggestion is to import the report without the scheduled job and then re-create the scheduled job in the target environment. ref: 01891998

Issue:After carrying out an upgrade from TIBCO JasperReports® Server 7.1 to TIBCO JasperReports® Server 7.8, the Server Attributes that were present in TIBCO JasperReports® Server 7.1 under Sever Settings -> Attributes are no longer present in TIBCO JasperReports® Server 7.8. The following commands were used during the upgrade process: Export: js-export.sh --everything --output-zip js-7.1-EXPORT.zipORjs-export.sh --everything --include-attributes --output-zip js-7.1-exportwithattributesflag.zip[/code]For both the above commands, we inspected the exported catalog file and the organization.xml within the zip file does contain the Server Attributes. Running the upgrade script: js-upgrade-newdb.sh js-7.1-export.zipORjs-upgrade-newdb.sh js-7.1-exportwithattributesflag.zip[/code]The upgrade script ran successfully with no errors but after logging into TIBCO JasperReports® Server 7.8.0, the "Server Attributes" page under the "Server Settings" does not contain any of the server attributes. Note: This issue may also be present when upgrading from and to varying TIBCO JasperReports® Server releases. Solution:The issue has been logged as a defect with reference: JS-59479: Server Attributes are not upgraded after running js-upgrade-newdb.bat/.sh Until there is a fix to the upgrade script, the following workaround is available. Workaround: The workaround is to manually export and import the server attributes only. 1> In the source environment, only export the server attributes with the --include-attributes option. This will generate a very small export catalog file. Example: js-export.sh --include-attributes --output-zip js-7.1-exportwithattributesflagonly.zip 2> Log into the upgraded target environment as 'superuser' and go to Server Settings -> Import and import this zip file. After this you should see the server attributes imported. Note: For TIBCO JasperReports® Server version 7.8, when you import a catalog created from a release pre-7.5.0, select the radio button "Legacy Key".

Issue:We are trying to work out how to calculate the crosstab bucket measure size for a Crosstab report designed in TIBCO Jaspersoft® Studio so that it can help in setting the net.sf.jasperreports.crosstab.bucket.measure.limit property. How can this be achieved ? Solution: The formula to calculate the crosstab bucket measures is: For JRXML Crosstab reports (number of crosstab rows) x (number of crosstab columns) x (number of user-defined measures) For Ad Hoc Crosstab reports (number of crosstab rows) x (number of crosstab columns) x (number of user-defined measures + 1) Note: The (measures + 1) formula applies to Ad Hoc Crosstab reports because it has an additional measure created internally. In TIBCO JasperReports® Server 7.5.0 and above, there is a new logger component which can be added to the "Log Settings" page to enable the TIBCO JasperReports® Server engine to calculate the size of the crosstab bucket measures and log these counts in the jasperserver.log file. In order to see the crosstab bucket measure values, debug logging needs to be enabled for the following component : net.sf.jasperreports.crosstabs.fill.calculation.CrosstabBucketingService Sample 1 - BucketLimit.jrxml: The following is a sample of the entries that would be logged to the jasperserver.log: 08:02:38:913 [main] DEBUG calculation.CrosstabBucketingService - crosstab has 165 row buckets, 234 column buckets and 5 measures 08:02:38:913 [main] DEBUG calculation.CrosstabBucketingService - bucket measure count is 193050, limit 0 08:02:39:895 [main] DEBUG calculation.CrosstabBucketingService - crosstab has 165 row buckets, 234 column buckets and 5 measures 08:02:39:895 [main] DEBUG calculation.CrosstabBucketingService - bucket measure count is 193050, limit 0 08:02:40:646 [main] DEBUG calculation.CrosstabBucketingService - crosstab has 198 row buckets, 234 column buckets and 5 measures 08:02:40:646 [main] DEBUG calculation.CrosstabBucketingService - bucket measure count is 231660, limit 0 Note: The bucket measure value is computed per crosstab instance, and not for the whole report. If the report has a crosstab in a group footer that repeats three times, then there will be three crosstab instances, each with its own bucket counts. Sample 2 - CrosstabBucket.jrxml : For the sample report, CrosstabBucket.jrxml, the engine detected 15 crosstab instances. After setting debug, for the 15th (last) instance, the following values were computed: 2020-08-12T12:55:33,864 DEBUG CrosstabBucketingService,pool-6-thread-1:110 - crosstab has 3109 row buckets, 6 column buckets and 10 measures 2020-08-12T12:55:33,866 DEBUG CrosstabBucketingService,pool-6-thread-1:113 - bucket measure count is 186540, limit 100000 The 15th crosstab's output is attached after exporting to XLSX and you can see from the number of rows that the value 3109 is accurate. The number of columns is based on the months per SubGeography. Related Articles: JS-34784: add debug log with crosstab bucket measure values

Issue:What is the purpose of the "Minimum Details To Start From Top" property that is found in the group footer ? In TIBCO JasperSoft® Studio, when hovering over this property, the tooltip has the following description : "Minimum number of details to be rendered on the current column, to avoid starting the group on a new column". Solution: The property minDetailsToStartFromTop is the minimum number of details to be rendered on the current column/page, to avoid starting the group on a new column/page. This would help make sure groups do not start too low on the page and at least a specified number of detail records fit into the remaining space.