Community
Participate
Working Groups
Common usage scenario: - User creates a new data control (aggregate or simple) - User builds binding for control which is set on the table - User deletes the control (stuff happens) - User wants to re-introduce a control that uses the existing binding Unfortunately, the GUI does not support this level of interaction. The only way you can do it is to add a new control that is bound to the first control, but that is silly cause now you this extra binding that does nothing. To me, the best solution is a view that displays the available fields (data binding) associated with any table. The user can then drag and drop from that view to the appropriate location in the table. Ideally the view would support modification of the data bindings, similar to the table binding page. Adding this type of GUI would make it significantly easier to understand and take advantage of table bindings. Navigation should be optimized for a tall skinny view. (overlays with palette, library, and data explorer)
This behavior can be achieved through the Change Data Binding, but finding that is a bit unclear. I really think a data binding view would add a lot to the app.
