Hello all !
Here is a great video of capabilities of the Portal (B2B / B2C) for Dynamics 365
It was last year AdxStudio but now a great way to access DATA of Dynamics 365 into a Website (public or private)
Viewing entries in
Hello all !
Here is a great video of capabilities of the Portal (B2B / B2C) for Dynamics 365
It was last year AdxStudio but now a great way to access DATA of Dynamics 365 into a Website (public or private)
Today, I am happy to announce availability of the Power BI data alert connector for Microsoft Flow. By combining the power of Power BI data alerts with the hundreds of actions available for Flow, we’re making it easier than ever to go from insight to deep, meaningful action.
Microsoft Flow is a SaaS offering for automating workflows across the growing number of applications and services that business users rely on. You can set up Flows to take care of the important, repeating tasks that take place daily in your organization. For example, you can create a Flow to text you via SMS when your manager sends you an e-mail marked as“high importance.” Or, automatically create a to-do item in Wunderlist when a customer e-mails your support line.
Data alerts are a recently released Power BI feature, which allow you to be notified whenever a tile on your dashboard meets a particular criteria. For example, you can set up an alert to send a push notification whenever tile “Daily Deliveries” > 10000. With this release, we are adding the Power BI data alert connector to Flow. This means that from a Power BI data alert, you can now trigger actions in dozens of other popular apps and services. Send an e-mail to a Security Group with the value of the alert. Post to a Slack channel with a link to the tile. Create a card in Trello based on the alert name. The list of possibilities is expansive, and it’s only getting bigger – new connectors are being added to Flow every week.
Ready to get started? What follows is a tutorial walkthrough for setting up your first flow. In this basic example, we’ll send out an e-mail to a broad audience whenever a Power BI data alert is triggered. You could imagine using a similar Flow to notify your support team whenever incident volume spikes.
Firstly, go to Power BI and set up a data alert if you haven’t already. If you need help, you can find the documentation for that process here.
With the alert set up, go to Flow, and sign in with your Work or school account.
Once you’re signed in, go to “My Flows” in the top left, and create a blank Flow by clicking on “Create from blank.”
The first thing you’ll want to do is create a trigger, which is an event which sets the Flow in motion. Search “Power BI” in the box titled “Search for more triggers”, and select the Power BI data alert option which shows up in the dropdown.
Next, select the name of the alert that you’d like to use to trigger the Flow
Now, you’ll want to add an action to be performed when the Flow is triggered. In this case, we’ll add an action to send an e-mail. Click the “+ New step” box below the Power BI trigger to start creating a new option. In the search box, type “Outlook” choose the Outlook “Send an email” action.
Note: this tutorial assumes that you have an Exchange Online mailbox. If not, you can also try using the SMTP action, which allows you to send e-mail to any SMTP server.
Now, you can populate the fields of the box as you would with any email. Keep in mind that the mail will be sent from your account.
Also, notice that when you click into any field in the e-mail action, a box appears on the right, which allows you to add information from the data alert to the e-mail. For the Power BI data alert trigger, this information includes:
Once you are satisfied with your e-mail, select Create Flow in the top bar to create your Flow, and you’re done !
The next time this data alert is triggered, the Flow you just configured will activate, sending the e-mail that you configured to your target audience.
For more ideas on Flows, check out the Flow templates page to see a gallery of the most popular ideas. We’ve also added several Flow templates with the Power BI connector, including the one featured in the tutorial above.
Also, stay tuned to the Power BI blog, as we’ll be releasing something new Flow connectors in the weeks to come.
Have an idea for another way that Power BI can connect to Flow? Head to the Power BI UserVoice and cast your vote to make your voice heard.
Made a cool Flow? Share it with the community! Either post in the comments below, or in the Power BI forums. Who knows, your Flow might even be featured in the next Power BI Flow blog post!
This week, Microsoft PowerApps has been updated with improvements to Studio and Mobile apps. We will cover some of the cool features coming up in this update, with the full list on the What’s new page.
All client users who are still using preview builds must upgrade to the latest Windows, iOS and Android bits in the store. This will enable you to take advantage of the latest features in PowerApps. Users running PowerApps versions prior to 2.0.540 on Windows, iOS and Android will be prompted to update PowerApps to the latest version. Clicking on the Update will take the user to the store.
Every app is uniquely referred using an app id. To run an app in the browser you would need use a URL with its appid. You can get the URL to run the app from the app’s details page listed under the “Web link” section in powerapps.com.
Traditionally to launch an app in the browser you would use a URL like this:
On the other hand, to run apps on Windows/iOS/Android clients you can use the deep linking URL like this:
Universal links brings these two worlds together. You can use a single HTTPs URL to launch your app either in the mobile app or in the web browser based on your preference. The URL also accept query strings, which you can use to pass parameters to the app.
If the user using the link does not have the app installed on mobile, the app runs in the browser automatically.
For example, you can link a Site Survey company app to launch another app to collect user feedback. The user feedback app will run on PowerApps mobile if the app is installed. Please note these links launch the mobile apps on iOS and Android.
HTML Text control can auto resize the height depending on the length of the text. This is huge improvement over the current control where the control size is fixed and can cause the content to be chopped. To use this feature, simply set AutoHeight to true in the HTML Text control.
Here is an example of using a description field in the HTML Text control:
You can now use context variables as part of delegable expressions. In the examples below, Filter and Lookup delegate the query to the service side even though they contain context variables.
Filter(‘[dbo].[Customers]’, MyCtxVariable in FirstName)
LookUp(Filter(‘[dbo].[Customers]’, MyCtxVariable in FirstName), LastName <> MyCtxVariable2)
Microsoft PowerApps now supports eight new services this month that you can use in your apps.
Checkout the What’s new page for details on other improvements:
Today, I want to share a fantastic way to open ISV and System Integrator their solution directly to the Business User. Microsoft AppSource helps enterprise users find and gauge line-of-business (LoB) software-as-a-service (SaaS) apps from Microsoft and its partners. AppSource apps are built on top of Microsoft Dynamics, Project Madeira, Power BI, Office 365, Cortana Intelligence Suite, and Azure, and include all of their existing app add-ins and content packages.
Here is a good video from Microsoft in Youtube to explain the power of App Source :
Today there are more than 350 solutions (at the end of November) :
Depending on their business needs, AppSource allows users to access apps from Dynamics AX, Dynamics CRM, Dynamics NAV, Project Madeira, Power BI, Office 365, or Azure. Searching through all the apps offered by AppSource can be narrowed down by category, industry, or by Microsoft product. Microsoft sees AppSource as “a place to find new apps and better ways to get things done.” Microsoft hopes that AppSource will be a big hit for enterprise customers as Microsoft pushes more apps and services to the cloud using Azure.
Currently, AppSource offers most apps to businesses to try-before-you-buy to see if the apps help enterprise customers in their daily operations. Microsoft plans to reveal more information in few weeks to its partners about Dynamics 365 and AppSource.
And finally here is what Microsoft says :
« We imagine a better world for business users everywhere. One where you can track leads, automate field service, drive sales and improve operations using modern, mobile, enterprise-ready intelligent business apps from the cloud that are as easy to use as the consumer apps that help us all get rides, book rooms, listen to music and take actions to improve our health », says Takeshi Numoto, corporate vice president, Microsoft Cloud and Enterprise. »
« With Dynamics 365 and AppSource customers can encourage innovation, increase collaboration and ultimately achieve more with the power of intelligent business apps ». Customers can learn more about Dynamics 365 here and about AppSource here. »
I will look forward in December to see the future of this App Source.
What if we told you that you have the power to connect all your SharePoint lists and libraries to a host of other apps from Dynamics CRM and Yammer to Dropbox, Mail Chimp, and Twitter? Imagine creating an item in SharePoint whenever a new lead is added in Dynamics or automatically copying files from your Dropbox to a SharePoint document library. Now what if we told you that you could do this in a matter of minutes and with zero lines of code? You’d be tempted to ask if we’re crazy or have had one sleepless night too many in Seattle.
The Microsoft Flow team gives us great pleasure to announce the integration of Microsoft Flow into SharePoint Online lists and libraries. Microsoft Flow is a new workflow tool that enables business users to create automation to receive notifications, synchronize files, and get data between your favorite apps and services, be it on premise or in the cloud. Be sure to check out this and other announcements from the Future of SharePoint conference in San Francisco.
In this post, using a premade flow template, we’re going to walk you through how you can quickly copy new members from a MailChimp member list to a SharePoint Online custom list based on approval via email. We will also be showing you how we are integrating Flow directly into SharePoint lists and libraries and the future of our integration work.
Let’s imagine that you work for an office supply company called OPENFIELD. Your marketing team manages email campaigns using MailChimp but you want to track your largest accounts in a list in SharePoint Online so that you can have a column for assigning the accounts to specific members of the team, and store additional metadata to add that personal touch to customer outreach.
Let’s create a flow such that whenever a new member is added to a subscriber list in MailChimp, you receive an approval email asking if you want to add this member to the VIP SharePoint Online list. To make things easier, you can just start from this premade template. Once you open the page, click “Use this template”.
Enter your credentials and click Continue.
Now select a MailChimp member list and configure the Send Approval email step.
Then select your SharePoint Site Url and the list you want to add these members to. In the example below, we use a list named “VIP Customers”, with columns “First Name”, “Last Name”, “Email Address”, and “Account Lead”.
Configure the Create item step for SharePoint such that for every new member in MailChimp, if the approval condition is met, the First Name from MailChimp maps to the First Name column in SharePoint. Map the other values from MailChimp to the columns in SharePoint as appropriate.
We firmly believe that all of our SharePoint customers can benefit greatly by connecting their data in SharePoint to other data sources. While Flow templates are a great start, we want to make the flow even easier (pun very much intended). In an upcoming release to SharePoint, we will be integrating Microsoft Flow directly into your SharePoint lists and libraries. With this update, users will be able to simply click Add flow and select a flow template from a panel. We will automatically carry forward the context of the site and list you’re on into the Flow template that was selected.
I will continue to invest in some integration efforts with more templates for more services and a more complete experience within SharePoint itself. In addition, the Microsoft Flow Team also plan to enhance the flow authoring experience for SharePoint by:
Stay tuned for more updates and check out http://flow.microsoft.com/search/?q=SharePoint for all SharePoint focused Flow templates.
With the launch of Microsoft PowerApps and Microsoft Flow, I thought it would be useful to have a close look at the underlying database and integration capabilities of these new systems.
In this, the first of two posts on the topic, I summarize the native integration capabilities and limitations of PowerApps and Flow. The second posts will show you how to do a bulk import of data from Dynamics CRM or Salesforce into the Common Data Service.
Power BI, PowerApps, and Flow are part of a major push to bring application development and integration to the hands of the ‘power user’ – allowing them to get done what would have in the past required programming skills, with each playing a specific role:
All of these can connect to various data sources such as Dynamics CRM, Salesforce, Excel, MailChimp…(full list for Flow here), but Microsoft is also providing the Common Data Service (CDS) as part of PowerApps to provide native database capabilities for the apps and BI.
The grand scheme that Microsoft is working towards looks like this:
The general idea is that enterprise users will be able to pull data from disparate sources into the database, and then rapidly develop apps and analytics to use this data. To quote Microsoft:
This data service adds powerful data storage and modeling capabilities to PowerApps. Our objective for the Common Data Service is to enable the following capabilities for the PowerApps, Microsoft Flow and Pro development communities:
- An easy to provision, yet scalable data store
- A common data model with standard entity schema and behavior
- A powerful data access layer with support for data import, export and security
- Integration with Microsoft Office for Excel and Outlook
The Common Data Model (CDM) database implemented by the CDS is a standardized set of entities and data types to ensure that apps are able to safely and reliably access data. The database is extensible – users will be able to add custom entities, but the standard fields in the standard entities cannot be modified. The objective is to ensure that PowerApps and PowerBI have a core set of entities and fields that can be relied on.
On a broader front there are indications that the CDM will form the basis of the Dynamics 365 platform going forward. Jukka Niiranen has an excellent blog postproviding quite a lot of context on the Dynamics 365 architecture and relationship with Azure.
At time of writing (November 2016), the only way to see a CDM database is to log into Power Apps and click the ‘Entities’ option in the side menu.This displays a list of the entities (aka tables) in the CDM database attached to your subscription. A detailed Entity Reference document is available, although at time of writing it does not accurately match the released database.
For a CRM user, the set of entities looks a little unusual – heavy ERP flavor, with multiple entities concerned with Purchase Orders, Sales Invoices, Sales Orders, Supplier Invoices etc. More unusual was the set of entities concerned with people in the August preview which had Contact, but also: Alumnus, Contractor, Customer, Donor, Employee, Family Member, Fan, Household Member, Team Member, Tenant. As Jukka Niiranen noted in another post:
OK, great, so I can store the name, address and Twitter handle of a physical person into 11 different entities now. I don’t recall ever wishing for such a possibility to exist, but it’s what’s coming at us now when Dynamics 365 arrives.
Thankfully, with the November release, this has been significantly rationalized, and a ‘Type’ field added to contact. We can expect the set of standard entites to evolve rapidly. Note that Microsoft is monitoring the way users customize the standard database and doubtless will incorporate some of the more popular ideas.
InaPlex is an integration specialist, so our particular interest is how to integrate with CDM. Currently there are two options for getting data into a CDM database:
Flow will be discussed in more detail in a later post, but for now note that the challenge with using Flow is that it is transactional – a Flow is defined as a connection between a data source and sink, and the the flow has to be triggered by some event. For example, you may set up a Flow that connects Dynamics CRM Companies and CDM Accounts. Each time a company is created in CRM the flow is triggered, and the company is created in CDM.
The problem with this approach is the initial data load. If you already have a few thousand companies in CRM, how do you get this data into the CDM database?
The only answer at the moment appears to be to import Excel spreadsheets. There are some tight constraints on how this can be done:
The easiest way of setting up the Excel spreadsheet initially is to do an export to a template from the CDM database. This gives you a work sheet with all the correct field names. You could also do a data export – this also provides an Excel worksheet with the field names, but additionally shows you how the data needs to appear.
Once the Excel file is populated here are the steps to import:
1. Select Entities, then Click the Import Data selection in the menu at top right.
2. Select the entity or entities you want to import into and click next.
3. Select the Excel file to be imported. The engine will load the file and check that matching (the Id field) and mapping (the column headers in the work sheet) are OK. If the field names in your work sheet do not match the field names in CDM, click the ‘Show Mapping’ link and select the correct mapping. Notice that the upload has selected the worksheet from the Excel file – you can have more than one work sheet for different entities.
4. Click import, and the Excel will be uploaded and imported.If there are errors, an error report in the form of an Excel file will be generated and can be downloaded.
Importing through Excel is relatively straightforward, if tedious. The bigger problem is getting the data into the Excel file in the correct format and ensuring you have data for all the required fields. For example:
Suppose you have a couple of thousand accounts and contacts in Dynamics CRM or Salesforce and you want the data in your local CDS database. You can drop the data into an Excel file, but then you have to manually reshape it, and if you do not rename all columns you will have to remap each time you do the import. And no, it will not work correctly first time…
With the launch date (1st November 2016), Microsoft unveiled the First look and shared more information regarding Dynamics 365, the next generation intelligent business apps in the cloud. Right now, there are obviously a lot of excitement, questions, confusions, concerns among existing customer and user base of the legacy On-premise applications (GP, SL, NAV & AX) as well as prospective customers and the partner community. All of us probably are wondering how our investments in Microsoft Dynamics is going to shape up in the new Dynamics Cloud era.
In this post today, let us understand and decode some of the key facts about Dynamics 365, that were unveiled and discussed in Summit 2016 held in Tampa, FL.
Microsoft unveiled the First Look of the next generation cloud business apps, all under one unified platform called Microsoft Dynamics 365. Below are some of the key take away from the first look.
Dynamics 365 For Sales: It is the Sales component/module of Dynamics CRM Online.
Dynamics 365 For Customer Service: It is the Customer Service/module component of Dynamics CRM Online.
Dynamics 365 For Field Service : This is the Field Service component/Module of Dynamics CRM Online.
Dynamics 365 For Project Service Automation: This is the Project Service component/module of Dynamics CRM Online.
Dynamics 365 For Marketing: Microsoft recently announced that it fully will integrate Adobe Marketing cloud with Dynamics 365 and make it the preferable marketing app for Dynamics 365.
Dynamics 365 For Operations: This is the New Dynamics AX (AX 7) ERP that we all are familiar with. This is where most of the customers/prospects might get confused. The name “Dynamics 365 For Operations” misleads a little bit. This business appis really targeted for the enterprise customers and obviously includes full advanced Financials functionality as well of AX 7. With this app, customers do NOT need to buy other Financials apps such as “Dynamics 365 for Financials”. “Dynamics 365 for Operations has everything you need to manage your Operations, including Core Financials. Hopefully, Microsoft will rename this app to “Dynamics 365 For Operations & Financials” at some point.
Dynamics 365 For Financials: This is the new Financials app of Dynamics 365(Earlier known as Project Madeira) and is primarily targeted for SMB customers in most cases. This does not include any of the advanced Operations functionality such as Manufacturing, E-commerce(Retail), advanced supply chain etc. When we say, this is targeted more for the SMB customers, we might argue whether Microsoft thinks that SMBs do not have “Operations” ? Of course, some of them do and Microsoft is probably thinking those customers should choose Dynamics 365 For Operations app instead of the Financials app. We will have to wait and see how this shapes up.
And Probably a new LOGO for Dynamics ? The Dynamics platform is most certainly getting a new logo which may look something like below.
Integration of Dynamics 365 and Office 365 Better than ever before. Traditional On-premise business apps (NAV, AX, SL etc) always had integrations with Office 365 and could exchange data with Microsoft word, excel outlook. But the scenarios and capabilities were somewhat limited. With Dynamics 365, the integration goes to a whole new level and provides users a full-blown integration. For example, you can drill into the details of a customer record of Dynamics 365 from within your Outlook email and even see further details such as associated sales opportunities, and launch the Dynamics 365 for Sales app/Other apps from within the email. Sleek !! A lot to explore and learn.
Question: Do customers need to pay to use this Service ? I do not know and we will need to wait and watch.
Long story short, customers using AX 2009 can start evaluating their upgrade options with assisted upgrade tool for AX 2009. These tools are in preview now and when released, it will have the capabilities to do the heavy lifting for you for the upgrade. I assume, while the tool can help these customers to a great deal, there will still be a good amount of work that needs to be done to make these upgrades successful.
For Customers using AX 2012, the upgrade path will be comparatively easier given the fact that schema and underlying business logic of AX 2012 and AX 7 are pretty much same. The upgrade assisting tools for AX 2012 may be available around March of 2017. Need to wait and watch.
Hope this was a good summary of Dynamics 365 announcements at Summit this year. We all havea long way to go and learn the cool new features and services and be ready to sail through the cloud era.
When Microsoft Dynamics 365 was announced a few weeks ago, the Common Data Model and other Microsoft productivity services such as PowerApps and Microsoft Flow were a significant part of this, along with the unified offering of Dynamics CRM and Dynamics ERP cloud services under this umbrella. The solution stack diagram below for Dynamics 365 depicts the positioning of these various elements in Dynamics 365.
The Common Data Model is now available, let us try to make sense of these together and see what are the possibilities using the CDM and Microsoft PowerApps.
In today’s post, we will create a simple example mobile app using Microsoft PowerApps and the Common Data Model database.
Log in to Microsoft PowerApps at the URL https://powerapps.microsoft.com. You can use the PowerApps web version to create your apps. But the best way to do this is to download the app from Windows store .
In this post, I will use the windows store app to create this sample mobile app.
Launch PowerApps and click New tab to select the data source. While you can use various data sources such as Dynamics CRM online, excel file stored in the cloud, online storage such as OneDrive or Google Drive, in this case we will use the Common Data Model as the data source for this app.
On the next screen, select the entity that you want to use in this app and click Connect button. For this sample app, we will use the Sales Order entity and build a simple app to interact with Sales orders (Simple actions such as view sales orders, edit or even create a new order).
At this point, PowerApps will consume the Sales Order entity data and create the sample app with some default screens automatically, which you can adjust and change to make it look the way you want it. The auto creation feature comes in handy, as you do not need to create the app from scratch.
Now that the default screens of the app are created, let us try to edit those a little bit to make them look more complete. The first screen is a Sales Order overview screen that shows the list of sales orders.
Below screenshot shows how this mobile app looked on my smartphone after I shared it and launched it on my Android phone.
This was just a very simple demonstration of the possibilities and what you can do with the Common Data Model and productivity tools such as PowerApps or Microsoft flow. The CDM is in preview now, but when it releases this fall, you will see a lot more data entities and much more capabilities of designing powerful business apps in the cloud for your organization.
That is it for today’s post and I will share more as details emerge and as I learn more.. Hope you all will keep exploring more on this. Till next time!!
Most of us must have heard a lot and read a number of blog posts already about the newest member of the Microsoft Dynamics family, “Dynamics 365“. Those who followed the WPC updates on the web or those attended the event in Toronto this year must already know a lot of details of this by now.
This is the first blog post on my new blog which will be dedicated and tailored for Microsoft Dynamics 365 going forward. In this first post, we will summarize some of the key aspects of Dynamics 365 that you need to know for now.
Microsoft Dynamics 365 is the next generation of business apps in the cloud from Microsoft. It is intended to bring together the best of Dynamics ERP and Dynamics CRM, cloud offerings into one consolidated cloud service. In other words, it is a new umbrella which will consolidate the Microsoft CRM and ERP cloud applications and provide specific purpose built apps for each of your business areas (Both for SMB and Enterprise Customers) along with the best of Microsoft Productivity apps (Office 365) and Business Intelligence/Analytics, IoT and power of Azure.
In more technical terms, Dynamics 365 aims at providing a new consistent application platform and a common data model with several standard business entities and that partners can leverage to build innovative business process and industry specific solutions using Dynamics 365, office 365, Power BI, Microsoft flow, Power Apps and more. The benefit that customers will get out this is, their users will not have to switch or change between multiple applications and still get everything (Data, Process), all at one place.
As depicted in the above solution stack diagram, you can clearly see that Dynamics 365 is fully a cloud only solution and is built on the Microsoft Azure stack. Dynamics 365 will provide a new application platform and common data model which will span across other cloud apps like Microsoft PowerApps, Power BI, Microsoft Flow etc., along with Office 365.
Two of the major components in this solution stack are the CRM and Finance/Operations. Dynamics CRM will primarily cater Sales & Marketing, Customer Service aspects. Optionally Field Service as well as Project Service (Professional Service Automation) can also be used by customers.
For the Financials and Operations area, the New Dynamics AX (AX 7) will be the backbone for the Enterprise edition of Dynamics 365 which is targeted for the Enterprise customers. Project Madeira (Code name) will be the backbone for the Business Edition of Dynamics 365, which is targeted for the SMB customers.
Power BI and Cortona Analytics Suite (Which are widely used applications already) will be the business intelligence platform for Dynamics 365.
Finally, there will be third party business applications extensions/add-on solutions by partners for industry specific solutions or functionality enhancements. These apps will be available for consumption in an entirely new platform called “App Source”. We will debrief App Source further in the post below.
As of the revealing so far, Dynamics 365 will be available in 2 editions. (This information is subjected to change when Dynamics 365 releases this fall)
The Enterprise edition is targeted for Enterprise customers and will come with full blown Dynamics CRM and Dynamics AX will be the ERP for operation. The Business edition is targeted for SMB customers and it will have a future sales and marketing solution (May be a lightweight Dynamics CRM online ?) with Project Madeira for financials.
Even though solid information about this is not yet available, the future licensing model is pretty obvious. Apps, Plans and Team members will be the new building blocks of Dynamics 365 licensing.
Refer the post at the URL below to know more on what Microsoft revealed at WPC 2016 about this.
App Source is the new “app store” where business customers and prospects can find and buy solutions for any of the Microsoft technologies. This is the platform for Partners to publish their industry specific solutions for Microsoft Dynamics AX, Project Madeira, office 365, Power BI etc.
As an example, you can see AXIO For Professional Services, an ERP solution powered by Dynamics AX and is tailored and built for Professional Services firm.
Details of pricing are not yet fully available, but customers will have better flexibility for pricing for sure. They will be able to buy in the traditional approach where they can license Dynamics 365 by application (Operations, Sales, Field Service etc.). They will also be to license Dynamics 365 by user role.
You can see some additional details on the blog post at URL below.
Stay tuned for more details.
Even though there is no solid information on this yet, I guess it may be during the OCT – NOV 2016 time frame. Stay tuned for more updates on this soon.
For customers who are already using Dynamics CRM online and the New Dynamics AX, Microsoft says it should be a seamless transition. For customers on earlier versions, there will need to be a transition path. I am not very clear on the complete transition path right now, but more details to follow as details emerges.
Dynamics 365 is a cloud service and will not be available on premise. Microsoft will continue to innovate and support the on premise Dynamics CRM, AX, NAV, SL solutions and may offer connectors if any customers want to use a hybrid of on premise and some of the cloud solutions. You can find more on what the engineering leads have to say about this at the blog post below.
I’ve been in the technology sector for years and have seen many dramatic…and some not so dramatic…milestones in the evolution of business software. IoT (Internet of Things), BYOD (Bring Your Own Device), App Stores, the consumerization of technology, mobile adoption, virtual reality, big data analytics and of course, the almighty cloud. And these are just a smattering of the major turning points in business technology over the last decade.
Most wouldn’t classify the evolution of Dynamics to Dynamics 365 to be on scale with virtual reality or IoT, but I find myself wondering if they’re just not looking closely enough.
The real value is not just in how it is being offered (the cloud) but in the depth of the offering itself. Bundling Office with ERP and CRM is great, and creating a common data model is great. But, when they added in Microsoft Flow, PowerApps, PowerBI and a focus on “power users” over traditional developers, you start to see something much more pivotal.
A Power User (also known as a Super User) is an end user expert with a more advanced grasp of a specific software solution than regular users, but not someone who makes their living as a technology consultant. For example, an accounting manager for a company using Dynamics 365 may have learned the ins and outs of the software through the normal course of business. Not necessarily a Power User. The Power User is someone with a taste for technology that takes a basic knowledge of a solution and runs with it. They begin to learn about related technologies and delve into the “why it works this way” and “how it works this way.” Over time, their penchant for a solution (or tech in general) becomes a defining factor in their career as employers begin to depend on them as internal experts.
As discussed in previous posts, the introduction of CDM (common data model) for Dynamics 365 has opened many doors for businesses that choose to invest in the Microsoft Dynamics platform. Although interoperability between products has always been possible, it was often just not cost-effective. Workarounds and third-party solutions were the preferred methods for swapping, sharing and collaborating. Now, Microsoft has introduced three new options to take advantage of the newfound interoperability and “empower the power user.”
PowerApps allows business users to easily create mobile apps for iOS (and soon Android and Windows) that can consume data from and insert into many of the systems you already use. For example, you might want to deploy an app that allows remote or mobile employees to add leads into Dynamics CRM from their phone. Or, a streamlined form your social team can use to post to multiple social networks simultaneously. With PowerApps, this can be accomplished without coding using an intuitive point and click, designer.
Other out of the box data sources, which can also be used to populate form fields (such as drop down lists) include Salesforce, Excel, Slack, Twilio, and Mail Chimp. If the data source or service you want to connect with doesn’t exist, then you can still connect to a custom API with relatively little effort.
Microsoft Flow works alongside PowerApps to provide even greater usability and access to Dynamics 365. With Microsoft Flow, you can automate almost any time-consuming process or task. From simple tasks such as emailing a group when a new inquiry is made from a website to much more complex workflows like as capturing, tracking and following up on leads.
Creating with PowerApps and Microsoft Flow doesn’t require an advanced IT degree or extensive knowledge of programming. Power Users can learn to create solutions using online training tools and intuition. Some challenges are harder than others, so formal developers will always have a role in extending solutions, but the ceiling has most definitely been lowered. As these technologies mature, premium services will often be reserved for the more complex projects while Power Users will often find what they need by browsing Microsoft AppSource and loading add-ons themselves or building them outright.
Technology and business professional services firms, like Dynamics VARs, will need to step up their game. Implementations will continue to get easier as the cloud picks up the heavy lifting. Automated configuration and online tools will also easy the challenge of tailoring solutions to the needs of individual companies. Customers will still depend on outsourced technology relationships to assist with implementation, but their impact will be defined by: