Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Oct 29, 2025

Fix the Refetch errors on Work Order table

Reproduced this in the IBM sandbox, version 9.0 with following steps:

1. When in Work Order Tracking (T & D) application, open a work order that has a task with inconsistent WORKPACKMTLSTATUS from the parent work order.   Doing an update on a current WORKPACKMTLSTATUS  using SQL is the only known way to replicate this issue.
2. Under Plans tab, change the description on both the parent work order and the task with material at the same time and Save
3. Error pops up "Record WORKORDER ... has been updated by another user."

This is occuring in our environment because we have custom code that propages the work order description field down to a field on tasks and WORKPACKMTLSTATUS is often inconsistent. 

Root cause: 

WO.updateHierarchyWPStatus is attempting to update the parent work order WORKPACKMTLSTATUS using the relationship "parent". That parent mbo is different from the original parent WO mbo that was saved. This wouldn't be a problem except that WORKVIEW update got called due to the description update and initialized the mbo early.

We found that overriding either WO.updateHierarchyWPStatus or WorkView.update can fix the problem.

Idea priority Medium
Needed By Month