The IG isn't intended for use with “large amounts of data”.

why not?

You can do this by fixing the grid to a region instead of a page in Attributes>Heading and setting the height of the region to whatever suits your page layout. The horizontal scrollbar always appears at the bottom of the region. Set Pagination>Type to Scroll.

I don't agree with the comment that IG is not intended to be used with large amounts of data. It depends what you mean by ‘large’, but in this case, talking about the width of the report, I have many examples where the grid has to be very wide and also can have thousands of rows. I have never seen anywhere else that it should only be used for small data sets.

It is intended as a light-weight grid with a bunch of features for small datasets.. it's not intended to work with hundreds of columns and millions of rows, c'mon.

But even a light-weight grid can have up to 8 columns that should be easy to work with. Why is it that you don't want to move the scrollbar to the pagination area that is fixed when scrolling?

It's not up to just me by far - but still, this can be done already and doesn't need to be baked into the product, imo.

Example grid with at least 35 columns and over 3,000 rows. Scrollbar always visible at the bottom of the region.

Purely from a customer support standpoint, why on earth would you fight against something that so many of your users clearly want.  Doesn't make sense.

The IG isn't intended for use with “large amounts of data”.

I also take issue with this. IG was definitely designed and intends to deal with large amounts of data. If this were not true then we wouldn't have implemented virtual scroll pagination and flyweight editing pattern. 

But just what “large” means is subjective. 100+ cols should be fine but maybe a usability issue to think about. 1M+ rows probably not because of client side memory use but because of virtual pagination it has a far better chance than any other APEX report. It can easily do 1000+ rows. 

But no matter what large means to you we can agree that it can easily be more rows/columns than will fit on the screen thus adding scroll bars.

However I have made my opinion clear in my blog, sample apps, and, community form that this is not an IG/IR issue but rather a theme issue. See my solution in IG Cookbook page 25 Wide Report.

I do not think that a floating scroll bar is a good idea. I do think that a fixed height region that dynamically adjust to available window size is a good idea.

As you state, there is a difference between what people consider “large amounts of data”. Try 1,000+ available columns. Bad experience. Bad UX, you name it. 1000+ rows is not “large amounts of data” but Millions sure is. Not a good approach to use an IG for wide reports with millions of rows. Call it what you want.

Idea closed as duplicate for the idea referenced. Whether IG or IR, like it or not, the decision is similar for the same reasons.