===Reusing & Rebranding Reports===

In some cases, you may want to use a particular report multiple times. This comes up quite a lot when you're doing //shift// reporting, where you'll want the same report for the **morning** shift that you have for the **afternoon** shift.

To save on maintenance, the [[report_list:welcome|reporting addon]] allows you to make a report that runs the Python script from a //different// report.

==An Example==

In this example, let's say we have a daily report called **daily_summary**, and we want to create an alternate version for //morning// and //afternoon// shifts.

We still create a folder and an **info.txt** file for our report, just as we'd normally do.

But instead of adding a Python script, we create a text file called **//<reportname>//.rebrand** (for example, the report 'morning_summary' would have a file called **morning_summary.rebrand**).

In the text file, we put the folder name of the report we **actually** want to use. In this case, the text file would contain...

<code>
daily_summary
</code>

==Report Behaviour==

The Python report itself can contain logic that checks the **report name** to determine which version is being produced. 

This allows the script to behave differently when making the morning vs the afternoon report, if required.