Skip to main content

Notifications

Announcements

No record found.

Customer Service forum

Team Member Licencing & Usage of Custom Entities

Posted on by Microsoft Employee

Hi all,

Looking for an official Microsoft answer on my query below. This question comes after reading the small print in the new licencing agreement:

"Custom Entities Microsoft Dynamics 365 for Team Members and higher provide the right to use custom entities. Custom entities may be based on entities included in Dynamics 365, or created by a customer or partner. If the custom entity is based on or replicates the functionality of entities included in Microsoft Dynamics 365, or if the entity links to entities included in Microsoft Dynamics 365, then users accessing the custom entity must also be licensed to access the included or replicated entity. For example, users creating an entity that replicates the cases entity for a ticketing system would still require the user to be licensed for cases. In other words, customizations may only be performed against entities users are licensed to access."

 

I'm working with Dynamics 365 Enterprise via a Microsoft Partner based in New Zealand. We've noticed an increase in the number of small businesses approaching us for assistance in implementing Dynamics 365. These businesses are small, and New Zealand based,  meaning we would be expecting approximately 5-15 users.

Having said that, the pricing of the new Team Member licence now makes Dynamics affordable to them and the Dynamics for Outlook client is a real selling point over competitors CRM. While the pricing of an App or Plan 1 may turn them away from Dynamics as the cost is too high.

These businesses are interested in tracking:

Sales Opportunities

  • They only need very basic fields, e.g. the Account/Contact involved in the sale. Some basic (custom) product lines for the Sales Opportunity. Some basic description and date/time fields. And the Social Pane
  • They have no requirement for most of the complex OOTB Opportunity functionality including:
    • Lead entity, and lead to opportunity conversion
    • Order, Quote, Invoice process
    • Closing as Won/Lost - instead just wan't to use a Option Set

Tickets/Issues

  • Again, only need very basic fields, e.g. the Account/Contact involved in the Ticket. A few multi-line text box to describe the Ticket/Investigation/Outcome. And the Social Pane
  • They have no requirement for most of the complex OOTB Case functionality including:
    • SLAs & Entitlements
    • Auto case creation
    • Case routing & queues

Events & Event Attendance

  • Creating a record to track an Event, and which Accounts or Contact attends
  • No need for any other marketing functionality, i.e. no advanced finds or campaigns. Basic needs can be met through Advanced Find + Export to Excel

Given my comments above, can you please advise on our available licensing options, can we:

  • Create a very basic/cut down "Sales Opportunity", "Ticket", and "Event" custom entities, and make use of the Team Member licence to onboard these small businesses on to the Dynamics 365 Platform, or
  • Must we stick to a higher tier of licences, and strip/cut most of the OOTB functionality out of the platform (as it is overwhelming for these clients).

Thanks

Ashley

Categories:
  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Team Member Licencing & Usage of Custom Entities

    Ok, thank you a lot, Diego,

    Evidently developers should create their own entities not linked to embedded ones, to comply with the license.

    So you use Team Licenses for custom made applications all the same, don't you?

  • Diego Segreto Profile Picture
    Diego Segreto 35 on at
    RE: Team Member Licencing & Usage of Custom Entities

    Hi Dmitriy,

    What I heard from them is that we have to be careful not to replicate an existing entity. For instance, we cannot create a custom entity to handle tickets and assign users only a Team License subscription.

    What I did for a specific scenario (different from the example above), was to ask Microsoft directly if what I was doing was a replication or not, because it can be quite hard to judge. I can tell you that the really help!.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Team Member Licencing & Usage of Custom Entities

    Hi, I have similar small-business clients and the same idea about using Dynamics as a low-code development platform, without its OOTB apps.

    Were you eventually able to build applications with Team Members licences?

    Kindest

    Dmitriy

  • Diego Segreto Profile Picture
    Diego Segreto 35 on at
    RE: Team Member Licencing & Usage of Custom Entities

    Hi Ashley, did you receive any official answer from Microsoft on this? Can Team Member access these custom entities which are similar to the OOTB ones? The pricing guide, page 15, under the Custome Entity section says this is "replication" and can not be done. Would you mind to share your findings? Thanks.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans