Navigate to Url Action and UrlEncoding

2 posts, 0 answers
  1. Jeff
    Jeff avatar
    6 posts
    Member since:
    May 2013

    Posted 20 Apr 2015 Link to this post

    We have a report with a Navigate to Url Action on a cell.  The Url generated consists of a time range where the times specified are DateTimeOffsets. We discovered an issue where times with a non-negative time zone offset would result in an incorrect Url string.  The root cause of this was due to the '+' in the '+00:00' portion of the DateTimeOffset not being UrlEncoded as it should be and resulted in a space instead of a plus.

    I believe this may be a bug/issue in how Telerik's Report Viewer generates the Url when the report is generated.  I believe it is not properly escaping all characters that should be escaped in a Url.


    Our solution is to create a User Function called UrlEncode which receives a string and returns the results of the C# WebUtility.UrlEncode() function.  This standard .Net function properly UrlEncodes all necessary characters in the string.  The only limitation I've seen is that it is new as of .NET 4.5. (Here is the MSDN documentation for this method:

    I've detailed an example below.


    A start date of 04/07/2015 13:29:32 +00:00

    An end date of 04/07/2015 13:34:25 +00:00


    The following is the original version of the Target Url expression used to generate the Url in the Navigate To Url action. This resulted in the '+' portion of a positive time zone offset being replaced by a space in the resulting Url:

    = '../RptExternal?' +
    'sDate=' + Fields.StartDate.ToString() +
    '&eDate=' + Fields.EndDate.ToString()

     This resulted in a Url such as:


    While relatively easy to decipher visually, our ASP.NET MVC web app would receive that and translate the URL incorrectly by replacing each occurrence of a '+' with a space.

    With the solution described above, the following is the working version of the Target Url expression used to generate the Url in the Navigate To Url action:


    = '../RptExternal?' +
    'sDate=' + Reporting.Helper.UserFunctions.UrlEncode(Fields.StartDate.ToString()) +
    '&eDate=' + Reporting.Helper.UserFunctions.UrlEncode(Fields.EndDate.ToString())

    This results in a Url such as:


    Which our web app receives and properly translates the date times into valid DateTimeOffsets as expected.

  2. Nasko
    Nasko avatar
    1045 posts

    Posted 22 Apr 2015 Link to this post

    Hello Jeff,

    Thank you for sharing this solution. It is the suggested solution to use the UrlEncode method in this scenario. However, you might also find useful the following discussion on replacing UrlEncodeHow do you UrlEncode without using System.Web?.


    See What's Next in App Development. Register for TelerikNEXT.

Back to Top