Depends on what you want to do.
The standard: You have an XML view. Somewhere in your XML view you want to display the product name.
The most simple way is to bind your view to a specific product:
onSubmit: function() {
...
// assuming oData is a variable which holds your model
var sKey = oData.createKey("/Products", {
Id: prodID // Assuming Id is the name of your key property
});
this.getView().bindElement({
path: sKey,
model: "myModelName" // if your model has no name, remove this line
});
}
Then you can access the product name in your view:
<Text text="{myModelName>Name}" />
After binding the model to the view, you can always access the data (and the path) in your code using oView.getBindingContext("myModelName");
If you don't want to display the data but do some calculations: The success callback has two parameters. The first one contains the data.
oData.read(sKey, {
success: function(oResult){
...
}
});
can you expand your answer slightly to explain how you would change the binding on subsequent views? The
onSubmitwillrouter().navTo("AnotherPage")- how do I change the binding path of the "AnotherPage" view?To me this seems like a different question. When doing navTo you should provide the necessary keys as url parameters (
.navTo("anotherPage", { Id: prodID }). Then in your subsequent view you have a handler (Router.attachPatternMatched) where you build a new path (createKeyand/or concatenate strings) and bind it (bindElement)attachPatternMatchedto create anonNavToevent in my second view's controller is exactly the piece I was missing.