Bug with Set-RsSubscription about reportingservicestools HOT 10 CLOSED

@ClaudioESSilva have you see it?

from reportingservicestools.

No, I didn't.

@vishyonline can you provide more details?
What is your source and target SSRS versions?

from reportingservicestools.

Thank you both for looking into this.

Both my source are target SSRS is on SQL 2016. Please let me know if you need any more details.

from reportingservicestools.

I get the same error message when i try to save a subscription to disk and load it back:

Get-RsSubscription |  Export-Clixml
Import-Clixml | Set-RsSubscription 

Not shure if this is a serialization issue or is the same thing as above.

from reportingservicestools.

@vishyonline I can't reproduce the error. Can you try to do that one a single instance. Like copying the Subscription from one Folder/Report to another Folder2/Report2.
Do you get the same error? Trying to eliminate variables :-)

Also can be some kind of subscription configuration that I haven't test before.

from reportingservicestools.

I am working on an amendment to the module that deals with the serialization issue by adding an Import-RsSubscription cmdlet that recreates the .ExtensionSettings property so that its a valid object for use with Set-RsSubscription.

PR: #79

from reportingservicestools.

Per PR #79 I've now amended the Set-RsSubscription cmdlet so that it recreates the .DeliverySettings property for a Deserialized object and removed the Import/Export-RsSubscription cmdlets that I proposed adding.

As a result if this PR is merged you should then be able to:

Get-RsSubscription -Path /some/path | Export-CliXML .\somefile.xml
Import-CliXML .\somefile.xml | Set-RsSubscription -Path /some/path

Successfully.

This PR also contains a new New-RsSubscription cmdlet which is useful to anyone looking to create subscriptions from scratch directly with PowerShell.

from reportingservicestools.

I've discovered today that Get-RsSubscription and Set-RsSubscription were not handling Data Driven subscriptions successfully as they require using different underlying SOAP methods. I'm working on fixes for this.

from reportingservicestools.

@markwragg: that's awesome, thank you very much

from reportingservicestools.

It seems like this issue is resolved, so I am going to go ahead and close it. Please feel free to reopen it if that is not the case.

from reportingservicestools.