CLONING BIMLFLEX METADATA
Updated: Aug 12, 2019
Varigence's flagship product, Bimlflex has a great feature which allows you to "Clone" the metadata from one version to another.
When I first noticed this feature, my initial impression was that you would use it for a couple of reasons:
1. You can clone a version of the metadata in order to keep the current version, while proceeding to develop the solution further. Almost like a form of source control. (I assume this was the original value of the feature).
2. You can clone a version of the metadata in order to experiment with changes, without losing the current baseline.
I have recently discovered another use for this feature that is very powerful. We have a customer where we are implementing BimlFlex, who has 20 instances of the same source system running. Although all 20 contain data from different business units, the database structure is basically the same. The challenge is that we do require some extremely minor differences in the artefacts generated by BimlFlex. This is where the clone feature has really helped us. We have done the metadata mapping once (lets call this the "Master" version), and then we simply clone this version 20 times (which we have automated). As part of the automation we have also applied the minor differences that each instance has, effectively automating the cloning from end-to-end.
At BiTQ we are very excited about this solution and would be happy to discuss it in more detail.