Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
Had a user ask me about measuring/reporting usage in Dynamics. He meant at an individual level (page views, clicks, etc) & knows about Organization Insights already. Has anyone pursued/investigated a feature like this that would be willing to share feedback/strategy? Off the top of my head i would assume it is possible IF:
- GA tracking token is executed on every form
- Must pass back custom variables to GA. These will be defined by .js executed onload providing form name, entity type, current user then immediately firing the GA tag..
I believe this is all theoretically possible. But wanted to see if anyone had an opinion or suggestion they would be willing to share.
We are going live with D365 soon. Even I am looking for best practices of measuring the usage. Any suggestions would be appreciated.
They do have a feature called Organization Insights which i highly recommend installing. If you are getting it soon, it likely will be installed already. If not, its free and just needs to be added. It will give you high-level information but nothing that a sales manager would consider useful imo. What my end-user is after is making sure people are actually doing stuff in there and identifying people that do very little. For the people that do "very little" you can easily identify them because usually they dont even log in lol. Running this fetch-xml via the XrmToolBox will return some data you can use to figure out those don't log in:
<fetch aggregate='true' >
<entity name='audit' >
<attribute name='createdon' alias='LastAccessTime' aggregate='max' />
<condition attribute='operation' operator='eq' value='4' />
<condition entityname='su' attribute='isdisabled' operator='eq' value='0' />
<link-entity name='systemuser' from='systemuserid' to='objectid' alias='su' >
<attribute name='systemuserid' alias='SystemUserId' groupby='true' />
<attribute name='domainname' alias='DomainName' groupby='true' />
<attribute name='fullname' alias='FullName' groupby='true' />
Probably more than you want to know at this point but i would store that XML for a rainy day.
Business Applications communities