In the Previous vs Current report, there were a number of multidrill options that were not needed by my customer. I commented out the unwanted drill downs in a_get_drill_down_meas.fex. It looked good.

Then when I drill into the dimensions and select a specific lower level a dimension, the full multi-drill menu appears again showing all the options I had commented out.

How do I limit this when drilling in from the left hand tree?

I just tried this out and the changes took on the left-side drilldown as well as on the top level report.

My guess is you need to configure your browser to get new pages from the cache each time you go to the server. You probably have an old version of that drill result - with more menus - in your local browser cache.

Either that, or you need to provide a more precise click by click reproduction of the behavior you're seeing.

The browser is IE 6. I changed the setting to refresh on every visit to the page. I cleared out all temporary files. I checked the server to be sure expire_reports is equal to 1.

The problem is still occuring. I believe it is a caching issue, but not sure how to resolve it.

Or, it's possible I misunderstand what you're reporting.

Click-by-click, exactly how could I reproduce this?

First, comment out one of the drill down options.

Run current vs previous report. Without drilling into any of the dimensions, click on the name of one of the measures and see the drill down report list with the missing option. Then drill into a dimension (location) and let the report refresh on the right hand side showing the breadcrumbs of where you drilled. Click on a measure name again and see if the option is still missing.

Dang. I did your exact repro and it doesn't repro. It works perfectly. I hate it when I can't break things.

Anyway, the assumption I'm (still) making is that you mean the "measures - previous vs. current" report and not the "objectives - previous vs. current" report. Am I right? If not, I'll try that other one, too.

The other assumption I'm making is the problem is independent of *which* multi-drill you're commenting out. The include file has some pathways in it. So which options are you commenting out?

OK, I think I found it. When customizing code for a customer, I always copy the program to another directory before changing it. This directory sits at the top of the app path (before mainstreet). I left the original name in place. Somehow it was picking up the original program when drilling it. I went out to mainstreet and renamed the program I modified to a_get_drill_down_meas-orig.fex and it cleared up the problem. Any idea why this would be necessary?

Thanks!

Aha. Makes sense.

In the particular contexts you discovered, the tree is loaded from the web server, and in the HTML we force the app-path to our folder. However, the first time the report runs it's not off the tree.

This would only cause problems in a name collision situation - such as you found.

Best practices say any customized code should be uniquely named to avoid these, either by renaming the original module to prevent it from being accidentally found. You fixed it by adhering to that best practice, as all good developers do.