Menu Close

Blog

Slide 1
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
Slide 2
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
Slide 3
UK365GUY

Microsoft Business Applications Blogposts, YouTube Videos and Podcasts

Helping Businesses with Technology

Subscribe
previous arrow
next arrow

Microsoft Dynamics 365 Processes

uk365guy

Microsoft Dynamics 365 Customer Engagement Processes:

From within PowerApps (Dynamics 365) you can leverage five different process types for specific needs and use cases. Each of the process types contain help to support a very specific type need that a customer may have.

Business Process Flows: Represent business processes that can potentially span multiple Dynamics 365 entities.

For example: An organizations sales process may start with the lead entity, and conclude with creating an Order in the application.

Task Flows: Assist in the automation of potentially repetitive tasks that users may execute in the application. These tasks may potentially need to touch multiple entities in the application.
For Example: After a sales meeting a user can run a Task Flow that updates the Appointment, and the Contact record at the same time.

Workflows: Automations that can run in the background or as part of a user invoked action and provide real-time feedback to end users.

For Example: After a CSR completes and closes a Case for a customer, a Workflow automatically send an e-mail to the customer that contains a link to a survey they can complete.
Actions: Allow transactional custom API calls such as “Escalate Case” or “Sent PotHole Report”. They can be executed by Workflow Actions.

Microsoft Flow: Automation tool that provides the ability to define workflows that can span multiple Line of Business Applications.

For Example: Microsoft Flow could monitor a Document Library in SharePoint. After a Document that contains specific information is added to the Library, Microsoft Flow could create a record automatically in Dynamics 365.

How they Fit into Customizing Dynamics 365

As you are customizing Dynamics 365, you encounter specific situations one or more of the previously mentioned process may be beneficial to your organization. Although each specific situation is often unique, there are specific situations where each type of process could be leveraged.

I hope this helps.

For Microsoft Dynamics 365 Consultancy/Training/Support/Licensing
Contact us: www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 Manual N:N Relationship

uk365guy

Hi Everyone,
Today i am going to explain how N:N relationship works in Microsoft Dynamics 365.
Lets gets started.
A manual many-to-many (N:N) relationship is not a true type of relationship, and will not appear in the N:N relationships node for an entity. It is a convenient way to describe how you can use a custom entity that has two lookup fields for the 1:N relationships to the two entities that you want to connect. This is known as a manual many-to-many (N:N) relationship because you create a custom entity instead of having the system create and maintain a hidden intersect entity.
The main benefit of creating a many-to-many (N:N) relationship in this way is that you can add custom fields to the intersect entity. In a native many-to-many (N:N) relationship, the intersect entity is hidden and custom fields cannot be added.
When you decide on the type of many-to-many (N:N) relationship to create, you have to know whether the organization must record additional information about the intersect entity.

In example, the native many-to-many relationship provided the required functionality that let multiple Contacts attend an Event, and a Contact attend multiple Events. However, because the intersect entity cannot be customized, additional details of a Contact’s attendance cannot be recorded, such as the following:

·         Contact’s registration status
·         User who recorded the registration information
·         When the contact registered to attend the event
·         If the contact has any specific requirements, such as accessibility or dietary requirements
If you have to store this additional information, you must create a manual many-to-many relationship. For example, in this scenario, create a custom entity that is named “Booking,” and then add fields to the Booking entity to record the additional data that is required. Then, from the Booking entity, create the following two 1:N relationships:
·         From Booking to Contact
·         From Booking to Event
By using the Booking entity as an intersect entity, the organization can track registration information that is related to both Events and Contacts, and still let multiple Contacts attend an Event, and a Contact attend multiple Events. When you create two 1:N relationships from the same entity in this manner, this can be described as a manual N:N relationship.
I hope this helps.
Contact us:
For Microsoft Dynamics 365 Training/Consultancy/Support/Licensing
Contact us: www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 for Marketing – Dynamic Segment Designer

uk365guy
Hi Everyone,

Welcome to part 2 of my preparation for dynamics 365 for Marketing.

Today i am reviewing Dynamics Segment Designer:

Dynamics Segment Designer: 
The designer tab is used to define sets of logical rules and conditions that filter out contacts in order to narrow down the audience. When working with Dynamic Segments , a secondary set of tabs will appear.
Designer, Flow and Query.

we can build complex queries with  AND or OR and group of additional clauses we can combine with the main clause and other segments by using Union, Exclude, or Intersect operations.

The Options used under the Add Group section are applied as the parent logic when used on a corner journey.

Union
Exclude
Intersect

Flow and Query Tabs
The Flow tab provides a visual representation of the entities and relationships the segment is utilizing. You can use the fields to the right to build onto the segment you may have started in the Designer tab.​
​
The Query tab is for those used to working with database queries in which the logic is written manually. ​
​
We can navigate, build and edit the same segment within all three of the Designer, Flow and Query tabs.​

Share this:

Microsoft Dynamics 365 for Marketing

uk365guy
Hi Everyone,

As i am preparing for Microsoft Dynamics 365 for Marketing certification, hence the below notes.

Follow my blog through out my preparation, you might benefit with this notes in clearing certification:

Microsoft Dynamics 365 for Marketing main features:

Segments and List Management
Marketing Pages
Lead Management
Email Marketing
Customer Journey
Event Management
Survey Management

Microsoft Dynamics 365 for Marketing Capabilities:
Muli channel campaigns: Eail Marketing, Marketing pages & forms,
Webniar’s, phone calls & in-person events, LinkedIn connector

Lead Nurturing: Campaign designer, 360 degree view, Behavior based lead nurture, Lead prioritization.

Embedded Intelligence: Multiple lead scoring, Dynamic segmentation, customer Insights, Notifications

Event Management: Webniar’s using ON24 , Events Portal, Attendance tracking, Speaker management

Reporting: Dashboards, Surveys, Embedded PowerBI, Configurable.

Marketing campaigns are most effective when they are targeted at a group of individuals who have a higher level of interest in the subject matter of the campaign. As such, it makes sense to strategically divide contacts with like-minded interests or based on key data points into groups – or segments – that can then be leveraged to more effectively target a campaign to the appropriate audience.​
​
Dynamics 365 for Marketing uses segments in two important ways: ​

Customer journeys: Most customer journeys start with a segment tile, which establishes the collection of contacts that will experience the customer journey. You can combine multiple segments in a journey.

Subscription lists: Subscription lists are static lists that contacts then add themselves to (or remove themselves from) using a subscription center. ​

Dynamics 365 for Marketing fully supports segmentation using the Segment entity, with these records primarily being used when architecting customer journeys or in relation to subscription lists. There are three types of segment records that can be created:​

Dynamic Segment: As the name implies, a dynamic segment is a group of contacts built from a defined expression or query.​

Static Segment: If contacts cannot be logically grouped using a query, then a static segment can also be used. Contacts can be selectively added to a static segment on a per-contact basis. Static segments are usually based on Marketing Lists so contacts can opt-in or opt-out of static segments by using a Subscription Center. These features are described later in this module.​

Compound Segment: This type of segment combines the virtues of both dynamic and static segments. Contacts can be added using an expression or query, or they can be selectively added.​

Dynamics 365 for Marketing works together with another product called Dynamics 365 for Customer Insights to provide advanced segment definitions and customer analytics. The integration is seamless and results in powerful combined functionality when the two systems work together. As your contact records and marketing lists are continuously synchronized, Customer Insights apply its powerful data processing and analytical tools to your contacts, along with information from other types of Dynamics 365 records and systems.

You can access Customer Insights directly to make use of its additional analytical tools and features. ​

I hope this helps:

For Microsoft Dynamics 365 Training/Consultancy/Support/Licensing
Contact us: www.gmritsolutions.co.uk
Email: admin@gmritsolutions.co.uk

Share this:

Microsoft Dynamics 365 Training

uk365guy
Hi Everyone,

I am happy to share about our Company  GMR IT SOLUTIONS LIMITED  has been  successfully delivering

Microsoft Dynamics 365 Training for customers SMB’S , SME’s, Corporate Customers and End Client’s across United Kingdom.

Dynamics 365 Customer Engagement
{Customer Service, Sales, Marketing}
Customizations,Solutions,Integration,Relationships, Web Resources, process,Plugin,Business Rules, Workflow, Dashboards and Charts, Report.
Power BI
Connecting With Data,Query Editor, Data Models, Data Visualizations,DAX,Reports and Dashboard.
Voice of customer: 
Installation and Configuration, Plan Survey, Design and Distribute Survey, Design an Advance survey, Analyze survey data
Project Service Automation:
Opportunity Management, Project Planning, Resource Management, Team Collaboration, Time and Expenses, Customer Billing, Service Analytics
Field Service:
Setup and Configure Field Service, Manage Work Order, Schedule and dispatch work orders, Manage Field service mobility , manage inventory and purchasing, manage the connected field service solutions, manage agreements.
Portals:
Create and design Portals,Manage and configure Portals, Manage and Customize Content.
Unified Service Desk:
Installation, Create Hosted Connection, Toolbar, Search function, session Lines, Association View
Gamification:
Configuration and Setup, Activation , Manage KPI Run Games, gamification Setting, Point Scoring, Schedule emails, Weekly awards, Configure stream tv.
Azure
Introduction and Overview, Building Application, Infrastructure,Strong, Data, Securing Azure Applications.
Talent: Onboard, HR and Core HR.
Business Central:
Finance and Operations:

Organisations looking for trainers
Get in touch:

www.gmritsolutions.co.uk
Email: Admin@gmritsolutions.co.uk

Share this: