We have an issue that arose when i upgraded flexmonster from v2.4 to v2.6.1

I wrote a POC on flexmonster v2.4 which worked fine.  Then I recently upgraded to v2.6.1 and the csv data seems to be parsed differently, causing values to appear the same.  Attached screencaps of both.  Would like to know if something changed between these versions requiring a code change?  Or is this a known bug?  Thanks.

2 answers

Public

Here is our configuration, also attached our csv file.

var pivot4 = new Flexmonster({
container: “pivotContainer4”,
toolbar: window.editMode,
height: 340,
report: {
dataSource: {
filename: “data/Agent Summary_2018.01.22.10.41.10_AgentTime.csv”
},
options: {
editing: false,
drillThrough: false,
showDrillThroughConfigurator: false,
showEmptyData: false,
grid: {
showTotals: “off”,
showGrandTotals: “off”,
showFilter: false,
showHeaders: false,
showReportFiltersArea: false,
fitGridlines: true
}
},
slice: {
reportFilters: [
{
uniqueName: “AgentCode”,
filter: {
members: [
“AgentCode.[T10]”
]
}
}
],
rows: [
{
uniqueName: “[Measures]”
}
],
columns: [
{
uniqueName: “AgentCode”,
caption: “Total Time in State”
}
],
measures: [
{
uniqueName: “Connected”,
aggregation: “none”,
},
{
uniqueName: “PlacedOnHold”,
aggregation: “none”,
caption: “&nbsp&nbspPlaced on Hold”
},
{
uniqueName: “LiveConnect”,
aggregation: “none”,
caption: “&nbsp&nbspLive Connect”
},
{
uniqueName: “Waiting”,
aggregation: “none”
},
{
uniqueName: “PreviewDialWait”,
aggregation: “none”,
caption: “&nbsp&nbspLive Preview Dial Wait”
},
{
uniqueName: “ACW”,
aggregation: “none”
},
{
uniqueName: “Deassigned”,
aggregation: “none”
},
{
uniqueName: “Paused”,
aggregation: “none”
},
{
uniqueName: “Avg”,
formula: “‘Connected’ + ‘PlacedOnHold’ + ‘LiveConnect’ + ‘Waiting’ + ‘PreviewDialWait’ + ‘ACW’ + ‘Deassigned’ + ‘Paused'”,
caption: “Total”,
type: 5,
active: true
}
]
}
},
licenseKey: “Z7KQ-XCJ7B5-01595R-5B4D1W”
});

Public
Dmytro Zvazhii Flexmonster October 1, 2018

Hello Chad,
Thank you for providing us with the code example. That was really helpful. The behavior in the version 2.6.1 is not correct. We will add the necessary fix to the minor release on ETA Oct22.
Regards,
Dmytro

Please login or Register to Submit Answer