Promotion Request Collector does not allow the usage of the "AsStored" configuration if multiple seeds were selected, in order to prevent collecting the same dependent objects in different Versions. Anyway, many customers nowadays want to rely rather on the AsStored configuration for the Promotion Objects Baseline than on the Latest configuration. And this decission was made disregarding the amount of seeds. So for these customers, the AsStored collection should work as well for multiple seeds. It will be a better idea to utilize an UI-Validator after the Collector step rather than just disabling the AsStored option, to avoid the multiple Version-conflict of dependents. Since most of realworld data structrures would work very well with AsStored combined with multiple seeds without resulting in version conflicts of common members.