Microsoft Cloud for Sustainability

From the standpoint of the user, the column name in Excel that they export using the Export to Excel function ought to match the name that appears in Views. If we can modify the column name in Views without utilizing Javascript, it will be more beneficial.

Need a solution to backup all setting from a tenant to another, like data import, calculation profiles, calculation models, factory libraries, greenhouse gas, facilities, organization units, etc..

Just like solution in Power Apps.

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.

As an ISV vendor with long term experience in energy applications we have recently added support to ingest our energy collected and calculated data into the Microsoft Cloud for Sustainability. We would like to see support in the data model for Facility Occupancy, similar to Production Counts. Occupancy typically varies on a daily basis and as such the Allocation Profiles support is not adequate. We can track in our software data from card entry systems or individual areas occupancy indicators and having the capability to have a dedicated dimension in the emissions data model would enable us and our end users to normalize carbon emissions so that we can compare "similar" facilities.

It's somewhat common for our Enterprise business to receive negative consumption values from our Utility provider/s. The typical reason being a bill adjustment. On other occasions, a site with solar may generate more than it consumes.

Unfortunately, Sustainability Manager does not accept negative values and we have to transform prior to data import by subtracting from previous records or other facilities.

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

I have many final users that will be reporting in MSM and I would like to be able to place a time limit on how far back the user can go to edit and/or delete information that they have previously uploaded. For example, not allowing users to edit or erase anything that is older than 3 months.

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.

Integrate MSM with Systainalytics

Today, the calculation job errors log provides the Activity ID guid which is a system specific reference. This makes troubleshooting calculation errors challenging for the customer. Adding [msdyn_origincorrelationid] and/or [msdyn_name] to all error logs will facilitate faster troubleshooting as these attributes are known to the customer and will enable the customer to more quickly identify and correct specific data gaps.