This content has been marked as final. Show 5 replies
Have you explored the data protection feature in FDM? You may want to research that option if you are loading to HFM and your metadata is set up to support that feature.
Understood....however, I forgot to mention, this is an Essbase load.
Why do you have a seperate location for the 2nd load? Different mappings, import format etc?
Yes, different import formats and mappings.
In that case you are going to have to do some scripting to achieve this. Take a look at the top of the Essabse Adapter Load action script. This is where the load parameters are set. You could put some conditional code here that always forces the location which needs to be a merge load to use the merge load parameter regardless of what has been selected. If you want it to be more configurable you could use one of the unused integration options to store an override indicator and check that here to determine what to do, this could then be enabled/disabled on a location by location basis.