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.

STEP 1: Enable SharePoint integration:

1. Go to Apps.
2. Select your portal –> Click on more commands(…) –> Click on Settings

3. Click on “Administration“

4. Go to Setup SharePoint Integration and click on “Enable SharePoint Integration“

5. Click on Enable button it will then ask you to sign in again.

6. Click on Accept to grant the required permissions.

7.  You will get the below message.

STEP 2: Enable document management for table(entity)

NOTE: If document management is not enabled already then follow below steps.

1. Go to Settings –> Document Management –> Document Management Settings

2. Select table

2. Click on Next
3. Click on OK

4. Click on Finish.

STEP 3: Customizing Form

1. Add Document Location subgrid in the form .(The form which you are using in the PowerApps portal)

2. Save and Publish your customization.

STEP 4: Creating and Assigning Table(Entity) Permissions.

1. I am enabling SharePoint Documents for the “Project” table so I have to create two table(entity) permission records one for Project and one for Document Location.

a. Table permission for the Project table. (Don’t forget to add web roles to the table permission)

b. Table permission for Document Location.

Table Name: Document Location

Scope: Parent (This will make sure the user can only see documents that are related to the record)

Parent Table Permission: Select table permission of project from lookup.

Privileges: Read,Create,Write,Append,Append To

Go to Portal, You should able to upload files now.

1. Open any Project record in Portal.
2. You should see the Document Section below from where you can “Add files” or Create “New folder” in SharePoint.

3. Click on the “Add files” button you are shown a pop-up window from where you can choose the files to upload.

4. You can see the New Folder is created in SharePoint for that Particular Project and file is also uploaded inside the respective folder.

5. Click on “New Folder” to create new folder this will get created inside the parent folder in SharePoint.

6. From the portal, you can go inside the folder and then upload files that get uploaded inside the respective folder in SharePoint.

• “Add Files” in newly created folder.

• New Folder and Files in SharePoint.

The post Enable SharePoint integration in PowerApps Portal ( Dynamics 365 Portal ), SharePoint Document in Microsoft power pages appeared first on Microsoft Dynamics 365 Blog.

You need a quick and easy way to store and access files related to opportunities, accounts, quotes, contacts, and more. This includes contracts, quotes, offers, images, etc.  then you should be looking for is Dynamics 365 integration with SharePoint.

Click here for blog : Enable SharePoint for Power pages | Power portals | Dynamics 365 Portals

1 – clock on setting and then Advanced Settings. If you can’t find this, make sure you are logged in as a user with administrator privileges.

2 – Open Settings and choose System – Document Management

3 – Choose the option Configure Server-Based SharePoint Integration

4 – On the wizard that will open, indicate if your SharePoint is Online or On-Premises. The SharePoint integration can connect to both. It can even connect to multiple SharePoint sites, but they all have to be either online or On-Premises.

5 – Assuming you chose Online on the previous step, now you one need to enter the URL of the SharePoint site you want to use.

You can simply copy the URL from when you are on the SharePoint site main page and the wizard will validate it when you click Next.

6 – Assuming the validation succeeds, the final step to enable your Server-Based SharePoint Integration is clicking the Finish button.

You can now go back to your Document Management screen and select which entities should be enabled for SharePoint folders.

Click on Document Management Settings.

In the pop-up window, you check the entities under which you anticipate storing documents and click Next.

You can then define the folder structure. Here are your options:

• Not check the Based on entity checkbox – Folders will not be automatically created
• Check the Based on entity checkbox and choose Account – the structure will have account as the primary folder, and sub-folders based on the actual account names will be created under it
• Check the Based on entity checkbox and choose Contact – the structure will start with the contact primary folder, and sub-folders based on the actual contact names will be created under it

Make your selection and click Next. We might have to wait a little at this point as the document libraries will be created. Once you’ve done that, you can click Finish.

The integration is now live! On the Dynamics 365 side you will now see a document option under the entities you enabled. On the screenshot below you can see the document that we created for an Account. Notice that its storage is on SharePoint.

How to use it for document management

• Edit this using the Opportunity record. Let’s say you have a prospective customer named Wonderful World who is working on a grand opening order. They go through your sales cycle and develop documents such as NDAs, specifications, offers, quotes and images. You need a place to store this data securely and easily access, edit, and share it within your organization.

• Notice the File tab circled in blue. When you click on this little guy, two beautiful things happen to him in the background.
  • A new folder is created in SharePoint. This folder is where we store all the files related to the deal.
  • Your Opportunity folder will be nested in your new Wonderful World account folder.
• A new, empty Opportunity folder looks like this: Here you can choose to create a new document, upload a file from your device, or change the SharePoint location. Easily upload 3 documents (image, PDF, Word document) from your laptop.

Click on Upload, and you’ll see an Upload Document dialog box.

Choose the files from your PC (or OneDrive even).

Now you have access to SharePoint. You should see three files inside the Opportunity folder. You will also see a nested Opportunity folder within your Wonderful World account folder. piece of cake. Another nice thing is that SharePoint users can access these files. No need to own a Dynamics 365 license. This means that other members of your organization can contribute to these documents as needed.

The post How to Enable Dynamics 365 CRM and SharePoint Integration Step by Step appeared first on Microsoft Dynamics 365 Blog.

Most of you would be well acquainted with our popular assignment automation app for Dynamics 365 CRM – Lead Assignment and Distribution Automation. Already a Preferred app on Microsoft AppSource, Lead Assignment and Distribution Automation is a productivity app that automates the allocation or distribution of Leads (or any other entity records) recorded in Dynamics 365 CRM. In this way, it ensures that Leads are not mismanaged or overlooked and are assigned to users automatically thereby improving the chances of creating new customers and increasing sales.

Now, let’s reiterate why Lead Assignment and Distribution Automation is the apt app for assigning Leads, Cases or any other entity records in Dynamics 365 CRM.

Say Goodbye to Manual Assignment of Leads

With this assignment automation app, you can assign Leads (or other entity records) to your team members using Round Robin or Capacity Algorithm. With Round Robin algorithm, the incoming Leads will be evenly distributed among your team members. If there are three members in your team and there are six incoming Leads then each member will be allotted two Leads.

But with Capacity Algorithm, the individual capacity of each team member will be taken into consideration. Here, you will be given the provision to determine the capacity of each team member depending upon their experience. And based on this capacity Leads will be allocated to your team members. Here, the most experienced team member will be assigned more Leads as compared to the least experienced team member.

Assign Leads in Sequence

With this feature of Lead Assignment and Distribution Automation, you can set a sequence or order to distribute the Leads to your team members. This will work for both Round Robin and Capacity algorithm and the Leads will be assigned from lowest to the highest sequence. So based on performance, experience or any other factors you can decide to set a sequence and determine who will be the first to get the share of incoming Leads.

Partnership in Leads

With Lead Assignment and Distribution Automation app, you can automate the process of transferring Leads from one team member to another by using workflows (Classic & Power Automate Flows) in Dynamics 365 CRM. There may be cases, where it may seem prudent to first assign Leads to one team member for initial footwork and then assign it to another team member for sales conversion. This will build partnership between team members and enhance productivity.

Now, all of these processes which used to be done manually can be automated with this amazing app. You have to just do three things – Get it, set it and forget it. In other words – get Lead Assignment and Distribution Automation app set it as per your requirements and then forget about it.

Sounds tempting, isn’t it?

Then go to our website or Microsoft AppSource to download this amazing assignment app for a free trial of 15 days and experience how automation of Lead assignment can boost your overall productivity.

And feel free to share your experience and expectations at crm@inogic.com

While we have been talking about Leads how can email marketing be left behind – it’s time to also look at our latest integration app – Marketing4Dynamics which integrates Mailchimp (one of the most famous and used email marketing software across the globe) with Dynamics 365 CRM.

Until then – Stay Healthy, Stay Wealthy!

Please visit the Source and support them

The post 3 Best Practices for Increasing your Lead Conversion Rates – Lead Assignment and Distribution Automation in Dynamics 365 CRM is what you need! appeared first on Microsoft Dynamics 365 Blog.

If you know Power Apps Component Framework, then you must know the updateView method, which is one of the standard methods of PCF.

The updateView method is triggered only when the PCF control is refreshed or rendered and shows us the updated data on our control.

We work on the dataset as well as field type components in PCF. In the dataset, we usually use context.dataset.refresh to refresh the dataset control, which calls the updateView method. Some users also use setState method to re-render a particular component. However, sometimes it becomes difficult to manage the data in the state.

In addition, on using setState only the component for which the state is changed gets re-rendered while all the other components in the PCF control remains as it is.

We recently had a requirement to refresh a field component. However, there is no appropriate refresh method for field component, which can work as same as context.dataset.refresh method.

So to overcome this limitation, let me introduce you a method named as requestRender. It is available for both dataset as well as field components, using this method we can re-render the PCF control. You can use this method as shown here, context.factory.requestRender().

It is similar to refresh method in dataset control; requestRender calls the updateView method and re-renders the control.

Scenario:

Let’s say we are using a single fluent UI component i.e., contextual menu and on click of its menu items, we want to set the button text to the selected menu item as shown below.

To achieve this, we can use setState, but sometimes it becomes difficult to maintain the state. Here, to make our work simple yet efficient, requestRender comes to the rescue.

Below is our Contextual Menu component class code, which we are calling from index.ts file by passing context as props in it.

Here, we selected Tomorrow option and it gets set as the button label.

Code:

export class FluentUIContextualMenu extends React.Component<any, any> {
private _buttonText: string = “Later Today”;
constructor(props: any) {
super(props);
}

render(): JSX.Element {
let menuItems: IContextualMenuItem[] = this.getMenuItems();
return (
<>
<DefaultButton text={this._buttonText}
menuProps={
{
shouldFocusOnMount: true,
directionalHint: DirectionalHint.bottomLeftEdge,
items: menuItems
}
}
/>
</>
)
}

private getMenuItems = (): IContextualMenuItem[] => {
let menuItems: any = [];
menuItems = [
{
key: ‘Later Today’,
iconProps: { iconName: ‘Clock’ },
text: ‘Later Today’,
onClick: (event: React.MouseEvent<HTMLAnchorElement | HTMLButtonElement>, item: IContextualMenuItem) => {
this.onMenuItemClick(event, item);
}
},
{
key: ‘Tomorrow’,
iconProps: { iconName: ‘Coffeescript’ },
text: ‘Tomorrow’,
onClick: (event: React.MouseEvent<HTMLAnchorElement | HTMLButtonElement>, item: IContextualMenuItem) => {
this.onMenuItemClick(event, item);
}
},
{
key: ‘This Weekend’,
iconProps: { iconName: ‘Vacation’ },
text: ‘This Weekend’,
onClick: (event: React.MouseEvent<HTMLAnchorElement | HTMLButtonElement>, item: IContextualMenuItem) => {
this.onMenuItemClick(event, item);
}
},
{
key: ‘Next Week’,
iconProps: { iconName: ‘Suitcase’ },
text: ‘Next Week’,
onClick: (event: React.MouseEvent<HTMLAnchorElement | HTMLButtonElement>, item: IContextualMenuItem) => {
this.onMenuItemClick(event, item);
}
},
];
return menuItems;
}

private onMenuItemClick = (event: React.MouseEvent<HTMLAnchorElement | HTMLButtonElement>, item: IContextualMenuItem) => {
this._buttonText = item.text != undefined ? item.text : this._buttonText;
this.props.context.factory.requestRender();
}
}

Explanation:

In the function onMenuItemClick, the global variable this._buttonText takes the updated text from contextual menu item and this.props.context.factory.requestRender(); renders the control, which calls the updateView method and the selected text remains intact in the global variable that shows the updated text on the contextual menu button.

Similarly, as we know, there is no refresh method available for the field component, unlike the dataset, which has one. We can use the requestRender method in the field component to refresh it.

Another good thing about the requestRender method is that, similar to the setState it maintains and gives the updated data to the user.

Conclusion: In this blog, we learned how to call the UpdateView method programmatically using RequestRender, which eventually helps in refreshing the entire PCF control thus helping us see our changes efficiently.

Reference: https://docs.microsoft.com/en-us/powerapps/developer/component-framework/reference/factory/requestrender

Go to Source and hit them a thumps up

The post How to programmatically call UpdateView in PCF using requestRender appeared first on Microsoft Dynamics 365 Blog.

Microsoft recently introduced Microsoft Power Platform Command Line Interface to perform various operations on Microsoft Dataverse environments, Power Apps Portal, PCF, Plugin, Solution, Admin, and Canvas by using Visual Studio Code.

In this blog, we will be focusing on Power Apps Portal and will see how we can connect Portal using Microsoft Power Platform CLI and perform various operation on the same.

To be precise, we will create a new web page using CLI and check it on the portal.

However, there are some prerequisites that we need to configure before start working on Power Apps Portal.

First, we need to configure the Power Apps Portal for our CRM.

Login to https://make.powerapps.com/ and click Portal from Blank.

After clicking the button, a popup will appear where we need to provide a suitable name for the portal and address.

Then click on the Create button and wait for the portal to become ready to use.

While the portal is being configured, we need to install the Power Platform VS Code Extension in our Visual Studio Code.

Open the Visual Studio, click the extension button and search for the Power Platform VS Code Extension. Once it is visible, click the install button.

Here we are done with prerequisites and ready to connect the Power Apps Portal.

Now create new folder and open that into Visual Studio Code. The Power Apps Portal data will be downloaded in this newly created folder.

Open the Terminal in VS Code.

Now we need to authenticate it in order to connect Power Apps Portal. To authenticate we will use below command:

Command: pac auth create –url <Dynamics CRM Url> –un <User ID> -p <Password>

For example: pac auth create –url https://orgname.crm.dynamics.com –un admin@orgname.onmicrosoft.com -p pass@123

You can check if you have successfully connected to your environment by running the command.

Command: pac org who

This will show you the organization details.

Once successfully authenticated now we need to download the portal data into our system so that we can work offline into our portal and then upload it back to cloud.

To download the Power Apps portal data we need to run the below commands.

Command: pac paportal list

This will show you the listing of portal websites and website ids into your connected environment. The WebsiteId will be used in the command to download the Portal data.

Command: pac paportal download –path “<Directory Path>” –webSiteId <Portal WebsiteId>

For Example:

pac paportal download –path “E:\Sam\PowerAppsCLI” –webSiteId d78574f9-20c3-4dcc-8d8d-85cf5b7ac141

Once it is downloaded, all portal data can be seen in the folder and since we have already opened the folder in our VS Code we just need to refresh it.

Now to create new custom webpage we need to know things we required to update.

• YML extension files: – yml is serialized human readable text document file, which is actually not a Markup Language. Using this we will be setting our web page properties.
  • How we can set property? It will be like key value pair and the key will be logical name of the property and the value for the key needs to specify after the colon (:).

Our custom page should be having the below properties and its values.

• Parent Page(adx_parentpageid) : Home Page
• Page Template(adx_pagetemplateid): Full Page without Child Links
• Publishing State(adx_publishingstateid) : Published

As can be seen above, we will be using the “Home Page” as the value of the adx_parentpageid, “Full Page without Child Links” as the adx_pagetemplateid and “Published” as the adx_publishingstateid.

Moreover, to set the above properties we first need to get unique ids for each of these properties. As each of them are attributes of type lookup in Dynamics 365 CRM and to map respective records in the lookup fields we require their respective Ids.

To get the unique id of the Home Page, expand the Web Pages folder and find home. Then expand it and open the Home.webpage.yml. After that copy the value of adx_webpageid. This is the value we shall use for the adx_parentpageid attribute of our custom page.

To get the unique id of Page Template, expand the page-templates folder from main folder, look for the Full-Page-without-Child-Links.pagetemplate.yml page template file and copy the value of adx_webtemplateid. This is the value we shall use for the adx_pagetemplateid attribute of our custom page.

Similarly, we need to find the id of Publishing State. In the main folder search publishingstate.yml file and copy the value of adx_publishingstateid. This is the value we shall use for the adx_publishingstateid attribute of our custom page.

Now we have all values for our required properties.

To create new custom web page, we will expand the Web Pages folder and within it copy & paste any Web Page. For instance, we copied category page as shown below:

After pasting all required things now we will update folder and files as per our requirement.

We changed the web page name to custom-page and also renamed all files inside the folder. After updating the name, we need to set/update the properties inside the “Custom-Page.webpage.yml” file.

You can check the changes we did in below screenshot:

Now in the “Custom-Page.en-US.webpage.yml” we will be adding the same values as we have set in the above step except for the adx_rootwebpageid. In the adx_rootwebpageid we will set the value of adx_webpageid from the “Custom-Page.webpage.yml” file.

After updating the yml files, we can now update the html files and that will be shown in our portal.

Once changes are done, save the changes. And now we are ready to upload our portal data into cloud.

For uploading the changes, we will use below command:

Command: pac paportal upload –path “<Directory Path>“

For Example: pac paportal upload –path “ E:\Sam\PowerAppsCLI“

Result:

We completed our changes and uploaded those changes on cloud. Now we will check if the changes are reflected in our Portal or not.

Open the portal home page and since parent page of our custom page is home then after the portal url we will add “/<partial name of the page>/” to access our page.

For example: <portal url>/custom-page/

Conclusion:

Using Microsoft Power Platform CLI, we are able to work on the portal in offline mode and after doing the changes, we are able to upload them in one go. In addition, it will help developers to migrate portal data from one environment to other environment with very less effort.

Please visit the Source and support them

The post Perform changes in Power Apps Portal with newly introduced Microsoft Power Platform CLI appeared first on Microsoft Dynamics 365 Blog.