WARNING: Niche L400 tip ahead. tl;dr If you’re expect primary column name to be tablename + “id“, add an exception for systemuser and team tables – both will come back as ownerid in custom API. L400 If custom API has an output property of type EntityReference then, for example, for account (or any other “normal”) table, the […]
Almost two years ago I wrote on the merits of using Teams vs Queues for managing Cases. While I stand behind what I wrote (Teams are simpler but Queues are more powerful) another element raised its head recently which is worthy of consideration if you are going down the path of setting up Case management. […]
Joel has been producing tips by a truckload, I don’t think he’ll notice if I sneak this one in, especially when a fellow comrade developer David “Xrm.Tools” Yack is in pain. David Anyone have any suggestions for where let’s say a Team/Department gets CRM in their own subscription but their e-mail is still managed by […]
In Tip 917 we talked about what happens if you have too many business units in Dynamics 365. But what about the opposite — can you have too few business units? If you are implementing Dynamics for a single group, it is common to only use the base business unit for all users. “We don’t […]
Someone recently asked me what I thought of someone adding 1,000 + business units to Dynamics 365. I told them it was a bad idea. Here’s why: Business units are like large granite rocks–they are designed to be permanent and infrequently moved. While users can be moved between business units, it is not a trivial […]
I would like to see my sales team’s appointments on the same calendar. Should I change my appointment sync rule to get all appointments for my team synchronized to my calendar? No. Don’t do it. That is a sure-fire way to make your Outlook calendar unusable. You won’t know what is your appointment, vs. your […]
Another mini truck stop, this time to assist Dylan “Not a real Kiwi” Haskins preserve his sanity. tl;dr If a team has user-level privileges, members of that team will NOT have these privileges for the records owned by individuals and not the team. For example, if the team has a user-level create privilege then a […]
Gustaf (not V) Westerlund mentions that while it may be attractive to create a team with System Administrator role to simplify security administration, the “inherited” approach is not sufficient to grant users all privileges that they need as System Administrator. For example, users cannot publish Business Rules if they don’t have a user role that […]
In a comment on Tip 211: When upgrading, don’t forget the team form, Pebo asked “what about the possibility for showing roles in subgrids of teams and user forms?” This is a great question, and we have an answer. First, you need to understand security roles in Dynamics CRM. There is not just one record for […]
When upgrading a deployment of Microsoft Dynamics CRM to version 2013, it is easy to overlook some of the back-end forms. These don’t get the attention of entities like Accounts and Cases, but they are very important to the people who use them. One of my favorite new forms in 2013 is the Team form. […]
of the