How to make certain column in primefaces datatable to be dragable - jsf

I need dragable feature to be applied on certain columns of the datatable. As of now when we use dragable datatable its applied to all columns. Can anyone have any idea how to achieve this.

Related

How do I disable PrimeFaces column overflow hiding within a datatable

I'm currently working with a <p:dataTable> (from PrimeFaces 5.2) with many columns, and as I approach the width of the datatable's parent container, PrimeFaces starts hiding columns; unfortunately it seems to be the most important column (first on the left, a <p:datePicker>).
I've tried assigning that column a priority="1" and the other columns priority="3" as described on the ShowCase site, but the first column is still hidden.
In addition to just nesting the datatable within a <p:tabView> I've tried making the dataTable scrollable via scrollable="true" and assigning a width, or also try wrapping the datatable within a <p:scrollPanel> but the column was still being hidden in either case.
When I remove enough columns (from the right-most of the table), the hidden column will again reappear.
I'm interested in a solution that is not tied/hard-coded to a specific column, as I've run into this same issue on the 2nd column, or 3rd, depending on the resolution or browser width...I want to be sure that my users are seeing everything that was coded into the datatable, even if that means they have to scroll, rather than having a dynamic function suppress values unbeknownst to the user or myself.
Basically, I recommend to add tableStyle="width:auto" to a <p:datatable> so that you do not have to deal with the single columns width. Primefaces will handle it for you dynamically depending on the length of the column entry.

How to make Selection Disable/Enable dynamically in DataTable

How can I make the Primefaces p:dataTable selection Enable or Disable or Multiple or Single dynamically based on some condition.
There is disabledSelection attribute of p:dataTable in PrimeFaces 5+. Using this attribute with proper data table update, enable/disable row selection can be reached.

Scroll to a Specified Row in an Extended Data-Table Using AJAX4JSF and/or JSF/RichFaces

I would like to scroll automatically to a given row in a JSF/RichFaces Extended Data-table (rich:extendedDataTable). Ideally, I would like to use two extended data-tables with vertical scrollbars on both.
When I select a row in a first table the corresponding row gets selected in the second table (do this from the managed bean, by playing with the selection attribute of my table).
The second table then scrolls automatically so that the selected row becomes visible, even if hidden.
The solution should not involve the rich:datascroller, but instead use the out-of-box JSF/RichFaces vertical scrolling.
Thanks for helping!
Matthieu
So well I finally developed my own kind of scrollable datatable, playing dynamically with the "first" and "rows" tags of both the datatable and collapsible subtable.
Relevant values are dynamically computed by the managed bean.

Moving the selected rows from one DataTable to Other inPrimeFaces 3.2

I'm new to PrimeFaces. In my project, I have a requirement to show 2 tables where user can select the rows and move to other datatable. In order to achieve this, can I use PickList component? If so, does it allow me show data with multiple columns. Any reference example is appreciated.
i dont think you need to use picklist. you can acheive this using primefaces drag and drop.
check it here
Drag and Drop components have special integration with data components. you can integrate drag and drop components with your datatable.
lemme know if this helps ...:)

Primefaces row grouping for repeated values

Is primefaces able to group rows dynamically in a dataTable like icefaces does?
<ice:column groupOn="#{employee.region}">...<ice:column>
<ice:column groupOn="#{employee.office}">...<ice:column>
Unfortunately expansible row grouping does not fit to me!
In PrimeFaces before 6.0.11 this is not possible. In 6.0.11 or 6.1 and up it works. It was implemented as a feature request: https://github.com/primefaces/primefaces/issues/39

Resources