This is not an error and is known as nesting. NocTel Insight loves to implicitly create relationships with data. In tabular reports, nesting is shown as one row having multiple subrows fit inside it. For example, if a column is used to indicate a Year, then rows that have the same value for the Year column are condensed under that same year to visually show the relationship. When you export report data to Excel (Crosstab), nesting does not occur - NocTel Insight isn't actually changing the underlying data, just the way it's visually presented to you. Nesting has the benefit of NocTel Insight knowing or having a strong idea of how data rows relate or may relate to one another. This enables faster processing of filtering. An example of this would be a report that lists the following columns in order: Birth Year, Birth Month, Birth Date, Name. Everyone in your data set born in 1990 would be grouped under a big "single" row for 1990. Everyone born in the month of March of the year 1990 would further be grouped together as a big row for 1990, March. If you had filters in place to select what Birth Year, Birth Month, and Birth Day to include or exclude; if you were to exclude all months but March (but keeping all years and days), NocTel Insight would refer to the known relationships it drew and very quickly make the irrelevant data go away. |