Skip to main content

Notifications

Announcements

No record found.

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

(3) ShareShare
ReportReport
Posted on by

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!

 

 

  • Suggested answer
    MSM Issue Reference Data Import Using Power Query
    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
  • Suggested answer
    Sachin Y Profile Picture
    Sachin Y on at
    MSM Issue Reference Data Import Using Power Query
    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.

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

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey Pt 2

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal...

#2
Martin Dráb Profile Picture

Martin Dráb

#3
nmaenpaa Profile Picture

nmaenpaa

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans