Armin Winkler 
Has successfully completed the online course Introduction
Has successfully completed the online course Intermediate (200)
Has successfully completed the online course Advanced (300)
Has successfully completed the online course Basics (100)Hi Patrick,
would you be able to share your example application once again so we can make some adjustments in there and provide it back to you? I am afraid I have already permanently removed it from our Simplifier instance since I was of the opinion that your problem had been solved. Here’s an upload folder once again, so I can access the transport file and import it to our system. I will immediately remove the folder after you’ve uploaded the file to it:
https://files.simplifier.io/u/d/60f1bb8b3e994153a1f2/ password: uyGLxaZBH33HS497
In general, this is how a data binding should behave when you are templating an aggregation: You add your template item (i.e. a single TabContainerItem widget) to a given aggregation in the UI Designer and then configure your data source on the item’s properties in the panel on the right side of the screen. This data source may e.g. be a variable of a collection type. In a Javascript context a collection type transfers to an array which holds up to an infinite number of objects which again correspond to struct types in Simplifier. Each object may contain several properties / fields that can be used for property bindings inside the data source, i.e. you can then proceed and link a field from the inner struct of the collection to a property of your item or even a widget that is still nested inside your template item.
Now, during runtime of your application, your collection variable that is used as data source for the binding of your template item place within the TabContainer widget, may be manipulated anf for example receive another entry. Via the binding, this should immediately reflect on the UI, i.e. another instance of your template item should automatically created and therefore you’d see a new tab in the UI. Whenever you remove an entry again, the UI should again update and no longer show the respective tab. Such bindings are always two-way, meaning that you could either manipulate the UI part to synchronize changes with your data source (the collection variable) or alternatively, you are also able to manipulate the data source itself and then the UI should update accordingly. For a more detailed description on aggregation bindings, please find the OpenUI5’s reference on it here: https://openui5.hana.ondemand.com/topic/91f057786f4d1014b6dd926db0e91070 (also mind the related articles of the documentation). And this video, which is taken from our Simplifier Intermediate course, shows you how to configure a data source in the UI Designer and also explains the whole process in more detail: https://community.simplifier.io/202-2/
Hope this makes data sources and binding clearer for you. Kind regards,
Armin