Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
[This post is part of the developer's manual preview published on this blog. You can find temporary TOC here.]
The ability to automatically parse parameter as a GUIDs, does not mean that you can only pass GUIDs as parameters. We can send any kind of serializable data through parameters. Here is an example of sending a simple string text.
SAMPLE 3: Creating a command and passing a general type of string with it
Now, on the View that will receive this parameter you can access its value as follows.
SAMPLE 4: Accessing the value of passed parameter which cannot be converted to a GUID
Notice, how we are using the ParameterKey as a QueryString key. By default the value of ParameterKey is “Param”, which means that in the url parameter will be transferred as follows:
Alternatively, you can decide to override the ParameterKey property on your Views and replace it with something more specific and user friendly, such as “ProductID”.
*** WARNING ***
When overriding ParameterKey, make sure you override it on both View that sends parameter and the one that receives it. Otherwise, the receiving View will not be able to pick out the value of parameter from the QueryString.
*** END WARNING ***
Built in feature of GUID parameter being automatically converted to Guid works for ParentId parameter as well. Let’s take a look at how would a receiving View access the values of the two parameters we have sent.
SAMPLE 6: Retriving the values of Param and ParentId on the receiving View
As for the Parameter, where one is able to override ParameterKey and change its value to something else, the same possibility exists for ParentId. One can override ParentIdKey property, which default value is “ParentID” and change it to something more specific, such as “Store”.
When overriding ParentIdKey, make sure you override it on both View that sends parameter and the one that receives it. Otherwise, the receiving View will not be able to pick out the value of parameter from the QueryString.
Generally speaking, when navigating between Views, methods such as CreateHostViewCommand, NavigateHostViewCommand etc. will have overloads that accept Parameter and ParentId. By specifying those values, you will be sending the parameters to the receiving View.
View all posts from The Progress Guys on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.