I have a map/reduce that I want to specify a saved search for as a script parameters. When I deploy to a specific account, i get an error that the saved search is an invalid key. My deploy.xml defines orders for deploying objects so this should not occur at all as the search is being created before the scripts. Is using saved search not supported? The search IS getting created by SDF correctly. I've also tried deleting the script deployment/records and the saved search and letting SDF deploy it all incase there's an APP ID conflict but still get the invalid key error.

What role is your M/R executing as? I can read, I swear.

Does the Role you're using for deploying have access to the Saved Search? Is the Saved Search being created as

private

? I find SDF's handling of Saved Searches generally to be a gigantic pain; we went so far as to remove them all from our SDF project.

@creece you can try adding the search to your hiding.xml file and unhide it. I was getting similar errors and this worked for me. Hopefully it will for you.

I just came across this thread. @creece was your issue resolved? and thank you for giving me a nice way to organize the custom objects.

@NickSuite i wound up just leaving it out and making it a manual step. I haven't tried adding a saved search back in as a script parameter anywhere (which is the root of the issue). For my particular case, it wasn't that important that a value be populated in this saved search field. No problem on the structure. I'm sure there's a few variations out there that people have been using that may be useful.