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 Not under consideration
Categories Feature
Created by Guest
Created on Mar 18, 2020

Removed attribute attached to artifact type after importing component properties should be hidden

Existing data should show as hidden (still show the data), new data shouldn't have the hidden attributes.. but you should be able to see them in schema properties as hidden and also option to unhide.

Idea priority Urgent
  • Guest
    Reply
    |
    Sep 18, 2020

    if we addressed this enhancement I do not think we can try to solve both worlds. Should an import remove attributes from an artifact type then this should behave as if the attribute is actually deleted. i.e. the import process should identify if the attribute is being used and help the administrator remove the existing data.

    e.g. the import process would simply behave as if the admin were making the changes directly.

    We have triaged this enhancement on that basis