web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Microsoft Cloud for Sustainability | MSM, SDSF,...
Suggested Answer

MSM Issue Reference Data Import Using Power Query

(4) ShareShare
ReportReport
Posted on by 28

Hi Community,

I’m facing an issue while importing facility data into Microsoft Sustainability Manager using Power Query. My dataset includes a Name column and an OriginCorrelationID column. According to Microsoft’s documentation for reference data:

If a record’s Name already exists, the record is considered a duplicate unless you specify an OriginCorrelationID.

In my dataset, all OriginCorrelationID values are unique, and a few records share the same Name values. Based on the documentation, I expected these records to be imported successfully since their OriginCorrelationID values are distinct.

However, during the import process, these records are flagged as duplicates and skipped without any error or warning.

I suspect the issue arises because the Name column is the primary name field in the Facility entity, and OriginCorrelationID is not being used to differentiate records during import. This behavior doesn’t seem to align with the documentation..

I’ve attached a sample dataset to illustrate the issue, showing unique correlation IDs with identical names.

Has anyone encountered a similar problem or have insights on how to resolve this?

Thanks in advance for your help!

 

 

I have the same question (0)
  • Suggested answer
    Sachin Yelkar(MSFT) Profile Picture
    on at
    In some reference data tables, such as the Facilities table in Microsoft Sustainability Manager (MSM), a natural key is set on the Name fields. This means that the Name field is used as a unique identifier for each record. As a result, the system restricts the creation of records with the same Name, treating them as duplicates. This ensures that each record has a unique Name, maintaining data integrity and preventing duplicate entries.
  • Suggested answer
    Ivan (Vanya) Kashperuk Profile Picture
    on at
    Yeah, the documentation is poorly phrased. Basically, Name does have to be unique.
    I'll create a ticket to update the documentation to be more precise

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Cloud for Sustainability | MSM, SDSF, EID

#1
PowerSoumyo Profile Picture

PowerSoumyo 14

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 8 Super User 2025 Season 2

#3
Vahid Ghafarpour Profile Picture

Vahid Ghafarpour 4 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans