Sweet, sharing Power Apps to Azure AD Groups.
Another reason to continue to emphasize using Azure AD Groups.
A great time was had by all at the Power Platform Seattle Q4 User Group meeting. Interesting insights on UCI what's new and a nice presentation on all things marketing module.
My clearing the confusion comment of the day, Dynamics 365 is A Power App.
Kicking it up a notch plowing through the mud, soaking up the richness of the dirt.
A new blog post has been added into the world of buzz: IT starts like this and you can follow the link to read even more
"The Microsoft product teams have finalized a huge list of new wonderful features for the Microsoft Dynamics 365 Business Applications stack.
James Phillips, corporate vice president of business applications and one of the most authentic stage presenters there can be, prepared and presented part of the October 2019 Business Applications Virtual Launch.. You can watch the virtual launch event presentation for free, but they do ask that you register so............"
If you have not heard about PowerApps, Microsoft Flow, the Common Data Model (CDM) and Common Data Service (CDS) then it is time for a bit of reading. Imagine an explosion within the world of Microsoft Technology where the entire Microsoft Stack of Applications become your tool set. OH Wait, the explosion continues and pulls in 100s of other non-Microsoft applications as well.
Now you get it.
What adds an interesting twist is this concept of "No Code" so business users can now put together building blocks to deliver their own mobile applications without having to jump into the world of GitHub or Visual Studio or pick your language of choice.
Developers, don't freak out, you are still loved and needed.
The grey area becomes the space where a relatively simple business user story, is not necessarily easy from a PowerApps or Microsoft Flow delivery. This is where understanding the fits and gaps is important.
Fits - Everything can be done with no code.
Gaps - Everything can be done with no code or low code
Big Gaps - Everything can be done with no code, low code and an extension.
So what does this really mean?
One of the huge shifts and benefits for a sales person is when technology gets aligned so that keeping data current falls to the most logical location. Consider for instances a prospects name, company and job title. A shift is when this information is kept current by that specific prospect rather than the sales person following that prospect. The prospect updates their name, role and company information because it is beneficial to the work that they are doing. The sales person who has a relationship with this person, or who is following them, can then be a straight consumer of data managed by a logical source.
Now this isn't perfect .. not everyone updates their information even with the power of a product such as LinkedIn and Sales Navigator so technology still needs to take another step in validating that the data is current. A futuristic option on this will be when AI technologies can tap into larger or the largest data repositories and filter out what they need to validate a person's name, role and company. If we take this one step further we add address, telephone numbers, historical information.
Data exists, we can purchase this data, but we are not quite to the point where the data on a person is 100% transparent when we need it AND there are many reasons why this also sends chills up many a spine.
If we circle back to what is happening in the world of Microsoft Dynamics 365 for Sales we find that Relationship Sales is a combination of the knowledge within LinkedIn and the Power of the Dynamics 365 platform.
Unifying the best of both worlds to further empower the business sales teams. It also uses AI Technology in addition to the combination of data. This takes this one step further.
Posted at 06:24 PM in Azure, Dynamics 365 in Enterprise , Dynamics 365 in Small and Midsize, Module: Sales, MSDYN365CE v9, Power Platform, PowerApps, Usability and User Resources | Permalink | Comments (0)
Tags: CRM, Customer Engagement, Dynamics, Dynamics 365 for Sales, Microsoft, Relationship Management, Relationship sales, The Future of Selling
Definition: "Azure Logic Apps gives you pre-built components to connect to hundreds of services." Reference Logic Apps can be used to automate business process and to schedule key steps within processes to occur at key times or when certain conditions are met.
Logic Apps can combine predefined existing services or components or they allow you to create your own components or services.
Logic Apps work with "Connectors". A connector uses the external service's REST or SOAP API to connect components or services. For instance a connector can call a service's underlying API. There are existing connectors such as a Twitter Connector or a D365 Connector and custom connectors can be created.
Why would Logic Apps be considered in the world of D365 Online?
Take for instance the need to batch process data within a time frame such as every day at 4pm process data from System A, clean the data and push it into a D365 Online Instance. In this particular example Logic Apps can be used to bridge the need to schedule a process from an external system into D365.
There are many other examples as well.
You also have the ability to work with TRIGGERS and ACTIONS within the world of Logic Apps.
"A trigger is an event that occurs when a specific set of conditions is satisfied. Triggers activate automatically when conditions are met. For example, when a timer expires or data becomes available.
An action is an operation that executes a task in your business process. Actions run when a trigger activates or another action completes." Reference
Defining Triggers and actions and creating your Logic App is all done within the Logic Apps Designer. A graphical tool for creating your Logic Apps workflows.
Logic Apps are not always the answer, but are one of the many choices in the world of Microsoft Azure and Microsoft Dynamics 365 for Customer Engagement. Take a minute to read up on Logic Apps using the reference links above. Also for a quick peek into when to use Logic Apps, here is the decision tree. Reference
Companies that sell complex products often include detailed spec sheets for their products. These spec sheets will many times include pictures, tiny type, videos, specifications and pop out messages. This type of format is not always the easiest to translate into text within a database. Shift your thinking ..
In the world of Microsoft Dynamics 365 for Sales you have some interesting options. Take for instance the Office 365 integration to OneNote. A OneNote page can align to a product in the product catalog. OneNote easily allows you to capture the specs, add pictures, include URLs and more.
Just paste in the Specs
You have heard all the buzz on the new Power Platform and you have seen many posts on PowerApps/Model-driven Apps and Canvas Apps. You have also upgraded your Microsoft Dynamics 365 CRM instance to v9.x either On-Premise or Online, but you are not sure where to get started with apps!
This might be an interesting path:
1) If you are familiar with configuring Microsoft Dynamics 365 for CRM/CE then you might want to start by adding a Model-driven app to your one of your solution files.
A Model-driven app can be used in conjunction with what you are doing today (the classic menu) and there are some nice little short cuts to getting started. For instance you can create a Model-driven app using your current sitemap and/or a current solution file.
2) Once you get the hang of creating Model-driven apps (and there are some small little tricks) then perhaps it is time to dive into creating your first Canvas App. One of the differences between a Canvas App and a Model-driven app is that Canvas Apps tend to be focused on the Microsoft Stack first (think Microsoft 365) and Model-driven apps tend to be focused from a Dynamics 365 perspective (Think an app within a solution).
If you are empowered from learning online, you can get some nice step by step materials by working through some of the exercises on Microsoft Learning!
If you prefer an in person type learning environment then you might want to attend the Business Applications Summit in Atlanta on June 10-11th or attend one of the App in a Day seminars in a city near you.
Now that we are running in larger data centers with the power of Microsoft Azure and with hardware technology such as solid state storage (moving away from the limitations of rotating platters) we all want to take a deep breath and make a sigh of performance joy.
Unfortunately when you eliminate one bottleneck the data moves to the next. Additionally bottlenecks are not just hardware.
Consider a rock wall layered in a stream of water, you remove the rocks blocking the water, and the water rushes to the next barrier. The same concept applies to data.
If you are working with millions or hundreds of thousands of data records you might want to consider:
What are your favorite tips and tricks for performance?
Oh and as a last note .. there are customers processing 100,000s of data records a DAY with the Microsoft Dynamics platform. The power is incredible with a little love.
Posted at 07:04 AM in Configuration/Customization , Dynamics 365 in Enterprise , MSDYN365CE v9, MSDYNCRM04, MSDYNCRM11 v5, MSDYNCRM13 v6, MSDYNCRM15 v7, MSDYNCRM16 v8, Partner Resources, Power Platform, Tips and FAQs | Permalink | Comments (0)
Tags: dyn365, dyn365ce, dynamics, Microsoft., performance, SQL Server
The power of the user group is that listening to peers, experts, partners, consultants, business users, financial advisors and so many more, opens the mind to interesting ideas.
CRM USER GROUP - FOCUS - in HOUSTON
9:49am and here are the first few tips
1) Have you considered holding your sales team to task by using SLAs on LEADS, measuring when the lead was first contacted or when a lead reached a key milestone in the qualification stage?
2) GOALS, so under appreciated and yet so powerful. Add goals in unique and creative ways to take full advantage of the complex hierarchy offered from this little feature.
3) Task Flows : Originally for Mobile Only, but now embedded across the new UI. Take for instance OOB Follow-up to a meeting. A sexy dialog.
4) DOCK your business process flow on the right side of your form so you can see the fields. Always learning, this is a cool one, although I thought a TAB approach might be useful as well. Some people like that old style form view.
5) Did you know you can use an Out of the Box action to move a business process flow to the next stage automatically (so your user doesn't have to press next)?
6) Has your partner added an APP or APPS to your configuration? If not, you are missing out.