Hi Andre,

Roles can be used for this. You can define multiple instances of the reports in the model with the same translation, set up multiple roles for each report that may be used and assign the correct roles to the correct application.

You can also do this using logic. The session variable tsf_appl_alias (Indicium/Universal only) can help with this:  select SESSION_CONTEXT(N'tsf_appl_alias')

This could be used in context logic to show the correct report for the application and hide the others.

Logic could also be used to dynamically load a different report file from disk, via a report property in conjunction with Default logic. While this doesn’t require the definition of additional reports in the model, this may make cloud deployments more challenging where a disk is not readily accessible.

Hi Anne, 

Thanks! I hoped it would be easier. I would prefer the dynamically load if it would be possible to load a different report (file_spec_data) at execution time. For instance by creating a report file in the end application. It would also be nice if you could override the report in the IAM application. 

How are software vendors dealing with this?  

Hi Andre,

The report property is the most used solution for this.

The feature you mention to upload a custom report in IAM is currently on our backlog and candidate to be implemented somewhere this year.