Suspending a Custom Report

Applies to:  Software

Do you have any custom reports that you’d like to NOT process any longer — but you want to keep the already-processed results available?  An example would be a custom report for a completed campaign.

You can suspend or discontinue an individual custom report without actually deleting it.  With this method, the report stays in the template, its old data can be viewed, but it will no longer process new data.

Add a line to a configuration file that tells WebTrends which custom report(s) should NOT be processed any more.

Step 1.  Know the GUID or ProfileID of the custom report

There are several ways to obtain a custom report’s 11-character GUID, but the easiest is:  From the custom report editing interface, go to the Summary tab and get it from the line “Internal ID.”

Step 2.  Add a line to the appropriate config file

For an individual profile — edit the profile’s *.wlp file, find the [profile] section, and add this line:

reportonlycustomtableprofiles = <GUID>

Globally, i.e. for all profiles at once — Edit the global settings file wtm_wtx.ini, find the [defaults] section, and add this line: 

reportonlycustomtableprofiles = <GUID>

That’s all it takes! 

PostScript and Supporting Details

• If you are suspending more than one report, put a space between GUIDs.
• You might see the GUID elsewhere in the *.wlp file.  Leave it where it is!  Don’t remove anything, just add the line we talked about.
• If you ever re-analyze old data, the suspended custom reports won’t analyze anything.  If you’re going to re-analyze, un-suspend the reports.
• You can find *.wlp files here in your installation directory:  ../storage/config/wtm_wtx/datfiles/
• You can find wtm_wtx.ini here in your installation directory:  ../storage/config/wtm_wtx/
• We agree with that you’re doubtless thinking – it’s odd that the line should say “report only these custom reports” when it means, in fact, “report everything except these custom reports”
• We agree with the other thing you’re thinking — that this should be in the UI!  There are several payoffs for doing this.
  • For end users, it’s a lot less trouble than finding and editing configs
  • For WebTrends, they will be spared the ridicule associated with users seeing a config line that makes no sense at all in the English language
  • For WebTrends, On Demand users who suspend custom reports will be reducing the processing load on the ever-reliable On Demand servers

Tags

.wlp files, config files, discontinue, hibernate, processing, suspend, wtm_wtx

Somewhat Related Posts

Under-appreciated feature: The auto-populated lists in templates

...

Cool custom report: What on-site search terms led to an exit?

...

Under-appreciated feature: The “URL Viewed In Visit” filter

...