Forum Discussion
Clone and Re-bind with on-prem SQL Server
heit0050 wrote:
Thanks for the reply, Eric! Thanks also for the super helpful sample code on getting the password encryption done to setup the gateway. I'm pretty sure I never would have figured that out on my own.
I had kind of resigned myself to just having our staff create the new pbix file each time. At least the rest of the procress can be autotmated. It just seems like they are so close to letting us 100% automate the system. I'm more just not looking forward to the hundreds of existing clients that'll need to be setup for the first time.
But with the new pbit files it is actually pretty quick. Maybe someday they'll let us go from pbit -> pbix via command line somehow. I did create an "idea" for this if it is something else that others are interested in:
Thanks again for all your help!
You only have to create the pbix file in DirectQuery for the very first time. If the customers have the same dataset and report, the pbix file can be reused. You can import the pbix file and update connection string once a new customer is on board. So maybe 100% automation can be done.
I am endeavoring to mechanize the "clone and rebind" technique with a report that is associated by means of DirectQuery to an on-prem SQL server database. We are an ISV and every client is in their own particular DB. Everytime we on-load up another customer, the objective would be to:
1) Setup another DataSource on the entryway (I've effectively finished this progression)
2) Setup another Dataset to associated with the above DataSource (this is the place I am trapped)
3) Perhaps utilize the BindToGateway to associate these two
4) Use the CloneReport call to copy our report layout and associate it to the new Dataset (I've effectively possessed the capacity to do this on the off chance that I physically make the dataset)
I can't help suspecting that there is a missing enum esteem for the "DefaultMode" property on the Dataset protest. These are the alternatives today:
'AsAzure', 'AsOnPrem', 'Push', 'Gushing', 'PushStreaming'
I feel like we require a "SqlOnPrem" to do what I need? It appears to be certain that it should be possible - since a dataset gets made amid the import of a pbix document that associates with the entryway and after that to the on-prem SQL server.