Metadata load from Data Management fails for Replace in Import and Export modes
Summary:
Metadata load from Data Management fails for Replace in Import and Export modes, it works for Replace and Merge when executed from Pipeline. Error is 'Plan type custom does not exist'. How does the export mode of replace affect this when it is able to identify the same plan type in Replace/Merge alone?
Also the Rule when executed from REST or Pipeline prompts for Import and export modes, Start Period and End period as mandatory params but on manual execution it prompts only for Import mode , Start and End Period but not for Export mode? Why these params are not common across REST/Pipeline and Manual execution?
Tagged:
0