IBM Watson™ Ideas

Welcome to the IBM Watson™ Ideas Portal

We welcome and appreciate your feedback on IBM Watson™ Products to help make them even better than they are today!

If you are looking for troubleshooting help or wondering how to use our products and services, please check the IBM Watson™ documentation. Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.

If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.

Make "name" optional for updateConfiguration and updateCollection

The Discovery updateConfiguration and updateCollection operations currently require name to be specified in the update request. If the user doesn’t want to change the name — just some other attribute — they still have to pass the "name" (and make sure the value is the same so it doesn’t change). This is confusing and burdensome to the developer.

These operations would be clearer and easier to use if "name" were instead defined to be optional.

  • Guest
  • Mar 10 2020
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? As an application developer, I don't want to specify all fields when updating a collection or configuration
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags