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 Future consideration
Created by Guest
Created on Nov 27, 2021

Importing a view: Don't make the attribute fields be read-only

When importing a view:

(not to be confused with creating a view in Maximo directly via the UI)


With imported views, there is a limitation in the DB Config application —> Attributes tab where the attribute fields become arbitrarily read-only, depending on the combination of fields that are chosen:

  • Type

  • Length

  • Search Type

  • Default value

(The fields are read-only -- even before I initially save the new object; the object has never been saved, so the fields shouldn't be read-only.)


The limitation is in the UI, not in the underlying MIF/business rules. I know this, because the fields aren't read-only if updating them via Application Import/Export (flat file) or via MxLoader.

IMPORTED DB VIEW: HOW TO SET CALCULATED/PERSISTENT TEXT ATTRIBUTE SEARCH TYPE TO WILDCARD?


I had reported this limitation to IBM Support, but their response was to work around the limitation using back-end UPDATE statements (and restarting the application server).

Instead of using the UPDATE statement/server-restart workaround (not a practical option), or using the other workarounds I mentioned (Application Import or MxLoader), it would be helpful if IBM could improve the UI so that it doesn't make the attributes be arbitrarily read-only in the UI.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 23, 2022

    Thanks for pointing out the issue. This looks like a bug - we would need to evaluate it internally and in any case improve the experience such that we do not need to resort to db updates.