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 updateson 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
We deliver several (20+) data sets to our clients in a multi-tenant environment. These datasets are deployed with demo data. They must copy these to a secured tenant folder in order to update them with their own data. We provide a pre-defined job that will refresh all data sets. If the client has multiple data connections enabled, then they first have to edit each data set and do a 'save as' to select the data connection they want to use for the refresh (quite tedious). If they need to use a test connection sometimes and then want to use prod connection other times - then it makes most sense to have two copies of all the data sets in order to avoid having to do a 'save as' every time you need to switch the data source. This is also problematic if we update the data sets in future. The client has to recopy and resave the connections for each data set every time we issue an update or add new data sets. My suggestion would be to define/capture the data connection for use within the job itself. Then you set the data connection once in the refresh job for any data sets contained within. You can have a different job for each connection as needed. This is considerably less work and maintenance than having to have the connection saved with each data set. I believe this concept would also be beneficial for jobs running reports or other cases as well.
Do not place IBM confidential, company confidential, or personal information into any field.