IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
When I request a record via the integration API, e.g via
productmaster.nateralab.com/mdm_rest/api/v1/integrations/catalogs/Tertiary Content/items/
the result only returns required fields by default.
We have a dedicated user for our microservice to call the integration API. In order to get all fields, I have to log into the UI as that dedicated user, and then for every record type I want to fetch, I have to pull up a record of that type and manually switch to a custom view that includes all the attributes I care about.
It is safest to assume I am going to forget to do this when we go to production, which will result in a very confusing production outage where half the values the app is expecting will be missing. If every team has this problem for every catalog that's six to eight possible outages.
This also means I will need to have the production creds in order to fix this issue. I would prefer not to ever have those credentials in my hands.
Personally, I would prefer that the integration API return all fields by default, but I suspect changing the default behavior in this way would negatively impact other customers who have more fields.
The second solution that comes to mind is extending the integration API to allow specifying the view to use. Then I could update my app to specify our custom view that includes all attributes as part of every API call. Not the most efficient solution, but it would work fine
The third solution that comes to mind is that if the integration API allowed me to set the desired view for a catalog for my user, I could just set the view for the catalog in question for the microservice's user every time the service starts.
Hopefully this is a solved problem and I'm just not seeing the solution in the integration API's swagger docs.