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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

Missing D365 field on Dataverse

(3) ShareShare
ReportReport
Posted on by 109
Hello Friends,
 
I am currently faced with an issue whereby i have fields on D365 DB , but same cannot be found on DATAVERSE
 
select OMOPERATINGUNITTYPE,OMOPERATINGUNITNUMBER from DIRPARTYTABLE party  
 
these two fields on missing on Dataverse from table DIRPARTYTABLE 
 
How can i add it to dataverse.
 
Thanks
 
I have the same question (0)
  • Martin Dráb Profile Picture
    237,795 Most Valuable Professional on at
    When saying D365, you seem to mean F&O. Are you using dual-write to synchronize F&O and Dataverse? Can you tell us more about your mapping?
     
    Note that not most parties aren't operating units and fields like OMOperatingUnitType don't apply to them. 
     
     
    For example, if you look at details of employees, they're all persons and their actual table is DirPerson, not OMOperatingUnit. Technically the schema is flattened to a single table, DirPartyTable, but the distiction of different types of records is still important.
  • Verified answer
    DAnny3211 Profile Picture
    11,397 on at

    Hi there 👋

    Thanks for your question!

    If you're seeing fields like OMOPERATINGUNITYTYPE and OMOPERATINGUNITNUMBER in the D365 Finance & Operations database but not in Dataverse, it likely means those fields haven’t been exposed through the Dual-write integration or virtual entities.

    âś… Here’s how you can add them to Dataverse:

    1. Check Dual-write Mapping

      • Go to Dual-write > Table mappings in your environment.
      • Locate the mapping for DIRPARTYTABLE.
      • Check if the fields are available but not mapped. If so, you can manually add them to the mapping.
    2. Extend the Entity in Dataverse

      • If the fields are not available in the mapping, you may need to extend the entity in Dataverse by creating custom columns that match the D365 fields.
    3. Use Virtual Entities (if applicable)

      • For read-only access, you can expose the fields via virtual entities using OData or custom connectors.
    4. Ensure Field Visibility

      • In some cases, fields may exist but are hidden due to security roles or field-level security. Make sure your user role has access to view them.

    💡 After updating the mapping or entity, run a sync to ensure the data flows correctly into Dataverse.

    Hope this helps!
    âś… Please mark this reply as helpful if it answered your question.
    Best regards! 👋

  • Martin Dráb Profile Picture
    237,795 Most Valuable Professional on at
    What was the actual solution? The AI-generated answer below mentions two completely different scenarios and several suggestions and it's not clear what the actual answer was. That makes this thread quite useless for anyone looking for an answer to the same question.

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

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 Dynamics 365 | Integration, Dataverse, and general topics

#1
#ManoVerse Profile Picture

#ManoVerse 93

#1
Siv Sagar Profile Picture

Siv Sagar 93 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 62 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans