Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
best way to implement custom web page in crm RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello, I have a possible requirement where I'll need to give the user the ability to click on a "Maximize Notes" button in the ribbon to open the incident notes in full screen mode in a custom web page.  The notes on this custom web page will display in full screen mode with an extra-large font.

    I worked on a previous CRM project that used a separate .NET WebSite project as a container for all custom web pages used by the CRM installation. A more experienced CRM developer on the previous project recreated one of the custom web pages as webresources within CRM and said that this was a more proper way to implement the custom web page solution.

    Is this the general approach that you would use to implement/deliver a custom web page used by CRM?  If so then can you describe how you would implement the functionality described in my first paragraph using this approach?
    Saturday, January 25, 2014 7:09 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    It is true that you are better off using an HTML web resource to deliver your custom user interface if at all possible. This has many advantages such as:

    1. Easier to deploy (part of the CRM solution)

    2. Can access the Xrm Client API that gives you access to things like Server URL, User Role and organisation name.

    3. You can call the SDK Webservices using the same authentication mechanism as the user is using to access CRM, so no storing of username/passwords or second logins. Since the webresource is hosted under the same domain as crm, authentication is passed through.

    4. You can use the REST endpoint to make communication with the server via Javascript easier. Although this can be done via another externally hosted webpage, it is harder due to authentication and cross domain issues.

    5. Client side caching is handled for you by the web resource mechanism. When a new version is published, the client side cache of html/javascript is invalidated automatically for you.

    6. You can make your custom UI work offline easily.

    There of course disadvantages around the fact that it is harder to make code run on the server and you can't use the ASP.NET/MVC style of programming. Custom actions in CRM2013 make it easier to implement server side code.

    If you want to make it easier to develop these custom UI's using JavaScript and HTML you can use my open source project - http://www.sparkleXrm.com.com

    Hope this helps,

    Scott

    Scott Durow
    Blog www.develop1.net    Follow Me
    Rockstar365
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Sunday, January 26, 2014 4:16 PM
    Answerer