Be able to have multiple imports of saved view to module

andrewtye

As part of the model cycle have an import which takes from model A and imports to model B but for the first run it's only half the line items and then for the second run it's the whole set. Essentially the second half of metrics are in flux and the end users don't want them updated.

What we have to do is go in and adjust the import action accordingly as required and clearly we could also have a separate saved view in the source model but it would be really great if it was possible to reuse a saved view → module linkage and it not update the existing import either by doing a "copy action" or by doing a "don't overwrite" option.

This would then reduce the amount of saved views needing to be maintained and also the albeit small amount of production model interaction by developers.