What's new in Microsoft Sustainability Manager May 2025

Users were unable to create records in certain tables when audit was enabled. They faced a Plugin error while creating item sustainable content when audit is enabled. The validation issue preventing the record creation is resolved.

Before, in a heterogeneous import, if the underlying tables for the selected activities or data are the same, running 'delete previously imported data' would delete data from the same run of a different activity.

This issue is fixed. Import runs now operate independently and don't interfere with each other, even when 'delete previously imported data' is enabled for heterogeneous imports targeting the same table.

Running too many profiles disrupted the user experience. The Refresh button wasn't pulling new data and sticky headers sometimes appeared on the profile wizard.

The issue is now fixed by refreshing only the latest data. Sticky headers issue in the profile wizard is resolved. New calculation profiles now appear immediately. The refresh button uses custom logic to update the list with the latest job. We added validation on the profile filter step to prevent accidental empty values in the filter.

Previously, we detected duplicates in the OCID column for a reference data import in each query, assuming that it's a user error if there are same OCID values in data source.

We changed this behavior to maintain consistency with other data model entities in Sustainability Manager. So, the last record to process is the last record updating the existing records with same OCID values.

When users select an import and make a schedule, they may find that selecting one day of the week will automatically select all days.

This issue is fixed where only the day(s) that you click is selected. The UI was updated so that those selections are saved correctly.

Previously, calculation jobs with over 5,000 errors didn't all show up in the grid on the calculation job page.

In this release, we fixed this issue so all errors from a calculation job are visible on the page, regardless of how many there are.

Partner activity and partner emissions were missing references to one another on their respective forms.

These forms are updated with the appropriate references.

Earlier, all underlying dataflow refresh failures for PQ-related imports failed silently. The import status updated to "Error" without any error messages or indication of why it failed. The data import detail view showed the previous run's details, with the latest run's failure status.

Now, the details page shows the latest run, with a generic error message indicating that the underlying dataflow failed, the dataflow name, and a link to find the error.

Incorrect validation logic prevented the update of GWP factors for custom AR versions.

This issue is resolved, and users can now update the GWP factors for custom AR versions.

The SharePoint connector can now show all available files, and multiple files can be used for data imports. A data import can now be set up to bring data from multiple files within a sharepoint folder using the sharepoint connector in PQ connectors.

The SharePoint connector now fully supports importing data from multiple source files in Microsoft Sustainability Manager.

Customers faced an issue where, after completing an import using a Power Query Connector and editing it, the import will remain stuck in the scheduled state.

We applied a fix that resolves this issue, ensuring the import process works as expected. We originally saved the information of the existing import after it was first completed, causing us to obtain dataflow information that is no longer used after we edit the import (a new dataflow is created after saving the edit). We now always get the dataflow information from Dataverse for each import run.

Previously, the external emissions calculation profiles didn't display any filters and showed a spinner.

This fix ensures that the profile filters are always displayed and the correct source is displayed.

Excel templates were missing certain tables and columns.

We added the missing tables and columns in the Excel templates.

Previously, the IEA 2022 emission factor library's description mentioned that the CH4 and N2O values in CO2e provided by IEA were derived using AR4 GWP factors. This issue is corrected to AR6 in the library description.

Also, we made IEA 2022 emission factor value precision improvements.

Previously, it wasn't possible to update existing records from the energy data model through the data import process.

OCID is added to all the relevant activity and reference data tables to enable the ability to update existing records.

The form for product footprint table wasn't editable in some cases. This error was due to validation logic that was incorrectly triggered.

We updated the validation logic to ensure the form is editable.

Customers found a pop-up error suggesting that an owner transfer failed for an import. This error is false and only happens on existing imports after an upgrade occurred. For example, if you create an import using version 2.26 and upgrade to version 2.29, you may see the error message come up yet the transfer was successful.

If you see this error after upgrading Sustainability Manager from a version before 2.28, verify that the transfer was successful. You shouldn't see the error from version 2.28 onwards on an upgrade.

This bug fix addresses the issues around copy and save functionality for customized dashboard in the insights section (Overview, Emissions, Water, Waste, Social, and governance).

This bug fix corrects the incorrect results shown on the visuals related to emissions break down by sdds for Scope 1, that is, stationary combustions, mobile combustion, industrial process and fugitive emissions on the Scope 1 page of the insights section.

Previously, any connect-to-data goals measuring water quantities would return 0 even if data was in the system.

We fixed this behavior so goal check-ins measuring water quantities display accurate aggregations.

Previously, some calculations jobs executed more than once when not intended by the user. This error created duplicate work in the system.

We made updates to ensure each calculation job gets executed exactly one time and not more.