What is the purpose and impact of the “Localizable” field property?


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?

[Admin: To see other related posts, use the Localization tag or Language tag.]

Continue reading

RFE: Can you allow users with “no access” to select related reports?


I submitted an RFE to IBM and would appreciate votes if this would help you, too!

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.

[Admin: The same question is also posted in the TRIRIGA Around the World Facebook group. To see other related posts, use the RFE tag.]

Continue reading

How do you report a triProperty with more than one triBuilding?


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?

[Admin: To see other related posts, use the Reports tag or My Reports tag.]

Continue reading

What are the different chart-type and metric-type reports in TRIRIGA?


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.

Name/Description Type
3D Doughnut Pie
3D Pie Pie
Bubble Bubble
Circular Bar Gauge Circular Gauge
Circular Gauge Circular Gauge
Doughnut Pie
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
Line Line
Pie Pie
Pyramid Pyramid
Spline Line
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.]

Continue reading

IV97245: Gantt section not keeping the associated report sort order


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.

[Admin: This post is related to the 06.14.17 post about task date issues when importing MS Project (MPP) files. To see other related posts, use the Gantt tag.]

Continue reading

IV97310: Pie chart labels are cut off in smallest portal section


The pie chart labels should actually be hidden, and not appear at all for the smallest portal section. Users should rely on tooltips for the smallest portal section. The reason labels were always meant to be hidden is because they make many pie charts unusable in the smallest portal section, due to labels bunching together in the small space. The smallest portal section should always hide the pie chart labels.

The hiding of the pie labels for the smallest portal section broke when AnyChart was upgraded in TRIRIGA 3.5.0. Moving forward, we resolved a metric report and chart report issue, where pie chart labels were chopped off in the smallest portal section. This fix hides pie chart labels when the TRIRIGA component that displays the chart falls below a height of 280px and a width of 280px, such as the smallest portal section. Pie labels become unusable when pie charts get too small. So users should rely on pie chart tooltips for the chart details, when the labels are hidden.

[Admin: This post is related to the 04.14.16 post about changing the AnyChart label settings. To see other related posts, search “Pie Chart“.]

Continue reading

IV97185: User session terminated due to missing security token


In TRIRIGA 3.5.2.2, the user’s session was terminated by the server due to a missing security token on the request when interacting with forms and large queries.

We needed to add a TRIRIGA security token to two locations in the reporting engine. Moving forward, we resolved an issue that could cause a user’s session to be terminated if the user interacts with an editable query before the query has finished loading.

[Admin: To see other related posts, use the Tokens tag or Editable tag.]

Continue reading