Skip to Content
author's profile photo Former Member
Former Member

Dealing with too many columns

Hi guys,

We have about 100 customers; we want to look at 24 months both actual and forecast for each customer

Currently we have:

Customers, time, and category in columns

Products and accounts in rows.

This will lead us to around 4800 columns and 300 rows, and then we need some custom calculations on that data.

Is there a better way to handle this?

Thank you

Farrukh

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on May 24, 2013 at 01:26 PM

    Hi Farrukh,

    are you sure that your users will such a report?

    I don't think that so a huge report is useful for the users, ask if they need all this informations at the same moment on the report, if so maybe it's better to have more rows than columns, f.e. putting customers in rows instead of cols.

    I would ask if they are ok to reduce data, f.e. for the oldest months (only the dec value for the previous year) and eventyally to have customers as parameters (and show only one customers in the report) so you will have only 48 cols in the worst case.

    You can also think to create one sheet for every customer using Expansion Across Sheets

    Kind regards

    Roberto

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks Roberto,

      My goal is to make the report as much automated and robust as possible, user should only have to change only time and forecast period at max. This report will be used for years.

      Actually what the end user will be looking at is bunch of custom calculations, i.e. sum of customer a-x…. all of the data pulled from system will be hidden. I'm using local members to do the calculations and not linking them to any Dim (i.e. not using epmmember....). So when they change the forecast period or time it doesn’t affect the local members since they will be changing forecast period every month. Our Fiscal year is different from CY. And no before after property in time dim.

      I was thinking more towards using YTD measure or any other way around it.

      Cannot use YTD since FY doesn’t = CY if I’m not wrong.

      I would be same if I use columns or rows. I'll have numbers instead of letters.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.