I’m seeing issues within report results, where if the user profile language is in US English, the results are of one type, but if the user profile language is in German, it is showing some other data. The record while checked is the same for both cases. While opening and checking the record, the ID and name of the record varies from what it showed as a result in the report. While investigating, what we observed is that these fields are marked as “Localizable” in Data Modeler. What is the use and impact of the “Localizable” field property? Any suggestions?
I submitted an RFE to IBM and would appreciate votes if this would help you, too!
- Option to allow Report Sharing and Related Reports access to users with No Access to the form (RFE ID 108263).
Allow users with “no access” to select related reports in embedded query sections and to have access to reports shared with directly with them.
- “No access” really means that users can still see data in embedded query sections in forms, they just can’t click through to the linked record. There are lots of potential benefits here as we could share reports with specific columns but not allow users to drill in and view data they shouldn’t.
- “Read Only” access, which I’ve heard as an alternative still allows users to click through query results and view data we may not want them to view.
I exported the .rpt and the properties file from BIRT report designer, zipped it, and then saved it in the TRIRIGA Document Manager under the respective object (in this case, triProject). I then modified and updated my query report as “External”, and then in the “Options” tab, pointed to the ZIP file from BIRT. However, when I run the report to view the BIRT report, I get a MID error. Meanwhile, the BIRT report works fine when I run it in BIRT report designer.
[Admin: This post is related to the 03.29.17 post about getting an error when evaluating script in TRIRIGA but not BIRT designer, and the 05.11.16 post about running a BIRT report ZIP. To see other related posts, use the BIRT tag.]
I have two questions:
- (1) Is there any way to export the results of a query and send them as an attachment to a particular email ID?
- (2) Is there any way to schedule to get the report results and automatically send them in Excel to an email ID?
I have a few questions from our customer about TRIRIGA reports:
- Question 1: We want to create a report to show the triProperty which has more than one triBuilding as children. By using an association filter, we can only show the triProperty which has at least one triBuilding. By using a summary report, we can group by triProperty to show the number of triBuilding it has, but we can’t add another criterion based on the “Number” column. So, both two solutions above don’t work.
- Question 2: How can we do something like a “left join” in a multiple-BO report? We have noticed that the behavior of multiple BOs in a report acts more like an “inner join” query. The filter based on the secondary BO will also impact the primary BO result. Do you know any way to get a “left join” result in TRIRIGA?
- Question 3: How can we share a list of reports with users who are members of a specified security group? Our customer doesn’t want to grant the access of the “My Report” application for those groups, and they would like a solution that is more dynamic than adding those reports into the portal of the user. I don’t know if there is way to do this. Can the Admin user define a favorite list for the end users?
In TRIRIGA, I can see only 4 main types of chart reports: (1) pie, (2) bar, (3) lined, and (4) stacked bar, and these are two-dimensional. Are there any other chart type reports apart from these? And how can we report on multi-dimensional (more than two-dimensional) chart reports?
TRIRIGA ships with the following chart types in the table below. TRIRIGA also integrates with the BIRT and Crystal Reports engines, which have very robust reporting options. Note that as of the TRIRIGA 3.5.0 platform, anything that says “linear gauge”, will render as a circular gauge.
|Circular Bar Gauge||Circular Gauge|
|Circular Gauge||Circular Gauge|
|Horizontal Grouped Bar (%)||Bar (%)|
|Horizontal Grouped Bar||Bar|
|Horizontal Linear Bar Gauge||Linear Gauge|
|Horizontal Linear Tank Gauge||Linear Gauge|
|Horizontal Stacked Bar||Bar|
|Line/Vertical Grouped Bar Combo||Line-Bar Combo|
|Line/Vertical Stacked Bar Combo||Line-Bar Combo|
|Vertical Grouped Bar (%)||Bar (%)|
|Vertical Grouped Bar||Bar|
|Vertical Linear Bar Gauge||Linear Gauge|
|Vertical Linear Tank Gauge||Linear Gauge|
|Vertical Stacked Bar||Bar|
|Circular Bar Gauge (%)||Circular Gauge (%)|
|Circular Gauge (%)||Circular Gauge (%)|
|Horizontal Linear Bar Gauge (%)||Linear Gauge (%)|
|Horizontal Linear Tank Gauge (%)||Linear Gauge (%)|
|Vertical Linear Bar Gauge (%)||Linear Gauge (%)|
|Vertical Linear Tank Gauge (%)||Linear Gauge (%)|
[Admin: The “Metric” type offers more options in addition to the “Chart” type. This post is related to the 04.17.17 post and 03.04.16 post about displaying a stacked bar chart, and the 04.05.17 post about displaying a mix of bars and stacked bars.]
In a Gantt section, the section is not honoring the associated report sort order.
The issue was caused by the dynamic ordering that was implemented by the project tasks’ internal tree set. The BO query comparison was performed by using the string form of the columns. Moving forward, we resolved an issue where the default Gantt sort ordering, and the sort ordering immediately after importing an MPP project file, did not correctly order by the sequence ID based on the Gantt section query configuration.