This is fixed within the 1.5 release. The current solution leaves the destination dataset with no resource name though, so if you want to set one, you'll need to do so manually.
With the bug fixed, I'm closing this ticket, but should you want to make a feature request to be able to specify the new resource name at job time, please do so, and we'll do our best to get that work slated in.
This is fixed within the 1.5 release. The current solution leaves the destination dataset with no resource name though, so if you want to set one, you'll need to do so manually.
With the bug fixed, I'm closing this ticket, but should you want to make a feature request to be able to specify the new resource name at job time, please do so, and we'll do our best to get that work slated in.