We always have the "Input Measure Values..." choice on the multi-drill menu that drops down when we click on a Measure name on any PMF view.

Looking at the code "a_get_drill_down_meas.fex", it has

-IF (&SHOW_MEASURES_ENTRY EQ 'N') THEN GOTO :A_GDDM_SK3 ;
DRILLMENUITEM=&MD_MEASVALINPUT.QUOTEDSTRING, FOCEXEC=measures_entry_frames( \
SCORECARD_ID = &SCORECARD_PARM \
TIME_RANGE = '&TIME_RANGE' \
RECORD_TYPE = RECORD_TYPE \
PM_MEAS_SRC_MEASURE_SERIES_Edit = &MEASURE_SERIES_FIELD), TARGET=&PMF_DRLL_TGT,

-:A_GDDM_SK3


Should this logic prevent the menu item to be displayed when we clik on a Measure that isn't User Enetered, but Loaded?

Thank you,
Endre

This message has been edited. Last edited by: Endre,

No, this would only let you globally show or hide the menu item. That flag is set at the top of the a_get_drill_down_meas FOCEXEC, so it's either always-on or always-off. You cannot use a single Dialogue Manager vars to do this because it is not sensitive intrinsically to the DB value; it's not data-dependent.

We haven't tested if WebFOCUS Conditional Styling can be used with multi-drill menus, but maybe that's the way to do it? Could you use conditional styling to hide or show a menu item depending on the measure's being loaded or user-entered? Conditional styling would let you create a test of the measure's acquire-type and style the column to include the menu item if it's user-entered. (in PM_MEAS_SRC the column is RECORD_TYPE; if RECORD_TYPE ='U' then it's user entered, if it's 'L' it's loadable).

Try it out and let us know if this works for you; if it does maybe we could integrate it into PMF. It would definitely be better if the menu would only appear when needed - right now if you select the menu item on a loadable type measure you get a pop-up telling you it's not user-enterable.

Note that in the near future we're splitting the loader up so that you will be able to enter some of the data and load other data. For example you could specify that targets are user-entered (and with security they could only be entered by planners) and actuals are loaded. Relatedly you'd be able to specify that actuals are loaded from one place and targets from another. This project is planned for 2010.

thanks

Thank you,
Since the pop up ( that tells us that it is not user enterable) works, we might just stick with it for a while. But on my own test environment I will try to use the (PM_MEAS_SRC / RECORD_TYPE; if RECORD_TYPE ='U' then its user entered, if it's 'L' it's loadable) route.

Splitting the measure into loaded and user entered will be great. We always have actuals in source systems, but not always the targets.

Take Care
Endre