5

Table limits at 200 and no work arounds

I have a Klip that references a table with about 2K rows. I just found out that Klipfolio limits you to only show 200 of those rows, but it does show the correct Sums. This is a major limitation especially when the use case is to review information line-by-line. I understand that performance is always an issue, but having an option like infinite scrolling or paging should help overcome that. 

I've read other posts where this was address, but it doesn't look like it was added to the Klipfolio roadmap. What is going to be done to resolve this issue?

8 comments

  • 4
    Avatar
    Jason Verdelli

    I also agree with Alexander. There is no warning to the 200 row limit. If it's mentioned somewhere it's hidden deep in support documentation. The fact that the 200 limit falsely reports the results reference because of the cut off is a major flaw. Any plans at this point to address this issue?

  • 1
    Avatar
    Alexander Dich Jensen

    Hi Jason,

     

    Regarding the sums being correct - would you prefer a wrong sum, which matches the rows shown in the table?

    If so, you can get that by switching out the built-in sum for a custom one, where you do a SUM function using results reference (&) rather than a formula reference(!).

    This sums only the displayed rows.

     

    With that said, we've also had our issues with the 200 row limit. While adding additional filtering, it isn't always viable. It's particularly infuriating that Klipfolio doesn't warn end users (both admins and viewers) more explicitly when data is being cut off.

  • 1
    Avatar
    Charlie Bantoft

    I've just come up against this too.  I'm providing feedback to one of my clients with each row being one line of feedback.  Is there anything in the pipeline to address this?  I have 650 rows of feedback in just one survey.  Thanks

  • 1
    Avatar
    Jason Verdelli

    In response to Zach:

    I understand the current mission of transforming raw data into smaller, actionable visualizations to spot trends, however I'm using Klipfolio as a way to report information across multiple platforms in one location. The users have no access to those other systems, so Klipfolio serves as an excellent hub to all the data coming from those systems.

    Is there a way to paginate results or somehow lighten the load on the system while making the data available? One possible solution would be some kind of "View All Results", and when you click that have the table load all results in a PDF or some other form of output?

  • 0
    Avatar
    Zach Kathnelson

    Hey Jason, thanks for reaching out!  Showing 2000 rows of data in a table at one time could have significant performance overhead.  

    Is there any way for you to segment your data to show it in multiple different tables, instead of one large one?  Or, could you include one or more filters on your table so that all of the data was accessible in a single Klip, however not necessarily at the same time?  Date ranges, product categories, regions, or any other segment could help you split a large data set into multiple smaller ones.  

    Klipfolio is intended to help organizations monitor what is happening in their business right now, and make actionable decisions based on data.  We want to help transform raw data into smaller, actionable visualizations to spot trends; showing large amounts of raw data isn't a core part of our mission, and for this reason we've not added this feature to our roadmap.  

    Happy to chat further to see how we can help out!  Please let us know what we can do.  

    Zach

  • 0
    Avatar
    Dave Ward

    Where is the significant performance overhead? I'm ok if it's on the client side as they will be aware they are waiting on a large table of data. Otherwise, I've never had a problem querying a few hundred or few thousand rows of data. It would be nice to have the option.

  • 0
    Avatar
    Javier Hernández Pescador
    Don't we have a solution yet for this problem?
  • 0
    Avatar
    WENDY GUERRERO

    Hi,

    We are having the same problem. The client would not mind the loading time as long as it would be all the correct data in one place.

Please sign in to leave a comment.