My binding blogs seem to be some of the most popular content on my blog. It is also one of the topics I get the most questions about. So I’ve been thinking, how do I make it easier for people to understand? And I thought “what about a decision tree?”. So I created one…
Scope and Limitations of the Decision Tree
Before using the decision tree please take a note of the following:
- The decision tree will help guide you to the right data selection and data serialization functions only – not data manipulation functions.
- You will need to understand the fundamentals of a binding before proceedings. You can read more about data selections and data serializations here. For a walk-through of them please check out the relevant blog from here.
- This is simply a guide and there might be other combinations of data selection and data serialization that work as well.
- The decision tree will not cover all possible use cases including but not limited to nested bindings.
- Just because you can use bindings as illustrated in the decision tree, please consider using the UI-friendly binding options – pages, component widgets or, the “baked-in” interactions directly in the widget.
- For additional help with the syntax feel free to use the advanced editor.
I haven’t tried out all the results in the decision tree, so if you find an error, please let me know in the comments below. I’ll then try to adjust the decision tree and update this blog with a new version.