A customer publishes several datamarts from a single source. Structures are updated in Controller and the user goes into FAP administration and tries to update structures on all datamarts concurrently. Sometimes this will fail because the temporary tables used are named generically and are not specific to one datamart. This functionality would then work properly and would not cause random failures. It can be worked around by running updates sequentially, but users will not want to do this. As sometimes it may work, it will be seen as a bug when it fails.
|Who would benefit from this IDEA?||Any customers wanting to publish multiple datamarts|
How should it work?
Re-code the temporary table naming to make them specific to each datamart (similar to the trickle tables). They should not be named generically as they are currently (eg nrtr_account_temp). Users may receive a series of errors similar to “invalid object name nrtr_account_temp” which causes the affected datamart to fail.
|Priority Justification||This is is inconsistent. Either it should work, or remove the ability to do it. It undermines the applications stability|
|Customer Name||Aramar Solutions|