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 Submitted
Created by Guest
Created on Jan 21, 2026

External file movement creating a new file

Scenario1:

When both packages (source and target packages) are external packages say Ext1 and Ext2 and both are at the same level in browser tree (say under the root node). In this case when we move class from Ext1 to Ext2 in that case, the file won't move but it's reference are created in respective sbsx file. Ext1.sbsx file will remove the reference of moved class and Ext2.sbsx file will have it added the reference of moved class. So no duplicate files are created here. Which is working as expected.

Scenario2:

When both packages(Source and Target) are external packages say Ext1 and Package1, but Package1 is a child of Ext1 package, in this case when we move class from Ext1 to Package1, in this case the class file will remain in folder Ext1 and when user save the model, it creates another file for that class inside Package1 folder. Here duplicate file is getting created.


Every time creating new file is not advisable while we are working on a SCM .
There should be some property or setting to avoid this .

Idea priority Medium