This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Currently, editable tables publish to 'normal' tables regardless if the data has changed within the editable or not and this causes a check-in. It would be more efficient if the editable table only published when the data in that editable table has changed. This would cause less check ins, and less calcs, meaning faster calculation times.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Great idea - fully supportive
This is a great and simple idea - it depresses me how many checkins and calcs we see in some of our clients logs, surely a saving for IBM too in reducing CPU load?
The only things I'd add would be to have an additional note in the 'published to' dataset to say it was checked and skipped on the date and time checked then you can see when it was last really updated (exactly as you can now) and also an audit to say it was included in the recurring publish but no update needed, then you know it is still part of the process rather than something having gone wrong preventing the publish