Why can’t you delete invalid values in List Manager after 10.5.2 OM?

I’ve noticed that after the upgrade for the 10.5.2 application, the Association Type list in List Manager has what appears to be bad or inappropriate values. Also, it doesn’t appear that I can delete them. The check box that is normally displayed for each entry is missing. The inappropriate values include:


Changes related to the UX framework caused changes to be introduced to the application OM. These need to be cleaned up in applications where the 10.5.2 OM package has been applied. At this time, the entries can be left alone as they are not being used and have no impact. We are developing a solution to remove these invalid entries and this document will be updated once that is made available.

Continue reading

Why can’t you cut and paste in hierarchy to same parent in 3.5.1?

After upgrading to TRIRIGA 3.5.1, the cut-and-paste function in a hierarchy no longer allows for cutting and pasting back to the same parent. In previous TRIRIGA versions, this function was allowed. When attempting to use this function to copy a hierarchy item back to the same level in the hierarchy, a message is displayed:

“Unable to paste because a record with the name {record name} already exists in the target path.”

This is a design change implemented in TRIRIGA 3.5.1 to address a defect identified in TRIRIGA 3.4.2 where cutting and pasting an hierarchy item back to the same level was causing inconsistencies with the hierarchy path.

[Admin: This post is related to the 03.28.16 post about IV82666.]

Continue reading

IV93263: Orphaned table T_TR_SU_QUE_RES_TR_SU_QUE

I have a table that does not seem to match the normal naming convention. We also noted that the table has no linkages to IBS_SPEC.

Can you confirm if it is part of the current TRIRIGA product? Perhaps it is left over from some old function. The table is T_TR_SU_QUE_RES_TR_SU_QUE and may be left over from some type of questionnaire. The content includes things like the following: “Did you like the move?” We have been upgrading since version 8. We are currently on TRIRIGA and 10.3.0.

Continue reading

How do you install BIRT Designer 4.6.0 with TRIRIGA 3.5.1 and later?

Starting in TRIRIGA 3.5.1, a new BIRT engine was introduced with your TRIRIGA installation. This is BIRT engine version 4.6.0.

To customize or create new reports, as well to convert your old BIRT 4.3.1 reports, you need the same BIRT Designer version. This Designer runs on the Neon Eclipse platform and you can use your current Java 1.8 with it (in older designers, you needed a Java 1.6, 32-bit, to make it work). This new version is optimized for Mac (in older versions, a lot of manual steps were needed). Also, you can have it as an application now. For Windows, it remains a folder in the location of your choice.

Another often-raised topic is about “upgrading from 4.3.1 to 4.6.0”. The fact is you can have both installed in your machine. They are separate installations. The caveat here is that you cannot use the same workspace for 4.6.0, if you already have 4.3.1 installed, so you just need to rename the workspace used for the first time.

So let’s start with what you need…

[Admin: This post is related to the 08.19.16 post about failing to connect with 3.5.1, and the 08.18.16 post about getting an HTTP Error 500.]

Continue reading

IV92996: Export of forms fails to generate object migration package

The Form query action URLs that did not have the “&reportName” parameter were failing to export, since OM export functionality was expecting an “&” when parsing the URL to retrieve the report ID.

During the development of TRIRIGA 3.5.2, there was a change to remove the “&reportName” from Form action URLs. Although the Application OM package correctly has the “&reportName” on all of the URLs it delivers, upgraded environments will have “&reportName” removed for Form action URLs that were not part of the Application OM package. When one makes an attempt to export these forms, the failure will occur.

Continue reading

Is there a way to refresh exported IBM Watson Analytics data in 3.5.2?

Is there a way to re-export an IBM Watson Analytics dataset and have it refresh rather than create new data? I haven’t refined the data in Watson, just testing after doing a TRIRIGA 3.5.2 upgrade. I exported a dataset from TRIRIGA, waited a day, exported again, and it shows as a second item in Watson.

This is an issue, because there are now discovery sets apparently pointing to the first data import, so the new data isn’t showing up. I don’t see a way to re-point the discovery set, and would prefer to not recreate after going into the new data. Am I overlooking something?

Unfortunately, there is no way for the TRIRIGA Connector for Watson Analytics to refresh or append to an existing dataset, because that capability was not available in the Watson Analytics API when we were developing the TRIRIGA Connector. It’s a good RFE candidate once supported by Watson Analytics and I encourage you to submit a request for enhancement (RFE) under “IBM TRIRIGA Platform”. Also, a good source of information is the Watson Analytics forum.

[Admin: This post is related to the 12.15.16 post about finding information about the IBM TRIRIGA Connector for Watson Analytics, the 11.15.16 post about the overview and demo, and the 07.09.16 post about combining IBM Watson Analytics and IoT with TRIRIGA. To see other related posts, search “Watson Analytics“.]

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