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).
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, if a particular field in GRESB is blank, that blank value will not be synced to GRESB via an API sync. For example, if the Street Address value in Envizi is blank, and the current value in GRESB for the corresponding location is "123 Test Street", the GRESB value will remain "123 Test Street", even after the sync. The only way to render the field blank from within Envizi is to apply the Clear function from within the GRESB Asset Summary with API screen.
The reasoning provided by IBM is that "treating blank fields as instructions to overwrite or delete existing values in GRESB could lead to undesired outcomes. Similarly, users may update field values directly in the GRESB web portal without first recording them in Envizi, and syncing blank fields from Envizi in such cases could inadvertently erase those updates in GRESB. By excluding blank fields, we aim to prioritize data integrity and prevent these unintended outcomes."
We disagree with this assessment. GRESB data is accurate when it has parity with the source data (i.e., Envizi), even when the source field is blank. While it is true that GRESB values previously provided directly into GRESB may be removed, if replaced by a blank value, the current GRESB values could just as easily be erroneous and in need of correction.
Furthermore, relying on the Envizi user to clear GRESB fields on a location by location basis raises the risk of human error (e.g., a field that needs to be cleared is missed).
Idea priority | Low |
Needed By | Not sure -- Just thought it was cool |
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.
Thanks for raising the enhancement request and providing the context.
To clear content for a particular question, the 'Clear' operation would be required to deliberately perform the action. Blank answers would be ignored when being transferred to GRESB as the system wouldn't know if the answer is yet available and as a result is being omiited (either deliberately or mistakenly), or is an instruction to perform the clear operation fo data already in GRESB.
We will need additional assessment to see if the request can be supported.