Does paid support provide better documentation?

[kidvid]

We're having a hell of a time getting the lazy, paginating, scrollable datatable to work with multiple selections. Our analysis is that if you turn on all of these options: paginating, lazy, scrollable and multiple select, then it's really difficult to work with the way we have it set up. We have noticed some graphical glitches with the top paginator div: because it's inside the table it moves when you scroll horizontally; the bottom paginator DIV is outside of the table and does not suffer from this glitch. There is also an easy way to get the top header to become out-of-alignment with the data columns beneath it.

Also, the setSelected method is really hard to use if you have lazy pagination with multiple select if the user selects and unselects rows, and goes back and forth between pages. It's really hard to tell what's going on with the selections that were de-selected by the user between page loads. There really needs to be a setSelected method in addition to a setDeSelected method, or the setSelected method should have a few arguments: one for new selections, one for existing selections that weren't altered, and one for previous selections that were unselected by the user.

The thing is - we can't tell if we're using it right because the guide, or the showcase, has very little example code on how to use a lazy paginating multiple selectable datatable, which I would imagine is is probably the most complicated component to get working correctly in the framework.

Either we're not using this right, or it's buggy if you try to do some heavy lifting with it, but we're not sure which. How would paid support help us?

[cagatay.civici]

Documentation is same for community and enterprise. If you get commercial support, you post your questions in private jira and get one-to-one assistance.