cancel
Showing results for 
Search instead for 
Did you mean: 

Fiori Elements Line Chart issues

smith_john
Active Participant
0 Kudos

Hi,

I'm creating an ObjectPage in my Fiori Elements App and I want to have a line chart on the page, for some reason the chart is only displaying one of the dates, not all of the series despite there being 14 records returned in the oData.

Any idea why it doesn't display the rest of the dates and values?

here is my CDS view with annotations

@UI.chart: [    //  for Object Page
    {
        qualifier: 'projectS_Curve',
        chartType: #LINE,
        dimensions:  [ 'timePhasedDate' ],
        measures:  [ 'pvCum', 'evCum', 'acCum', 'etcCum' ],
        dimensionAttributes: [
        {   dimension: 'timePhasedDate',
                 role: #SERIES}],
        measureAttributes: [{
              measure: 'pvCum',
                 role: #AXIS_1,
                 asDataPoint: true
            },
            {measure: 'evCum',
                 role: #AXIS_2,
                 asDataPoint: true
            },
             {measure: 'acCum',
                 role: #AXIS_3,
                 asDataPoint: true
            },
             {measure: 'etcCum',
                 role: #AXIS_3,
                 asDataPoint: true
            }]
    }    ]
define view zdsn_c_projectS_Curve
  as select from znrw_i_projectS_Curve as projectScurve
{
  key projectScurve.projectID,
  key projectScurve.timePhasedDate,
      @UI.dataPoint.title: 'Planned Value'
      @DefaultAggregation: #SUM
      projectScurve.pvCum,
      @UI.dataPoint.title: 'Earned Value'
      @DefaultAggregation: #SUM
      projectScurve.evCum,
      @UI.dataPoint.title: 'Actual Cost'
      @DefaultAggregation: #SUM
      projectScurve.acCum,
      @UI.dataPoint.title: 'Forecast Value'
      @DefaultAggregation: #SUM
      projectScurve.etcCum,
      projectScurve.currency
}

Some screenshots of the data and the resulting chart with the issue...

Accepted Solutions (1)

Accepted Solutions (1)

smith_john
Active Participant
0 Kudos

So it seems, the issue was resolved by flushing the browser cache

Answers (0)