Erik Windell

This is related to working with data import connectors - "Data management" / "Data imports". Specifically the "Ready to import" toggle.

When you click "Ready to import" and change the state to "Yes", this automatically kicks off an import. Enabling the connector and running an import should be two separate functions.

1. Enable the connector by changing the state of "Ready to import" to Yes
2. Click "Import" to trigger a manual import or setup a scheduled to task

This would provide the ability to review configuration, mappings, etc., without accidently kicking off an import. It can be time consuming when troubleshooting issues to have to cancel imports.

Renaming idea:

Change "Ready to import" to a connector status of "Enabled / Disabled". Enabled state would require either a manual trigger or scheduled task.

Ultimately removing the automatic trigger of running an import after changing the state to "Ready to import = Yes" is the ask.

In the top menu bar for the "Data imports" window, the "Delete" button is right next to the "Import" button. It easy to accidently click "Delete". It would be great if the Import and Delete buttons could be moved apart.

It would be great to get email alerts when a data import completes. It should be configurable to notify on success, failure, or both. Another option would be to include any error codes and files.. Ability to specify more than one email recipient would be great.

This would be an optional selection.

Use case: We have set our data imports to run on a schedule and it would help streamline administration if we could receive email notifications when the job completes.

We have over 200 calculation profiles and it is time consuming to select individual calculation profiles and click "Run calculation". It would be great to be able to select multiple calculation profiles at one time and click "Run calculations".

We build many similar calculation profiles that may only change one item, such as country code or maybe consumption date. It would be great to be able to copy a profile, similar to being able to copy calculation models.

For troubleshooting calculation profiles, especially when trying to identify any overlap between calculation profiles, it would be nice to be able to disable or deactivate a profile.

The way we are importing data, we expect every record to generate an emissions record. One of the queries that was being worked on was to enable us to identify any activity records that did not have a corresponding emissions record. We would then use this data to both verify that the record is accurate and if we have an appropriate calculation profile to generate the emissions record.

We have over 200 calculation profiles. It can be easy to accidentally misconfigure a calculation profile, or even build the wrong logic in the first place. It would be helpful to be able to generate a view that compares the calculation profiles and identifies any overlap

Would love to see a dashboard and receive email notifications of updates that will be applied to the MSM environment. Items included could be proposed date of release, when specific regions will have it applies, a changelog of the update and category of the update (feature enhancement, bug fix, etc.). We would greatly appreciate the ability to test the updates in a sandbox/dev environment prior to the release in our production environment. It would be very helpful to have changelog information if any issues are encountered.

This is separate from the Wave Releases and focused on the weekly/monthly update cycles.

Exporting emission information out of MSM is helpful for sharing with our business partners and completing our review of emission in excel. We also like to visualize this information outside of the MSM platform for internal reporting. 

Per MS Learn documentation, the purpose of the data export in MSM is to enable the extraction and transfer of sustainability-related data to external systems or tools, such as reporting and compliance.

The current export restrictions make it difficult and time consuming to share data with external tools or partners. It would be very beneficial to us to have these limits significantly increased.