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 Functionality already exists
Categories Rhapsody Client
Created by Guest
Created on Jun 18, 2025

The "Delete from Model" option from Rhapsody should delete the unit files from the ewm component even for the external units added from a different component

In our current setup, Stream A contains over 100 components, with one default component containing the Rhapsody model(.rpyx). The model in Component A has data(.sbsx/.clsx/..,) added from the other 99 components. When an element(say .clsx) from Component B which is added in the model in Component A is deleted, the element is removed from the model, but its file remains in the file system of Component B. This leads to below issues:

"When the deleted element’s File is still present in the component B, the RMM API includes these deleted elements as well in its response since it gives the response from the stream level"


To address the issue, we request the following enhancements for the  Rhapsody tool:

"Introduce a new delete functionality(Hard Delete) in the Rhapsody tool to remove the added external elements which will delete it from the model and as well as the file System

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Guest
    Sep 1, 2025

    While I understand the considerations why Rhapsody behavior is as described, in the concrete use-case the reference is (logically) owned by the model in which the deletion happens.

    The model is split up into multiple RMM (EWM SCM) components to be able to only share smaller parts of complex models to other models (which then include those in read-only manner).

    Therefore - in this special case - it would make total sense if Rhapsody would delete also the referenced units. As this difference will be hard to be detected automatically, it would probably make sense to introduce an flag/option for r/w reference on how to handle deletion (and also moving of units).

  • Admin
    SANTHARAM SUNEEL
    Jul 21, 2025

    Hi,

    We’ve reviewed the reported behavior and can confirm that Rhapsody is functioning as expected in this scenario.

    As a best practice, we recommend that model elements be deleted only from their owning model. When elements are deleted through the model editor, the associated unit files are automatically removed, helping to maintain model consistency and integrity.

    If you're not observing this behavior in your environment, we suggest raising a support ticket and including the product version details. There was a similar issue reported previously, which has been addressed in the latest release.

    Important: Reference models are strictly intended for referencing purposes. Deleting elements from a reference model may lead to unintended consequences, including potential corruption of other models that depend on those shared references.

    Please don’t hesitate to reach out if you have any further questions or require assistance with the recommended procedures.

    Regards,
    Suneel...