Microsoft Dynamics 365 is designed to support the sales process from acquiring a new lead through the close of a sale. CRM has a place to store the contact information for new leads, a place to track the follow-up communications (such as Phone Calls, Emails, and Appointments), and the ability to qualify a Lead into an Account, Contact, and Opportunity.

• Terminologies:

   

1. Account: Organization; Includes Customer, Vendor, Partner, Affiliate or Other.
2. Contacts: Individual; Associated with maximum one account (through contact form).
3. Leads: Prospect (Potential Customer/ Potential Sale).
4. Opportunities: Potential Sale (Created when lead is almost ready to buy product or service).
5. Quote: Document for customer/prospect; Contains information about Product, Quantity, Pricing, Payment terms and other important details.
6. Order: Confirmation from customer/ prospect on buying a product.
7. Invoices: Document containing billing information.
8. Competitors: Information about competitors. So that you can keep track of them and win.
9. Sales literature: Centralized repository for sales related documents. Contains Brochures, Product Guides, Competitors information, Pricing and Discounts, Sales documents, etc.
10. Product Catalog: Collection of Products and their pricing information.
11. Goals: Used to keep track of progress on achieving target revenue.
12. Goal Metrics: Explains how the goal number or figure I measured.

     

• Process Flow:

Step 1: Capture Lead – Create Lead.

Step 2: Account Creation – Information captured of a company or company details become Account after lead qualification process.

Step 3: Contact Setup – Information captured of an individual in a lead becomes Contact after lead qualification process.

Step 4: Opportunity management – Once Lead shows interest in product and ask for more information Qualify the lead. Now the Lead becomes an Opportunity.

Step 5: Product Catalog – Add all the information about products and their pricing.

Step 6: Quote Management – Create Sales Quote.

Step 7: Order Management – Once the customer accepts everything mentioned in Sales Quote and confirms, convert quote to order.

Step 8: Close Opportunity.

Step 9: Invoice Management – Create Sales Invoice and send it to the customer.

Step 10: Sales Business Process – Business can define a process flow so that sales user will follow the guided process without any confusion.

The post Microsoft dynamics CRM tutorial for beginner – Sales Module Process Flow || 2023 latest Sales module appeared first on Microsoft Dynamics 365 Blog.

Click here if your file in SharePoint doesn’t load or corrupted.

Click here for How to Enable Dynamics 365 CRM and SharePoint Integration Step by Step

This question has been going around on the power users community forums and I thought it would be nice to blog it because it is always gets tricky trying to save files from different data sources , so for this we have a single source the outlook connector and there is two destination.

1. Sharepoint File
2. Dataverse Email Attachment

Lets Get Started!

So the starting point is the Flow Trigger which is “When a new email arrives (v3)”

Then the next step is to get the Attachments from the Email by using the below steps:

1. Loop on the attachments from the triggerOutputs
2. Use Get Attachment (v2) to get each attachment

Then to save to sharepoint that was pretty easy .. Just using the outputs of the Get Attachments (V2) has worked from the first Go!

Name and Content Bytes!

What about dataverse?

So for DataVerse we are creating a new email activity and adding the attachments to it as below but it wasn’t straight forward adding the attachment.

Step 1: Easy : Create the Email Activity

Step2: Add the Attachment and here is a couple of tricks

1. when you select the table name attachments there is 2 tables , make sure you select first one.
2. Attachment(Attachments) just pass null from the Expressions Pane … Weird but how this is working.
3. Entity: Do not select one of the available Options , just use enter a custom value and type email otherwise you will get an error.

The entity with a name = ‘4200’ with namemapping = ‘Logical’ was not found in the MetadataCache. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=3040485, MinActiveRowVersion=3040485, MetadataInstanceId=51707140, LastUpdated=2021-08-04 11:35:57.770

And when it came to setting the body ; it wasn’t as easy as passing the content bytes directly as with sharepoint ..

Attempt 1: Pass Content Bytes directly .. Error Received

The attachment body should be a valid Base 64 string

Attempt 2: Convert Content Bytes to base 64, No error received, file was attached but corrupted

Attempt 3: Binary ???!!! .. Weird but this is what worked for me run successfully and file was not corrupted.

Hope this is useful!

The post Move Attachments Note or email to SharePoint using Power automate flow Dataverse Microsoft Dynamics CE | CRM appeared first on Microsoft Dynamics 365 Blog.

formContext.data.save(saveOptions).then(successCallback, errorCallback);

 formContext.data.save().then(function() { alert("Successfully Saved "); }, function() { alert("Something Went Wrong"); });

The post Best Way to use Force Save JavaScript client API in Microsoft dynamics CRM appeared first on Microsoft Dynamics 365 Blog.

The post Get AppID of Dynamics 365 Crm App in power Automate – UCI appeared first on Microsoft Dynamics 365 Blog.

Even selecting Sales only while creating Trail , We get Trail Field Service and Project Service Automation Solutions,
and for specific purpose like converting trail to sandbox or production
we might need to remove these extra solution and it important to know in what order to uninstall solution

Below are the order in which we need to delete Solutions for field service, I am not including uninstall of IOT component

• FieldServiceTrial
• FieldServiceGeofencing
• Geofencing_patch
• Geofencing
• ConnectedFieldService
• FieldService_Patch
• FieldServiceHealth
• Remove component from model driven app if any
• FieldService

Remember there might be some patches for each individual , 1st uninstall patch

1. Click on the solution and then Delete

The post How to uninstall / remove Field Service from Dynamics 365 CRM Trail appeared first on Microsoft Dynamics 365 Blog.

This post is on how to add a trigger condition and how are the expression used as TriggerBody()

We will divide the example into below points, As by name itself it states Flow will only run when the trigger condition is matched
EXAMPLE:  We want the flow to trigger only when case status = 2 where our flow trigger is “When a record  is created”

1. Trigger flow on condition of OptionSet Value, option Label or Boolean field
2. Trigger flow on condition of Lookup name, GUID, Type or Customer Type
3. Trigger flow on the condition to check contains the operation
4. Trigger flow on condition to check GreaterOrEqual, LessOrEqual
5. Trigger condition “OR” “AND” Logical Operators example
6. Troubleshot: check TriggerBody() Body with fields and Values

Troubleshot: check TriggerBody() Body with fields and Values

• There were chances with OOB entities like Ai builder or Forms pro which have some background workflow on create or update  and we might be putting a condition where value might not be in BODY of triggerbody()
• We can check and successful or failed history for body content

The post Trigger condition expression example for each field Datatype in Power Automate appeared first on Microsoft Dynamics 365 Blog.

Omni Channel for Customer Service is a new offering from Microsoft that sits on top of the existing Microsoft Dynamics 365 platform. As the name suggests the new robust platform is specifically built for the Customer Service agents, supervisors and administrators to handle Customers across different channels at the same time.

As of today the platform supports various channels such as Chat, SMS, Facebook, Twitter, etc. The platform also be extended to support System and Custom entities. Currently WhatsApp, Microsoft Teams and integration with other Custom channels is still in preview mode.

Queues and Users –

• The platform allows administrators to configure different types of queues based on skills, specializations, shifts, etc.
• Administrators can also configure existing Dynamics 365 users as Omni Channel users and different their key attributes such as Capacity.
• Chat BOTS configured using Microsoft Power Virtual Agent are also available that can be used for internal consultation or as first point of contact for Customer interaction.

Work Distribution is a concept of Omni Channel for Customer Service that ensures conversations are routed effectively to relevant agents based on their availability and skills.

The post Introduction to Microsoft Omni Channel for Customer Service appeared first on Microsoft Dynamics 365 Blog.