Episode 74: Markus Erlandsson talks to Ted Ohlsson from DXC about Dynamics 365 Integration Flows. Where Ted starts with explaining how Common Data Service fits into Data Connectors and Integration Engines. He continues to describe three integration templates or Application Lays, Prospect to Cash, Field service and Project service Automation integration. What the difference between a logic app and data integration project is.
Bio:
Ted is a Solution Architect and a Team lead at DXC. Working with one foot in business and one foot in technology.
Episode 68: Markus Erlandsson talks to Steve Mordue from Forceworks about the Microsoft Power Platform. Steve starts by explaining what the Power Platform is and how it includes the Common Data Service (CDS), PowerApps, Power BI and Flow. Steve continues how this change to the Power Platform will change the apps that we build for Dynamics 365 Customer Engagement.
Bio
Steve is a Microsoft Dynamics 365 MVP, CEO of forceworks who was recently one of the first partners to achieve the Gold ISV Competency and a former Microsoft Partner of the Year
A Former Salesforce.com consultant, who, after 10 years, saw the light in 2011, and moved to Dynamics CRM Online(now Dynamics 365)
Episode 63: Markus Erlandsson talks to Jukka Niiranen from Elisa about Dynamics 365 Spring Release 2018. Jukka explains what the new Business Application Platform is all about and how it is based on Common Data Service and how that is the 2.0 of XRM. We speculate if there ever will be a next version of on-premise and how the new licensing works for Marketing as well as what is new for GDPR and compliance.
Bio:
Jukka works as a Dynamics 365 Tech Lead at Elisa, and is a Microsoft MVP for Business Solutions. He has 10+ years of experience from Microsoft Dynamics CRM and has been writing his Surviving CRM blog ever since the days of CRM v3.0.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager