Zero Suppression - Fed Numeric Values Being Suppressed

[mystrJeff]

Hi All,

TM1 Version: 10.2
Issue: When selecting only numeric measures in a cube and turning on zero suppression, TM1 gives the "No values available" popup box. However, when I "Check Feeders", the measures are fed. When I add a String measure in the subset and turn on zero suppression, all values appear.

In the Cube Rule, SKIPCHECK, FEEDSTIRNGS are both on. This happens for any numeric value in the cube, but as an example of one of the rules being used:

Code: Select all

['yrs_elig']=N: DB('cfg_emp_inpt', !fy, !emp, 'yrs_elig_inpt');

Where "yrs_elig_inpt" is a manually entered field and is feeding into the current cube.

Here are the settings being used in the tm1s.cfg file:

Code: Select all

##  security ##

IntegratedSecurityMode=2
ServerLogging=T
AuditLogOn=T
AuditLogMaxFileSize= 100 MB
AuditLogUpdateInterval=60

GroupsCreationLimit=10
UseSSL=T

## perf ##

ParallelInteraction=T
PersistentFeeders=F
ForceReevaluationOfFeedersForFedCellsOnDataChange=F
ReevaluateConditionalFeeders=F

MTQ = 2
AllRuleCalcStargateOptimization = T
CalculationThresholdForStorage = 30
AllowSeparateNandCRules = T


## standard ##

Language=eng
Protocol=tcp
NetworkFrame=   
SaveTime=   
DownTime=   
RuleTraceOn=   
RunningInBackground=T
MaximumViewSize=4000

Has anyone experienced this before? Am I missing a setting in the tm1s.cfg file?

Thanks for your time!

[qml]

Could you please post your feeder statement too? Better yet, could you post your entire rule file (or both rule files if this is an intercube rule) and the dimensionality of your cube(s)?

[mystrJeff]

Cube in question:

Code: Select all

  ################################################################################
  ## fy15_rpt_emp
  ################################################################################
  SKIPCHECK;
  FEEDSTRINGS;
  ################################################################################

  []=S: IF( ISLEAF=0, '', continue );

  ['emp_name']=S: DB('cfg_emp_inpt', !fy, !emp, !fy15_rpt_emp.msr );
  ['emp_is_elig']=N: DB('cfg_emp_inpt', !fy, !emp, !fy15_rpt_emp.msr);
  []=N: IF( ['emp_is_elig']=0, 0, continue );
  
  ['yrs_elig']=N: DB('cfg_emp_inpt', !fy, !emp, !fy15_rpt_emp.msr | '_inpt' );
  ['ttl_sal']=N: DB('cfg_emp_inpt', !fy, !emp, !fy15_rpt_emp.msr | '_inpt' );
  ['sal_incrs_pct']=N: DB('cfg_emp_inpt', !fy, !emp, !fy15_rpt_emp.msr );
  
  ['sal_bonus']=N: ['ttl_sal'] + ( ['ttl_sal'] * ['sal_incrs_pct'] );

  ########################################################

  FEEDERS;
  ['emp_is_elig']=>
      ['emp_name']
    , ['sal_bonus']
    , ['sal_incrs_pct']
    , ['ttl_sal']
    , ['yrs_elig']
  ;    
  

Cube the data is pulling from:

Code: Select all

  ################################################################################
  ## cfg_emp_inpt
  ################################################################################
  SKIPCHECK;
  FEEDSTRINGS;
  ################################################################################

  []=S: IF( ISLEAF=0, '', continue );

  ['sal_incrs_pct']=N: DB('cfg_emp_inpt', !fy, !emp, !cfg_emp_inpt.msr | '_inpt' ) \ 100;
  
  ########################################################

  FEEDERS;
  ['emp_is_elig']=>
    DB('fy15_rpt_emp', !fy, !emp, !cfg_emp_inpt.msr);
  ;    
  

cfg_emp_inpt is mainly a user input cube. Each cube has the years, employee ID, and measures dimensions.

The feeder is just a block feeder. "emp_is_elig" is a numeric flag, either 1 or 0.

Thanks for your time.

[qml]

You have problems right at the top of both of your rule files. If you use FEEDSTRINGS it needs to be on the first line, before SKIPCHECK. It's right there in the documentation for that keyword.

Change that and it might start working for you. If not, we'll have to dissect your rules a bit more, especially the relationship between the dimensions cfg_emp_inpt.msr and fy15_rpt_emp.msr.

[lotsaram]

You have problems right at the top of both of your rule files. If you use FEEDSTRINGS it needs to be on the first line, before SKIPCHECK. It's right there in the documentation for that keyword.

Documentation might have changed. I seem to recall reading that Feedstrings can be the first OR second statement in a rule and it doesn't matter if it comes before or after Skipcheck. I have Skipckeck first in all my rules (without any apparent ill effect).

[mystrJeff]

You have problems right at the top of both of your rule files. If you use FEEDSTRINGS it needs to be on the first line, before SKIPCHECK. It's right there in the documentation for that keyword.

Change that and it might start working for you. If not, we'll have to dissect your rules a bit more, especially the relationship between the dimensions cfg_emp_inpt.msr and fy15_rpt_emp.msr.

Unfortunately this did not change anything. Thanks for the suggestion though!