From the vice president of the InfoStrat division of Serenic Software, thoughts on digital transformation, marketing automation, customer relationship management, Microsoft Dynamics 365 (formerly CRM), government contracting, customer service and more. For breaking news, follow me on Twitter @jamestownsend and for more depth see the InfoStrat website at www.infostrat.com
Subscribe to this blog
Follow by Email
Search This Blog
Microsoft Introduces Project Oakdale to improve the Microsoft Power Platform integration with Microsoft Teams
Yesterday at the Inspire event Microsoft announced a new product called Dataflex, subsequently renamed Project Oakdale which is build on the Power Apps Common Data Service. Project Oakdalesimplifies building and deploying apps and intelligent chatbots in Teams with Microsoft Power Apps and Microsoft Power Virtual Agents.
The rapid expansion of remote working during the COVID-19 crisis has fueled adoption of Microsoft Teams. Project Oakdale adds features to make Teams more competitive to products such as Slack. The new functionality of Project Oakdale allows apps and bots to be created from inside Microsoft Teams. This means that organizations can access more data without leaving Teams for other apps.
Adoption of Teams strengthens the appeal of Office 356. Some companies that rarely used Teams or even maintained subscriptions to online meeting products such as Zoom, GoToMeeting and Webex have come to appreciate Teams for internal and external collaboration. The enhanced security of Teams compared to Zoom spurred use of Teams, and Microsoft continues to add new features in order to gain dominance in this market segment.
For more details, see this post by Charles Lamanna on the Power Apps blog.
NOTE: DataAccess offers a product called DataFlex which was introduced in 1982. For now, to find technical documentation on what is now branded as Project Oakdale by Microsoft, you should search for Common Data Service or CDS.
To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud. This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant . A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions. Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com. User accounts belong to a tenant, and subscriptions are assigned to user accoun
Source: https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003. InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint. The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath . Power Apps has much in common with InfoPath. Both products include integration with SharePoint. Both are geared toward the citizen developer and do not require advan
Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts. The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator. This role is analogous to a network administrator for an on premises