...
If not using realms, you will need to remove or comment out the SQL for the left outer join to the realm table and the WHERE condition filtering to realm by GUID. If you are using realms, replace the GUID in the WHERE clause with the realm you want to display in this portal/report/homepage.
...
Throughout the cycle it is also advisable to review queries assigned and archive any queries which are no longer in use or relevant to ensure the list per user does not become too long.
Quick Custom SQL in Queries
In this particular query, the description field is not available via the standard CJ interface. The query table contains the field, which can be seen via SSMS and manipulated via custom SQL. One fast method of creating a custom sql export for fields like this is to copy a select statement from the SQL and edit it in in the formula window. Although an export is required, it does not affect what is displayed in the field.
...
Copy Existing Portal & Update - Quick Steps
Open the Query List portal you want to copy, and under Edit select “Copy Portal.”
Give it a new name and key and save.
In the new portal:
Edit the view to change the header text to the new program in the View.
In the custom SQL query replace the realm GUID with the correct GUID for the realm you need.
To get the Realm GUID do a quick query for System > Realm and then export the name and GUID to see a list.
Click Embed Portal to get the embed code.
Go to the Reports and open an existing homepage report. Copy the report.
Edit the new Report static text by opening the Static Content block and then viewing the Source. Delete all the old code and replace with the new embed code.