Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why am I receiving "Last Transaction may be Incomplete" errors when adding attributes to Custom Tabs?

Why am I receiving "Last Transaction may be Incomplete" errors when adding attributes to Custom Tabs?

Problem:

Why am I receiving "Last Transaction may be Incomplete" errors when adding attributes to Custom Tabs?

Resolution:


Adding a UDA to a Custom Tab is a very database intensive task. In order to add a UDA to a custom tab, each version of each requirement of a given Requirement Type must be updated to reflect the change. If any Requirements are locked (being updated) during this process, it can cause lock/contention issues in the database. This will cause the process to return a Last Transaction error.

The best way to avoid this error is to modify your Requirement Types during off hours when users are not using the CaliberRM application. This will insure there are no locking issues and allow UDAs to be added to the Custom Tabs without issue.

Old KB# 29608

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 20:38
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.