The good part about working the the Thinkwise platform for quite some years now is that you build up a lof of reusable parts. However it is very difficult to extract reusable parts from a model, export it and import it as a reusable base model.
Two main ideas:
- Most basic, export model for environment A and import in into environment B, if the base models are not available in the new environment import fails. Also when a base model has a different name. In this case in both environments the date_helper was downloaded, however in one it had a different name.
- More powerful, and if you really want to become a 10x developer (
@Arie V ) is to have the ability to export a part of an existing model to reuse in a different model or even better create a base model of it. Now it's pure manual labor to or remodel the things you want in a new model, or copy the whole model and clean up the parts you don't want. All manually.- Being model and relation driven, a nifty solution to pick a table, a menu item or starting point as such, and determine everything you need to export everything that relates to it.
Another thing I would love to see is to have a function/procedure repository. The overhead of the Thinkstore model download is too large. You end up with 50 base models, all with 1 or 2 functions/procedures etc.. that do generic stuff. Would be great if for example the functionality/subroutine parts could talk with a type of github repository that could be forked. No need to import full models, just reusable pieces of SQL code.
