microsoft dynamics crm Archives - Microsoft Dynamics 365 Blog

How to Enable Dynamics 365 CRM and SharePoint Integration Step by Step

Microsoft Dynamics 365 — Sat, 20 May 2023 14:25:17 +0000

Enable SharePoint for Microsoft dynamics CE

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.

Deployment process flow and Access level Distribution for Support client (Non Technical Explanation not the Current Best Practice )

Microsoft Dynamics 365 — Mon, 22 Jun 2020 16:47:42 +0000

Below Process or Steps are not to be implemented for all Scenario and doesn't include CDS as well. This is just a Generic Flow Sent to one of a Support client to make them understand how deployment with multi Environment (Prod and Non-Prod) are done in Layman Language as we were Seeing constant change on Production by System Users.

QUICK SUMMARY

No Development or Customization should be done on UAT and PRODUCTION
Customization roles are never Given to System User or System ADMIN. Customization Roles and Credentials will only be with IT, Admin, and Support Team.
Deployment From DEV to UAT and UAT to Production needs to be followed and should only be done by the Support team or Deployment Team
1. Case Number is registered Support Portal
2. All emails follow-up and requirements should contain Case number in Subject.
3. If ticket Require any FIX/CHANGE/DEVELOPMENT, A new Solution Package is created with the Case number in CRM DEV Environment containing all the development or changed components
4. Once unit testing is done of DEV by the Support team, Solution Package will be moved to UAT.
5. After UAT Deployment, System User will be informed to Test Fix and change.
6. If System User Failed the Testing, Fix will be done in Dev first and then only moved to UAT for retesting
7. If the System User Test is Successful, the Support team will send Deployment Document with Required component and Fix details
8. Once the Document is signed by System User, the Support team will Deploy Solution from UAT TO DEV.
9. Validation will be done by the Support team and Confirmation will be sent once done.
Once Deployment is done, or the Issue has been resolve Case will be closed.

Deployment Process (Again for Non-Technical System Users)

Microsoft dynamics 365 CRM ProjectName has multiple instances i.e. DEV,UAT and PRODUCTION and support/dev team need continuous fixes/development releases to Production and as explained in below process,

Development can only be done in DEV that can include
– Entity, Fields, Relationship, Optionsets
– System + Custom Templates
– Process/Flow/Codes/business rule/web resources
– Security roles, Field Security, Reports, System Settings, Configurations
– Forms, views, charts, dashboards, Sitemap
– E.T.C
No Development or customization can be done on UAT: UAT is for Integration + process + Performance testing
– All Customization + Confirmations need to be moved from DEV to UAT using Solution Package and Configuration Migration
– Can only Map Transaction data to Configurations Example In Approval Process actual or test Approvers user can be mapped in UAT
– No Dashboard Change, No Charts Change, No Configuration change, No field mandatory non-mandatory Change,No security role change, No email Template, No Workflow Change, No Field Creation, No Report change, No System Settings, No System or Custom views changes can be done directly on UAT

PRODUCTION: All customization + configurations need to be moved from UAT to PROD using Solution and configuration migration package deployment.
No Development or Customizations of any type can be done on Production
NOTE: To prevent this as per standards, Customization roles are never Given to System User or System ADMIN. Customization Roles and Credentials can only be with the IT Admin and Support Team and can only be used in the presence of the Support Team.
Also, Customization Role Removal doesn’t remove Charts, Dashboard or advance find Rights. System admin can still be Accessible by system admin.

Key Roles and Permissions on Environments

Below are the issues/Problems which can occur if we don’t follow standard Deployment process and Stockholder Access Levels

For smooth DEV -> UAT -> PROD Fix deployment i.e to prevent solution errors and issues post-deployment.
Prevent Missing Dependencies and overwriting existing important customization
GUID can be different which can break integration or approval process
Performance issue
Troubleshooting can take more time than usual and Downtime can increase so user cannot access Production
Unequal multiple environments will result in no Fix Deployment and unexpected system behaviors and would be difficult to troubleshoot

Below are the Stockholders, Login Access and Permission as per standards

The post Deployment process flow and Access level Distribution for Support client (Non Technical Explanation not the Current Best Practice ) appeared first on Microsoft Dynamics 365 Blog.

Set only contact entity or only Account entity customer field lookup in case / Opportunity for ms crm

Microsoft Dynamics 365 — Fri, 11 Mar 2016 10:01:00 +0000

Set potential customer look up field to only for contact entity record.

By default out of the box functionality gave a pop up with two entity type -contact & account for customer lookup field ,
if your requirement is to set only contact or only account as entity it can be done using javascript as given below ,

Both Contact and Account are viewed by Default

Only Contact records are views

Only Contact is selected and read only

Both account and contact shown by default

function disableaccountfromcustomer() {

debugger;

//timeout of 1sec

setTimeout(function () {

debugger;

var getid = $(‘#customerid_i’); //customer field id contain account and contact both view

getid .attr(‘defaulttype’, ‘2’); // default advance find entity type to contact

getid .attr(‘lookuptypes’, ‘2’); //change lookup view to contact

}, 1000);

}

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post Set only contact entity or only Account entity customer field lookup in case / Opportunity for ms crm appeared first on Microsoft Dynamics 365 Blog.

ERROR : The specified user is either disabled or is not a member of any business unit in Microsoft Dynamics CRM while activating workflow or saving a record ( The System Could not log you on. This could be because your user record or the business unit you belong to has been disabled in microsoft Dynamics CRM )

Microsoft Dynamics 365 — Mon, 16 Nov 2015 15:24:00 +0000

While activating one draft workflow, i was getting an error .

The System Could not log you on. This could be because your user record or the business unit you belong to has been disabled in Microsoft Dynamics CRM

This happened because of following :

1. Workflow owner user is deactivated , change the user or activate the one and activate the workflow .

2. If error is coming while saving a record , the plugin or workflow might be executing under user context and that user is no longer enabled , either change the context to organization ( for workflow)

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post ERROR : The specified user is either disabled or is not a member of any business unit in Microsoft Dynamics CRM while activating workflow or saving a record ( The System Could not log you on. This could be because your user record or the business unit you belong to has been disabled in microsoft Dynamics CRM ) appeared first on Microsoft Dynamics 365 Blog.

Set Profile Image / note attachment using javascript / jquery in mscrm

Microsoft Dynamics 365 — Tue, 01 Sep 2015 12:52:00 +0000

Below code convert image from upload control and convert it into base64 which can be directly set to the image field / notes etc ,

function uploadprofilepic(){

var imgvar = new Image();

imgvar.src = SourceOfFile;

imgvar.onload = function () {

var canvas = document.createElement(“canvas”);

canvas.width = this.width;

canvas.height = this.height;

var ctx = canvas.getContext(“2d”);

ctx.drawImage(this, 0, 0);

var dataURL = canvas.toDataURL(“image/png”);

var base64Image = dataURL.replace(/^data:image/(png|jpg);base64,/, “”);

Now This base64Image can be set Directly to Imageprofile of an entity .

entityimage = base64Image ;

Hope this Helped Thanks for the Support .

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post Set Profile Image / note attachment using javascript / jquery in mscrm appeared first on Microsoft Dynamics 365 Blog.

Get / Retrieve all Fields of an Entity in MSCRM using C# ( RetrieveEntityRequest )

Microsoft Dynamics 365 — Tue, 01 Sep 2015 12:46:00 +0000

Below Code Retrieve all Fields Of an Entity which can be used to perfore sevral execution Like bulk update of fields in an entity .

RetrieveEntityRequest aEntity = new RetrieveEntityRequest();

aEntity.LogicalName = entityLogicanName;

//only get published fields / attributes

aEntity.RetrieveAsIfPublished = true;

aEntity.EntityFilters = EntityFilters.All ;

RetrieveEntityResponse resp = (RetrieveEntityResponse)service.Execute(aEntity);

EntityMetadata getmetadata = resp.EntityMetadata;

var crmAttributes = getmetadata.Attributes;

attributes.Items.Clear();

foreach (var attr in crmAttributes)

{

// filter can be used to get only Custom fields / or System fields with change

if (attr.IsSecured == false && (attr.CanBeSecuredForUpdate == true || attr.CanBeSecuredForRead == true || attr.CanBeSecuredForCreate == true))

attributes.Items.Add(attr.LogicalName);

}

Hope This Helped You Thanks For the Support , If Any query or suggestion , please comment below

SOURCE : JUST2CODE.IN Subscribe to our YouTube channel : https://www.youtube.com/user/TheRussell2012

The post Get / Retrieve all Fields of an Entity in MSCRM using C# ( RetrieveEntityRequest ) appeared first on Microsoft Dynamics 365 Blog.