Archives

Archives / 2015 / July
  • NPAPI Plugins will not work on chrome version 42 and higher

    Plugins allow extra features to be added to browsers. For example, you can watch certain types of videos or play a game that’s on a webpage.

     

    NPAPI(Netscape Plugin Application Programming Interface) support has ended

    In the past, many plugins were developed using an older system called NPAPI. Today fewer sites are using NPAPI plugins and they can sometimes cause security risks on websites.

     

    To make browsing with Chrome safer, faster, and more stable, we’re ending support for NPAPI with Chrome version 42.

    Which plugins are supported

     

    Plugins that use a newer, more secure system called Pepper API (PPAPI) will continue to work, including those that come with Chrome, like Adobe Flash and PDF Viewer. If Flash or PDF doesn’t automatically load, make sure that you have the PPAPI plugin version enabled in Chrome.

    Plugins that use NPAPI, including Silverlight, Java, and Unity, will not work

     
    To enable PPAPI plugins follow below steps
    • Open Chrome.
    • In the address bar at the top, type chrome://plugins and press Enter.
    • Click Details.
    • Scroll down to "Adobe Flash Player."
    • Under "Type: PPAPI," click Enable.
     
    How to temporarily enable NPAPI plugins

    If you must use a NPAPI plugin, there’s a temporary workaround that will work until Chrome version 45 is released later in 2015:

    • Open Chrome.
    • In the address bar at the top of the screen, type chrome://flags/#enable-npapi
    • In the window that opens, click the link that says Enable under the Enable NPAPI flag.
    • In the bottom left corner of the page, click the Relaunch Now button.

    After the release of Chrome version 45, you’ll need to use an alternate web browser to load content that requires a NPAPI plugin.

  • Time Out Expired error in MSCRM

    When you import large customization files into Microsoft Dynamics CRM 2011 or into Microsoft Dynamics CRM 2013, or into Microsoft Dynamics CRM 2015 time-out occurs. Additionally, you receive one of the following error messages.

    Types of Errors will be

    Error message 1: Import timeout error

    Error message 2: The file could not be uploaded or import failed

    Error message 3: Maximum request length exceeded

    Error message 4: This is not a valid customization file. Please use and XML file that was generated by exporting customizations.

    If the DevErrors value is set to "On" in the Web.config file, you receive the following error message:

    Microsoft CRM Platform Error Report: 
    Error Description: Timeout expired 
    Error Details: Details on this error have not been provided by the platform. 
    Error Number: 0x80040E31

    Reason for the issue is:

    This problem occurs because one of the following conditions is true:

    • The time that is used for importing the customization files or for upgrading Microsoft Business Solutions - CRM exceeds the default OLEDBTimeout value in Microsoft Dynamics CRM for the computer that is running Microsoft SQL Server.
    • The time that is used for importing the customization files or for upgrading Microsoft CRM exceeds the ExtendedTimeout value that is used for long-running operations.

    Notes

    • The ExtendedTimeout registry entry on the Microsoft Dynamics CRM server should not be set to a value that is larger than 2,147,483,647. That is the maximum value that the ExtendedTimout registry entry can use. 
      Note
    • Importing customization files can be a long-running operation.
    • The size of the Customization.xml file is larger than 7.5 megabytes (MB).

     

    Notes

    • The Customization.xml file is created when you export custom entities.
    • By default, Microsoft ASP.NET limits the HTTP request size to 8 MB.

    The OLEDBTimeout value

     

    The unit of the OLEDBTimeout value is seconds. By default, the OLEDBTimeout value is 30 seconds. The OLEDBTimeout value controls the SQL time-out value that is used for a single SQL query. The increased OLEDBTimeout value is useful when the SQL server is overloaded. Additionally, the query takes a longer time to process.

    The ExtendedTimeout value

     

    The unit of the ExtendedTimeout value is milliseconds. By default, the ExtendedTimeout value is 1000000 milliseconds. The ExtendedTimeout value controls the ASP.NET time-out value that is used for import requests. The time-out value must be larger than the time for finishing the whole import process. The increased ExtendedTimeout value is useful when the import process takes a long time.


    Note When the performance of the SQL server is slow or when there are many customization files to import, the import process takes a long time.

    Resolution to solve this issue is:

    To resolve this problem, use one or more of the following methods.

    Method 1: Add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values

    Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

    1. Click Start, click Run, type regedit, and then click OK.

    2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM

    3. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.

    4. Rename the DWORD value to the following value:

    OLEDBTimeout
    NOTE: This value is case sensitive

    5. Right-click the DWORD value, and then click Modify.

    6. In the Edit DWORD Value dialog box, type 86400 in the Value data box, click Decimal in the Base option, and then click OK.
    Note

    According to the requirement of the computer that is running SQL server and the number of customization files, the value can be larger than 86400. The value of 86400 is equivalent to 24 hours. This should only be done temporarily or as a troubleshooting step. The recommended value of this is between 30 and 300. Leaving this setting too high can result in performance issues.

    7. Right-click MSCRM, point to New, and then click DWORD Value to create a new DWORD value.

    8. Rename the DWORD value to the following value:

    ExtendedTimeout

    9. Right-click the DWORD value, and then click Modify

    10. In the Edit DWORD Value dialog box, type 1000000 in the Value data box, and then click OK.

    Notes

    In the Value data box, you can type a value that is larger than 1,000,000. However, do not type a value that is larger than 2,147,483,647. This is hexadecimal 0x7FFFFFFF.

     Important: If this key already exists, notice the current value. After you have completed the import or the upgrade for Microsoft Dynamics CRM, set the value of this key back to the original value or delete the key if it did not previously exist. The default OLEDBTimeout value is 30 seconds.

     

    Method 2: Modify the parameters in two different Web.config files

    1. Click Start, click All Programs, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

    2. Expand the server name, and then expand Web Sites.

    3. Right-click the Microsoft CRM v3.0 Web site or the Microsoft CRM v4.0 Web site, and then click Open.

    4. Right-click the Web.config file, click Open With, and then click Notepad.

    5. In Notepad, locate the following line.

    <httpRuntime executionTimeout="300" maxRequestLength="8192"/>

    6. Change executionTimeout="3600" and change maxRequestLength="20000".

    7. Save and then close the Web.config file.

    8. In the directory in which you opened the Web.config file, open the MSCRMServices folder.

    9. Right-click the Web.config file, click Open With, and then click Notepad.

    10. In Notepad, locate the following line.

    <httpRuntime maxRequestLength="8192"/>

    11. Change maxRequestLength="20000".

    12. Save and then close the Web.config file.

    Important: After completing the action that requires the above changes to the web.config file, these parameters should be reset to their default values.

  • Send an Email on creation of Notes in MSCRM 2015

    Sending email with an entity record description from Notes then this solution is going to help you to implement this requirement. Let’s consider a business scenario where we have implemented a customer approval process and as soon as the customer approves we need to send him notification with the description in notes.

    We can’t access description from Notes in an OOB workflow so we need to write a custom workflow where we need to get an entity record description from an annotation entity.

    So mainly we need to use the following procedure to implement our requirements:

    • Develop a custom workflow assembly to get an attachment.
    • Create a workflow and use a custom workflow assembly step to send the email.

     

    The Process is described below:

    This solution works for Opportunity entity. On creation of Notes in opportunity an email will  be created and sends an email to the opportunity account or contact.

    image

     

    On creation of Note an Email activity will create as From will be the CRM logged in user and the To will be the opportunity contact.

    And setting the Email regarding as Opportunity and body of the Email will be Notes description.

    image

     

     

    Installation Procedure:

    To install this solution please follow below steps:

    Prerequisite: Email router configuration is necessary to send an email.

    step1: Save the CRM solution on your desk. Download here.

    step 2: import the solution. Navigation is settings –> customizations –> solution –> import

    step 3: click on Browse and select the solution from the downloaded path.

    step 4: Click on the next until imports. Then close the form and refresh the page.

    step 5: After importing the process test the solution as described above.

  • Multiple File attachment uploaded for MSCRM 2015

    CRM OOB feature allows adding single attachment to the Email activity, but the functionality of this solution enhances the Emails to get multiple attachments on a single click, as compared to the conventional method of having one attachment to the email

    The functionality is explained briefly here:

    Create an Email activity and save the record.

    Upon saving the record you can able to see the below tab. Please see the below screenshot.

     

    image

    Click on Select files. This will pop up with the list of files to upload. select the multiple files by clicking on the

    Shift or CTRL key.

    Click on Open. Then select the submit button.

    image

     

    The added files will be shown in the Attachment area.

    image 

     

  • String Functions

    Concatenation of two Strings:-

     

    • In any Entity of MS Dynamic CRM, Two Strings (Single line of text) can be concatenated by this library function.


       

     

    • In the Image, first two Highlighted Single line of text fields are concatenated and the resultant string will be displayed in the last highlighted Single line of text field.

    Execution of Work Flow:-   

    •  Write the Source code and register the dll file using plugin registration tool.
    • Go to “Processes” Entity and create new process by clicking on NEW .

     

     

     

    • Enter Process Name, Select category as Workflow, Select Entity on which you wish to fire and Check Type as New blank Process. Click on OK. 

     

     

    •  Check “START WHEN”, this decides when your workflow should fire. 

     

     

    •  Click on Add Step, select your workflow.
    •  Add another step “UPDATE RECORD” for output to display. This displays the output when the record is updated.

     

     

     

    •  Now Click on Set Properties to set input and output properties.
    •  Activate the Process by clicking on “Activate” button.
    •  Select the required entity and fields and then click Add then OK.

     

     

     

     

     

    •  Select the field which displays output and set workflow into it by clicking on entity fields and click add and then ok.

     

     

     

     

     

    •  This completes the setting of input and output properties.

     

    •  Now go to entity forms and provide input values and click on save.

     

    •  Check into system jobs entity to know whether the workflow got succeeded or not.

     

     

     

     Replace one String with another String:

    • In any Entity of MS Dynamic CRM, the text field is replacing with new text field. It do not allow Case Sensitive.

     

     

     

     

     

    Execution of Work Flow:-   

    •  Write the Source code and register the dll file using plugin registration tool.
    • Go to “Processes” Entity and create new process by clicking on NEW.
    • Enter Process Name, Select category as Workflow, Select Entity on which you wish to fire and Check Type as New blank Process. Click on OK.
    •  Check “START WHEN”, this decides when your workflow should fire.
    • Click on Add Step, select your workflow.
    •  Add another step “UPDATE RECORD” for output to display. This displays the output when the record is updated.
    •  Now Click on Set Properties to set input and output properties.
    •  Activate the Process by clicking on “Activate” button.
    • Select the required entity and fields and then click Add then OK.

     

     

     

    •  Select the field which displays output and set workflow into it by clicking on entity fields and click add and then ok.

     

     

     

     

     

     

     

     

    •  This completes the setting of input and output properties.

     

    •  Now go to entity forms and provide input values and click on save.

     

    •  Check into system jobs entity to know whether the workflow got succeeded or not.

     

     

     

    Right and Left Trim of the text:

     

    • In any Entity of MS Dynamic CRM, If any String contains Space that can be removed whether it is right side of the String and left side of the String.

     

    Execution of Work Flow:-   

    •  Write the Source code and register the dll file using plugin registration tool.
    • Go to “Processes” Entity and create new process by clicking on NEW.
    •  Enter Process Name, Select category as Workflow, Select Entity on which you wish to fire and Check Type as New blank Process. Click on OK.
    •  Click on Add Step, select your workflow.
    • Add another step “UPDATE RECORD” for output to display. This displays the output when the record is updated.
    •  Now Click on Set Properties to set input and output properties.
    •  Activate the Process by clicking on “Activate” button.
    • Select the required entity and fields and then click Add then OK.

     

     

     

     

     

    •   Select the field which displays output and set workflow into it by clicking on entity fields and click add and then ok.

     

     

     

     

     

    •  This completes the setting of input and output properties.

     

    •  Now go to entity forms and provide input values and click on save.
    • Check into system jobs entity to know whether the workflow got succeeded or not.

    The String function solution download here:    Download

Please Wait