This is Hitachi Solutions CRM's Typepad Profile.
Join Typepad and start following Hitachi Solutions CRM's activity
Join Now!
Already a member? Sign In
Hitachi Solutions CRM
Hitachi Solutions is a transformation consulting company helping clients deliver compelling customer experiences with Microsoft Dynamics
Interests: Microsoft Dynamics CRM, Dynamics Marketing, SharePoint, Office 365, Yammer, Microsoft Social Listening, Parature, Financial Services, Enterprise CRM, Manufacturing, Customer Experiences, Call Center, etc
Recent Activity
see my comment above yours. You can't do a max with calculated fields, but you can build a view that includes multiple rollup fields grouped by "or" to get your desired results.
sharing with users creates a much greater performance impact. When you share a record with 5 users, 5 records are created in the POA table (and many more downstream with sharing cascading). Sharing with a team or using access teams creates one POA table record for the team, no matter how many people are on the team. Team sharing and access teams are similar from a POA standpoint, access teams have lower overhead as they don't have all of the relationships like queues that owner teams do, they are also more user friendly as it is very easy to see whom the record is shared with. Just sharing with users/teams it is not obvious to users who view the record who the record has been shared with.
To avoid this happening, move the data from the teamtemplate entity to your other instance, including the GUID (ID). The problem you saw was the subgrid references the GUID of the access team template, and since that template ID does not exist in the new org, it cannot find it. By first moving the team template records, including the ID, you will be able to move customization between orgs.