Choices option is not working, you can check below:

TRAINING_TYPE_CHOICES = (
    (TRAINING, 'TRAINING'),
    (MATCH, 'MATCH'),
    (REGENERATION, 'REGENERATION'),
    (REHABILITATION, 'REHABILITATION'),
    (OTHER, 'OTHER'),
)

training_type = models.PositiveSmallIntegerField(choices=TRAINING_TYPE_CHOICES, default=1, null=False, blank=False)

DataField and TimeField Widget Problem. Widgets are wrong (date widget in time input)

training_date = models.DateField(null=True, blank=True, default='2020-05-21')
start_time = models.TimeField(null=True, blank=True, default='00:00:')
end_time = models.TimeField(null=True, blank=True, default='00:00:')

To be checked with Django Datta Able:

https://github.com/app-generator/django-datta-able

Hello

Thank for the app, i couldn't make it work with my model, it seems like the app doesn't work with ForeignKey field or M2M fields

The issue appears in the view.py

for field in headings: filter_options = filter_options | Q(**{field + '__icontains': search_key})

i've tried to override the logic but couldn't make it run with my FK models

Thank you!

Using the model to build the database, I specified one of the fields:
photo=models.ImageField(upload_to="images/", blank=True, null=True)
but when adding a record, it is impossible to add a file or an image
is there any solution to this problem or should I deal with the code myself and rewrite some points?

I think it is better to have a custom data table and not use bootstrap or simple-datatables
So, I implemented an initial table if you like it, inform me to complete it.

Suggested in yTube

I would like to share feedback for further improvement:

• Allow for "default" fields that need to be shown in the list view. In my situation, not all fields are required to be shown in the list view, only when the detailed view is clicked they should be shown;
• Make default filters set - Similarly to the above one, default filters will be very useful, accomplishing the same thing as not showing not needed data;
• Unnecessary JS - There are a couple of places where JS is used to load data as well as certain fields. This makes it a bit more complex to read/understand than feeding the data in the actual Python template. e.g. The heading for the model name on the top of the page is configured with JS, but it's provided in the context of the view anyways, so a simple {{model_name}} will accomplish the same thing.

Hello @Mortrest

The current version of the library works as a separate page with its own links and actions.

We need to find a solution to provide the same features as a widget where the user can embed this dataTable element in any page.

The NEW requirements:

• Handle any model enabled by Config (as it is now)
• Datatables View can be embedded in any page
• All Exports available

Here are some other packages that look more or less similar:

• https://pypi.org/search/?q=django+datatables (PyPi Search)
• https://pypi.org/project/django-serverside-datatable/
• https://pypi.org/project/django-datatables-serverside/
• https://pypi.org/project/djangorestframework-datatables/

Let's brain storm around these new requirements and let's go.

ty!