Hi 

Can anybody help me ?

One week without response .. so long !

Kind regards

Andrzej 

Hello Andrzej,

First of all, deeply apologize for the late response. I can also see the issue in here and need to discuss with our developer teams. I will let you know the result asap.

Regards,
Handy 

Hi Andrzej,

The e.QueryString in the OnNavigatedTo method is populated correctly when navigated locally. However, it seems to populated too late when the page is navigated from external application (through ClientUI application framework). Consequently, this caused an error when your code attempted to access the e.QueryString dictionary in the method.

The fix for the issue will be available in this month's hotfix due to release in a couple days.

Thanks,
Jimmy

Hi Andrzej,

The new hotfix is now available (build 4), which includes the fix to this issue.

In your code, use this.NavigationContextExtended.QueryString in order to access the parameter.

Hope this helps,
Jimmy

Hi Jimmy,

Yes, it's  working now.

But...

Is it neccesary to add new "NavigationContextExtended" property. 

If so, that's no problem, otherwise it leads to a lack of clarity of methods and their applications (in my opinion).

Kind Regards

Andrzej

Hi Andrzej,

Yes, it's necessary to use the NavigationContextExtended since we extend the default navigation behavior.

You can always use NavigationContextExtended in all scenarios, it should work 100% reliable, whether the page is navigated from a local application or an external application.

Hope this helps,
Jimmy