SSRS Server Report Variants

Hey,

I would not recommend modifying any IAM tables, that aren’t accessible through the UI, via post-sync scripts etc.

Can you provide some more information about how you envisioned setting this up for different clients? E.g. is this the development environment and are you using a single reporting server for convenience or is it meant to work this way in production as well. Are clients separated by different IAMs or by applications inside the same IAM etc.

I think there used to be a way to change the path of the report being executed through binding a parameter to one of the selectable properties but I know that at least Indicium dropped support for that when all the “local” report types ended up in its file cache because you have to upload the report file itself to the model in the SF these days.

I guess for SSRS reports managed by a server this could still be a valid use case since Indicium doesn’t manage the report files by itself but as I said that doesn’t work at the moment so it would need to be a feature request.

Not that I have any experience in this, but I have to say that could this may be an spelling error? Shouldn't this spell “http://”?:

The error mentions that the request was unauthorized which indicates the user identity that Indicium is running as does not have access to the SSRS reporting server.

If you are running Indicium on IIS this corresponds to the application pool user that was set.

Have a look at https://learn.microsoft.com/en-us/sql/reporting-services/security/authentication-with-the-report-server?view=sql-server-ver15#authentication-types for some more information about SSRS server authentication types.

By default it is set to RSWindowsNegotiate and RSWindowsNTLM which is why the current user of Indicium is used. RSWindowsKerberos would probably work as well but requires more setup. The other two (RSWindowsBasic/Custom) are currently not supported.

Another thing to consider is that credentials for data sources might be overwritten by the user credentials set in Indicium’s MetaSourceConnection or via the pool user credentials that can be set per application since 2023.1: https://docs.thinkwisesoftware.com/blog/2023_1#deployment---pool-user-credentials

As for the URL for the ssrsreportserver setting, that needs to be set to the “Web Service URL” that was configured while setting up de reporting server.

By default the virtual directory for this is set to “ReportServer”:

And “Reports” is the default location for the web view.

So if you would be using the default settings your example URL should have been:

http://reportservice.domain.com/reportserver

Going back to the original issue. If I understand you correctly the desire for having all the different client reports on the same server is mostly for testing/development purposes? If so I guess the easiest way to do this would be to bind a hidden parameter to the “File path” property like I suggested earlier and then select the relative report path on the server based on which application you are currently in (based on the alias or something).

This might still work in the Windows or Web GUI but like I said it probably doesn’t in the Universal GUI at the moment since Indicium doesn’t support that property anymore. So we would have to re-implement it for SSRS server reports, which is the only one it actually makes sense for in my opinion since Indicium manages the report files itself when using the other report types.

@kensonlatchmansing Any updates on this topic? Do you still require support?

@kensonlatchmansing Sorry it took a while to find some time to try and test the scenario you've described above.

Unfortunately, I also could not find a way to use the pool user of an App Service Indicium in combination with a SSRS server. A Power BI server could probably make it work when using a managed identity on the App Service but I did not test this since the Thinkwise Platform currently does not support Power BI as a report type.

Setting the MetaSourceConnection:Username/Userpassword options instead also will not work since the code only seems to override the credentials on each dataset in the report and not the credentials used to authenticate with the SSRS server itself.

So, for the described scenario, the platform would probably need to support configuring a location + credentials of a SSRS server in the model itself. Like how file storage locations etc. can be provided.

This is just a thought since I don't know how complicated the reports are but if they only differ in styling between your customers it might be a lot easier to make those styling options part of the application and send them to the report as parameters. Then you could just include the rdl file of the report using the SSRS (Local) type and allow Indicium to contact the data source directly (assuming all the data comes from the application database).