How do you query which label class is used on which fields?

Is there a way to query which label class is being used on which fields? I want to tweak the existing ones slightly, but I’m not sure what is going to be updated when I make the change.

[Admin: To see other related posts, use the Labels tag or Query tag.]

Continue reading


How do you use drawing labels for international measurements?

We manage properties globally so some of our locations are measured in Imperial and some are in Metric. What is the best way to manage this type of scenario so that our drawing and graphics section labels are not incorrectly sized when they are viewed from other global geographies?

The best way to address this situation is to have 2 sets of labels for your drawings, and 2 sets of labels for your TRIRIGA graphics section. You will need to adjust the height of the label elements to work for both situations. We are considering an enhancement to automatically scale according to the drawing units.

[Admin: To see other related posts, use the Graphics tag or the Labels 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

Why is there OM validation error with navigation collections?

I have been trying to do an object migration (OM) import, but I am getting a validation error on one of the navigation collections contained in the OM package. It is not an error I have seen before, so I wondered if anyone could tell me what it meant? And how I can resolve it?

Which TRIRIGA Platform version are you using? I know we fixed an issue related to OM packages in our TRIRIGA 3.5.2 release, where certain navigation items were not exporting correctly, which may be related to you having problems importing the object. The following is the text from the TRIRIGA 3.5.2 release notes:

“Resolved object migration issues where Navigation Items may not export correctly if the Dynamic Label check box was selected and the Dynamic Label Query was not selected on the Navigation Item definition. (Tri-250723)”

[Admin: This post is related to the 05.19.16 post about inconsistent OM validation results. To see other related posts, use the Object Migration tag.]

Continue reading

IV92514: Cannot perform Sync Full command in CI for MicroStation

After upgrading from CAD Integrator (CI) 12.1.1 to 12.1.4 for MicroStation, we cannot do a Sync Full command successfully, if there are more than 14 people assigned to any space. We get kicked out of MicroStation, or we get a message indicating that MicroStation stopped working and are forced to close the program.

The issue happens when there is a very long label applied. For example, the “People” label style appends every person to the label string. If the string is “too long”, i.e. more than 256 characters, it overflows the char buffer on the heap, causing stack corruption, usually causing MicroStation to crash immediately.

Continue reading

IV92225: Locator query headers not reflecting the correct labels

If you have a locator query that has multiple business objects, whether through associated business object or through smart sections: Pick multiple fields with names like triIDTX, triNameTX from these business objects. Change the labels on these fields so that they don’t all just say ID, ID, ID, or Name, Name, Name. Change them to something like Employee ID, Supervisor ID, Organization ID.

Now place this query on a locator field, publish the form, and go open a record. DO NOT use the magnifying glass on the locator field, but simply start typing into the locator field. The system should automatically pre-filter the query result and display it below the locator field. Note the columns now are not displayed as Employee ID, Supervisor ID, Organization ID, but rather it ignores the label changes done in the query manager.

Continue reading

Where are the untranslated labels and data in 3.5.2 and 10.5.2?

In the Attachments tab, this package contains the untranslated labels and data delivered in IBM TRIRIGA Platform 3.5.2 and Application 10.5.2. These will be translated in the future release.  You can use the files inside this package to provide translations for your supported languages, then import them into your environments.

Continue reading