Most of the organization are using the built-in integration between Dynamics 365 and SharePoint, which allows the organization to manage and store documents in SharePoint. Microsoft has expanded the document management capabilities for Dynamics 365 with the built-in integration of Dynamics 365 with OneDrive for Business. With this integration, users can manage the documents for the D365 CE entities from their OneDrive for Business. In this article, we are going to see how to enable Dynamics 365 integration with OneDrive for Business. IT Considerations: No additional software required. You need to have the System Administration role in Dynamics 365 to enable OneDrive for Business integration with D365. Users must have a SharePoint Online license. Enabling D365 integration with OneDrive for Business: Go to Settings > Document Management > Enable OneDrive for Business. Tick on Enable OneDrive for Business and click OK. After enabling OneDrive for Business, you can see OneDrive for Business Folder Settings, in which you can define the folder which will be used for storing the Dynamics 365 documents in your OneDrive for Business. You can see the default folder as /CRM. Go to Dynamics 365 records > Related > Documents. In the Document Location, you will see two folders appeared. OneDrive – From here you can save the document in OneDrive CRM Shared with me  – Files shared with you for the associated record will be shown here. Using OneDrive for Business for Dynamics 365 Entities: Once you are in the Document Location of a record, you can create or upload the document in OneDrive. You will need to first select OneDrive in Document Location. In this case, I am uploading a document to OneDrive for an Opportunity. When I select All locations, I will be able to see all the documents associated with this record. The above-uploaded document has now been associated with this Opportunity. Here is how the folder gets created in your OneDrive for Business. The folder structure will be like CRM > Opportunity > Record. Now, let’s see if the other user can access the OneDrive document I uploaded for the record. I went to the same record and selected All locations. So, the user is only able to see the files on SharePoint. Let’s try to share this file with the user and see if it is accessible after sharing. When the file was shared with other users, the document is now visible under Shared with me a folder or under All locations in the D365 record. You can check the source; it says Shared with Me. This is how we can integrate Dynamics 365 CE with OneDrive for Business and can associate their documents with D365 for Customer Engagement records which any other individual will not be able to see unless the file is shared.

Do not use any CDN links for any .js or .css file, include them in your own project. Do not give multiple references of any .js or .css file on the same HTML. If any .js or .css file is going to be used on multiple Html web resources, then keep them at one common location and include the same URL reference on all the HTML page, do not try to create same web resources repeatedly. Always try to write minimum codes and re-use the code where possible. Always try to use objects where possible. Minimize the use of global variables (use local variables). Avoid multiple API hits try to get maximum data in a single hit where possible. Use joins in fetch XML queries to get data from all the related entity to avoid multiple API hits. Use Try and catch for exception handling. Minify .js and .css file before releasing the same on production.

Using Xrm.WebApi needs you to be careful with the field names and what to use when. Especially, when you are dealing with Lookups. One of the most common errors you’ll come across is the one like below – “An undeclared property (fieldname you entered) which only has property annotations in the payload but no property value was found in the payload.” This is confusing as to what needs to be put in while setting the lookup. If you have done the below, entered the name of the field which is all in small caps  – object[“msdyn_resourcerequirement@odata.bind”] = “/msdyn_resourcerequirements(<Guid>)”; This will result in the above error!!!   You’ll need to put the Schema name of the lookup field instead and this should solve your problem – and the code should look like this – object[“msdyn_ResourceRequirement@odata.bind”] = “/msdyn_resourcerequirements(<Guid>)”; And this should totally work for you!! Hope this helps! 🙂

One of the common tasks to import multiple users in Office 365 is to be able to create multiple users in the most efficient way possible. Here’s a quick guide to doing so using Import multiple users feature in Office 365 Admin Center. Download Template for Importing Users Let’s say you are in the Admin Center using portal.office.com. Under Users, You’ll find a button to Add Multiple Users And the feature lets you download a template with some sample data in case you’re unsure of what to enter. Once downloaded, you’ll get the Excel in your system Now, you’ll see some sample data which you can simply delete to add your actual data. And let’s say, your data looks like this. I’ve added Kuldeep Gupta and Subhash Mahato, 2 users with some info. Import Back into O365 Now, we are set to import this in O365. On the same feature, look for Browser button to import. Click Verify to validate the info entered for any errors. Once verified, you can click Next. On the next step, I’ll assign licenses and proceed by clicking Next. Once the processing is done, users will be added And you’ll see 2 new users in O365 with the selected licenses Hope this was easy! 🙂  

Why it is required? Let’s discuss the scenario where we will be required to have some records in the Multiple Environment. Let’s say we have workflow or flow which is configured or running with specific records. So, if we move the flow or workflow to another organization or Instance so the same record is not available with the same GUID. To run the flow or workflow we must change the flow or workflow. Now if we have 10 – 20 flow / Workflow like the same, then it will be so much time consuming So, the best solution to have the Same records with the same GUID in multiple instances. Prerequisite: The system must have the same entity and fields present in both the system in which you must transfer records. Because it will through an error while import to destination Environment Solution: Exporting Phase: Login to Source Environment from where you want to export the Data. Open the Entity of which data needs to be migrated. You can see I have an Entity called Customer which is having a few numbers of records present in the system. Now You need to export the Data from the source Environment. Export Data from the advance find or direct from the View. After Exporting the Data from the system, an excel file will be downloaded with the same columns as in the views. Now, open the exported Data file. The following is the screenshot of the file. You can see there will hidden Columns in Excel A, B, and C. Now to Unhide the Hidden Columns, select all Data Or Press Ctrl + A and Go to Format in Home Section > Under the Visibility Section Click on Hide & Unhide > Unhide Columns. Please see the following Screenshot for more reference. Now You can see all the three Columns as (Do Not Modify) Entity Name, (Do Not Modify) Row Checksum & (Do Not Modify) Modified On. You can see the Hidden Column in the screenshot after unhiding. Let’s move forward now, we must delete (Do Not Modify) Row Checksum & (Do Not Modify) Modified on Columns because we are not required those columns while importing to another environment. If we will import with those columns it will through the error while import Operation. Change the Header from (Do not Modify) Entity_name to Entity_name for convenience while mapping during importing and Save as CSV. Now Your File is ready to import in another system. Let’s go towards the importing phase.

Introduction It is important for the end-user to understand the error displayed on D365 Portals. In this blog, we will display D365 Plugin Error on the D365 Portals. By default, the error will be displayed as shown below: Implementation Step 1: Create a new Site Setting record. Step 2: Set the values given below in the fields: Name: Site/EnableCustomPluginError Value: true Now you can see the Error thrown by D365 Plugin. Custom plugin errors will appear on the following screens: Entity list Retrieval of records Entity form Retrieve Create/Update and so on Web forms Retrieve Create/Update and so on

Introduction In this blog, we will resolve “Operation has timed out” error in D365 Portals. Steps to solve this issue: Restart your portal by going to the admin center. Steps to restart the portal: Go to the Dynamics 365 Administration Center page and select the Applications tab. Select the name of the portal, and then select Manage. Click on Portal Actions –>Restart.  Click on Restart. Wait for a few minutes and go back to your portal, it should be working now. Reference: https://docs.microsoft.com/en-us/dynamics365/portals/portal-faq

The tips for formating SSRS reports have been covered here. The Default margin settings have been given as to avoid the blank page issue And give the report a formal look. Also, how to Align Page Number in center of the page has been showed. Default margin settings:- Aligning Page Number in center of the page :- Select Page Number Text Box-> Format->Center in Form Hope this helps! For more such blogs refer the below link. https://www.cloudfronts.com/how-to-use-level-up-for-dynamics-365-crm/

Introduction: This blog details steps on how to disable most recently used items in Lookup of D365 CRM. Scenario: Enabling prefiltering on “Reported By Contact” Lookup by Service Account in Work Order Form of D365 Field Service however it shows records which are not filtered. Developers assume prefiltering is not working however it shows most recently used items also. This feature was released in version 9.1.0.3452 and it can be disabled by following the below steps. Step: Navigate to the form editor and open the lookup field’s properties dialog. The checkbox should be enabled for option “Disable most recently used items for this field” below is screenshot for reference. Below is screenshot after publishing the form and Contacts are shown as expected.   Conclusion: Hope this blog helps you resolve the issue for disabling most recent items in lookup of D365 CRM.

Microsoft Excel has traditionally been the go-to reporting tool for businesses, but Power BI offers powerful analytics and reporting features for organizations. With faster experimentation with visualizations, statistical functions and calculations across broad datasets and ability to derive answers on the fly through the rapid recombination of fields, it is clear that Power BI delivers far greater insight than Excel. Reasons Why You Should Migrate Reporting from Excel to Power BI: 1. Storing and Accessing Large amount of Data Power BI has very impressive compression abilities for Microsoft Excel and text/.csv files, which allows you to view, analyze and visualize huge quantities of data that cannot be opened in Excel. Large datasets don’t have to be cut down in size and aggregated to show more encompassing analysis. 2.Applications Excel does have some of the newer charts now, they can’t connect to the data model. But Power BI is ideal for Dashboards, alerts, KPIs, and visualizations, including analyzing your data visually. 3.Reports Excel reports are normal and ordinary comparing Power BI whereas Power BI offers Beautiful branded reports comparing Excel. 4.Cross Filtering Power BI allows advanced features in Cross filtering between charts unlike excel. 5.Dashboard Refreshment You can refresh data in Power BI. Excel does not allow dashboard refreshment. 6.DataSet Power BI has the capability of handling larger dataset. Excel can handle limited dataset only. 7. Incredible Cloud-based Features Once you have finished constructing your Power BI analysis, you need a way to publish and disseminate your dashboards and reports. In Excel this would typically involve emailing a large file around, putting it in a shared drive or SharePoint portal, and letting people know it has been updated.With Power BI offered “publish” this process has been completely revolutionized. 8.Natural Language Query This incredible feature allows users to type questions and get an answer, either in a default or user-specified form. This is useful for executives with specific questions and business users who are unfamiliar with Power BI or the data model behind the report. Power BI is an easy tool to use that helps propel organizations into a data driven culture. With powerful self-service abilities, no longer are business users dependent on IT for gathering, transforming and analyzing data. Automation of dataset integration, ease of expansion into new data sources, rapid visualizations, and easily deployable Row Level Security are amongst the many reasons Power BI is a necessity.Additionally, a cloud-based collaboration environment with features like Natural Language Query ease the process of data governance. In the age of analytics, it’s import for organizations to intelligently utilize the data they collect to rapidly evolve with changing business and consumer habits. For more such blogs refer the below link. https://www.cloudfronts.com/how-to-use-level-up-for-dynamics-365-crm/