Compound Custom Fields in Intelligent reports templates between projects

Compound custom fields are specific to each project and have no dependence on report templates accessible in said project. If the compound custom fields in one project are different from another, then the report template simply won't have the same fields it is reaching for accessible to it. As far as I am aware, there are no internal checks for which fields are accessible to a report when it is copied to another project. Additionally, the system would have no way of knowing which compound custom parameters that do exist are the ones you want to use. You basically have 3 options here. 

1. Add the compound custom fields to the project manually (making sure the names are EXACTLY the same)

2. Go through the report template and replace those those fields with appropriate ones that already exist in the project manually

3. A mixture of the two above

I hope they eventually make this a bit less clunky, but I expect it would be a total rework of the current hierarchy so my hopes aren't high. To avoid this problem in the future, you can make sure to add some fields to all projects and use those for report templates instead of fields that aren't universal.

Compound custom fields are specific to each project and have no dependence on report templates accessible in said project. If the compound custom fields in one project are different from another, then the report template simply won't have the same fields it is reaching for accessible to it. As far as I am aware, there are no internal checks for which fields are accessible to a report when it is copied to another project. Additionally, the system would have no way of knowing which compound custom parameters that do exist are the ones you want to use. You basically have 3 options here. 

1. Add the compound custom fields to the project manually (making sure the names are EXACTLY the same)

2. Go through the report template and replace those those fields with appropriate ones that already exist in the project manually

3. A mixture of the two above

I hope they eventually make this a bit less clunky, but I expect it would be a total rework of the current hierarchy so my hopes aren't high. To avoid this problem in the future, you can make sure to add some fields to all projects and use those for report templates instead of fields that aren't universal.