Dynamics Community Forum Thread Details

We use encodeURIComponents to pass parameters to a html web resource. We use decodeURIComponent in the HTML web resource to get the string and we split it to an array at the & chars (26). This works fine in the old legacy UI but when testing in the ne Unified Interface the chars '25' are getting added to the string parameter after each '%' char. In the old UI the parameter looks like this after we pass it to the function decodeURIComponent:

Phil%20Crocker%26test%2640472B11-122B-EA11-A810-000D3A86A78C

but in the Unified Interface the string looks like this after it is passed to the same function:

Phil%2520Crocker%2526null%2526B184FA94-0E2B-EA11-A810-000D3A86AD25 (ignore the 25 at the end of the GUID - it is a coincidence)

I am using Xrm.Navigation.openWebResource to open the web resource and pass the string parameter. The string parameter is built up like this:

var params = currentUserName + "&" + resolveComments + "&" + caseId;

Here is the code used:

This opens the web resource and passes the string parameter:

//Open Resolve case form
function OpenResolveCaseForm(caseId, currentUserName, resolveComments)
{
debugger;
    var params = currentUserName + "&" + resolveComments + "&" + caseId;
    var customParameters = encodeURIComponent(params);
    var windowOptions = { height: 200, width: 500 }
   Xrm.Navigation.openWebResource("pol_ResolutionForm", windowOptions ,customParameters);
}

This converts the string to an array and should contain 3 seperate string objects:

System User name
Text for text box
Case record ID

Anyone else experiencing this behaviour or have an idea why this functionality has changed with the Unified Interface

Thanks

Phil

Hi Phil,

It looks like your string is encoded twice:

Without encoding: Phil Crocker&test&40472B11-122B-EA11-A810-000D3A86A78C
After a 1st encoding: Phil%20Crocker%26test%2640472B11-122B-EA11-A810-000D3A86A78C
After a 2nd encoding: Phil%2520Crocker%2526test%252640472B11-122B-EA11-A810-000D3A86A78C

I have no idea if this expected in Unified Interface, so I would open a Support Request: https://admin.powerplatform.microsoft.com/support

On a side note, I see you are trying to replace the default Case Resolution logic with a custom Web Resource.
You might to keep an eye open for the 2020 Release Wave 1, as 2019 Release Wave 2 introduced this for opportunities:
https://docs.microsoft.com/en-us/dynamics365-release-plan/2019wave2/dynamics365-sales/customization-opportunity-close-dialog-box

Also, have you had a look at the navigateTo method? It could be of interest to you, although it has some limitations, as highlighted in this article:
https://butenko.pro/2019/12/23/xrm-navigation-navigateto-gotchas-tricks-and-limitations/

Henry