Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
With emails going out from Microsoft about the Team Member Custom Entity Limit enforcement. Does anybody know how this works?The email warnings states: "Users with a Team Members license are now limited to creating, updating and deleting records for a maximum of 15 custom entities"My Question is which 15 custom entities?If a system has 20 custom entities, created for providing structured lists with the 360 degree view. Which 15 of the 20 do team members get to use?It's possible that two users with team member licence may have need to access only a subset of 20 custom entities, do we have to list the 15 users can use or is there another mechanism that decides this arbitrary limit.
I remember a time when CRM licences were a simple affair.
Its a very good question. :)
I believe information will come out soon.
I will also try to check and will get back.
You should have the ability to select which of the 15 entities the user has access to under their Team licence. I cannot fathom that it would be any other way!
How it is applied though, not sure. Perhaps through creating a Security Role where you set the privileges there?
Thanks for the feedback everybody. We await the news on this given the deadline isn't that far away.
One possible suggestion of how Microsoft are going to impose the 15 entity limit is specialized Site Maps for various aspects of your solution.This seems to be in keeping with the new model of building applets (aka powerapps).
I hope Microsoft come out with clear directions soon as a number of customers are getting nervous about what this means.
This decision IMHO is also likely to lead to development strategies that exist parley to prevent excessive licence costs rather than best designed application approaches. For example Entities that exist to provide lookup options, benefiting from the 360 degree view are likely to be consolidated into singular master lists as the arbitrary 15 custom entities could easily gobble up your 15 limit list before you get into the nuts and bolts of the application.
Kindly check out this link.
Hope this helps.
Thanks and Regards,
Business Applications communities