Missing D365 field on Dataverse

(1) Share

Report

Posted on by KP-08101030-0

105

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

Categories:

Power Platform integration

I have the same question (0)

All responses (3)

Answers (1)

Martin Dráb 235,412 Most Valuable Professional on at

Like (0)

Report

Missing D365 field on Dataverse

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.

Was this reply helpful? Yes No
Verified answer

DAnny3211 10,421 Moderator on at

Like (0)

Report
Missing D365 field on Dataverse

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:

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.

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.

Use Virtual Entities (if applicable)

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

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! 👋

1 people found this reply helpful.

Was this reply helpful? Yes No
Martin Dráb 235,412 Most Valuable Professional on at

Like (0)

Report

Missing D365 field on Dataverse

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.

Was this reply helpful? Yes No