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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Virtual entity to own tenant

(0) ShareShare
ReportReport
Posted on by 55

I would like to expose some account and contact data to our phone system supplier. 
they will lookup the number within CRM and pass it on the MS Teams call. 
I don’t want to give them access to all account and contact fields. I can set fieldsecurity on all fields off course but that isn’t the best solution I believe. 

can we do a virtual entity with ODATA to our own tenant without coding something in c#?

i have created an application user, setup odata and a virtual entity for accounts with only name and telephone1 field but this isn’t working yet. 
I think something need to be passed with parameters but have no clue anymore. 

I have the same question (0)
  • Suggested answer
    Johao Larios Profile Picture
    1,795 on at

    Hello There, 


    I'm not sure if I understood your question. But this is our documentation for Virtual entities. Ihttps://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-edit-virtual-entities

    if this is not related with what are you looking for, please explain a little bit more.

  • MRCBob Profile Picture
    55 on at

    Thanks,

    It looks a lot to what I am looking for but I missing the point what to setup.

    So I have 1 CRM tenant with accounts and contact off course. I want to create a Virtual Entity which reflects the accounts and contacts but only with Name and Phonenumber:

    vEntity.png

    Now I can give permission to a user to only read v_Accounts and v_Contacts and he will only be able to retrieve Name and Phonenumber.

    I have setup the Virtual entity to use ODATAv4 with https://customer.crm4.dynamics.com/api/data/v9.1 

    I created a Virtual entity v_accounts connected to this datasource.

    • External Name: accounts
    • External Collection Name: accounts

    New fields:

    • v_accountid: external: accountid
    • v_name: external: name
    • v_phonenumber: external: telephone1

    I read in your link something about Connectionstring field as Data source secret, is this needed?

  • Suggested answer
    Johao Larios Profile Picture
    1,795 on at

    Hello, 
    The virtual entities are intended for external data sources.  So, for that reason you need to provided the connection data as mentioned in the documentation that I shared. 

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 69 Most Valuable Professional

#2
ManoVerse Profile Picture

ManoVerse 62 Super User 2026 Season 1

#3
11manish Profile Picture

11manish 43

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans