flask-admin

My SQLAlchemy model has a String field that I would like to limit to a few choices. I am wondering how I would be able to create a dropdown for this field in the Flask-Admin interface that would ensure that the db is only populated with one of my choices. If I let the user manually enter these fields, they may spell them incorrectly, etc. enum , form_choices and form_args Your question is about restricting values at the form level, but we can also briefly discuss it at the schema level. A. Restricting Values at the Database Level: enum fields To limit the range of allowable values, the first

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I would like to display only paid orders in my Flask-Admin model list view. Here is models.py: class Order(db.Model): id = db.Column(db.Integer, primary_key=True) amount = db.Column(db.Integer) description = db.Column(db.String) paid = db.Column(db.Boolean, default=False) Here is ModelView for Flask-Admin: class OrderView(ModelView): column_filters = ("paid") admin.add_view(OrderView(Order, db.session)) Filters work fine, but I would like to make this filter default. Or better yet, do not use filters, and only show orders that are output of

In my flask-admin index_view, I am displaying financial information for my rows. I would like to add an extra row, "summary row", at the bottom of my index_view table which sums up all the columns. How can I accomplish this? There's a couple of things you need to do. Provide a custom list.html template and override the render() method for the view. In the render method inject your summary data into the kwargs and in the custom template use the summary data to output appropriate html. You could add the summary data to the end of the existing data table or add it to a separate table, as seen in

I've checked the docs and It's pretty vague how the is_accessible method should be implemented. Here is what the docs of flask admin showed class MicroBlogModelView(sqla.ModelView): def is_accessible(self): return login.current_user.is_authenticated() def inaccessible_callback(self, name, **kwargs): # redirect to login page if user doesn't have access return redirect(url_for('login', next=request.url)) what I don't get though is how do you call it is it automatically called or do you have to call it yourself like this: @expose("/", methods=["GET", "POST"]) def home(self): if self.is_accesible(

I have Users and Roles in my Flask app thanks to Flask-Security. For some roles I would like to hide certain fields in the forms created by Flask-Admin. I know about customizing ModelViews with eg. form_create_rules = ('title', 'file') but while instantiating a ModelView there isn't access to the current request so current_user.has_role(USER_ROLE) can't be called. Is there any other way to achieve this? pjcunningham One way of achieving this is to create multiple view classes and register these view classes against their appropriate roles. See this answer on how to register roles to views.

I'm trying to render a template that contains a DatePicker, but I'm getting a 500 error when I try. For my the code is correct, but it seems that something is failing or I'm not understanding correctly the way to do it. The code is the following: Reporting.py from flask.ext.admin import BaseView, expose from wtforms import DateField, Form from wtforms.validators import Required from flask.ext.admin.form import widgets from flask import request class DateRangeForm(Form): start_date = DateField('Start', validators=[Required()], format = '%d/%m/%Y', description = 'Time that the event will occur',

I was trying to save a project's reviewer using below, and the select field shows correct: # Query the user with Role.id == 4 as reviewer def reviewer_choices(): return User.query.join(User.roles).filter(Role.id == 4) # Build a select field class ProjectView(sqla.ModelView): form_extra_fields = { 'reviewer': sqla.fields.QuerySelectField( label='Reviewer', query_factory=reviewer_choices, )} However, when I was trying to save it, the error occurred: InterfaceError: (sqlite3.InterfaceError) Error binding parameter 8 - probably unsupported type. [SQL: u'INSERT INTO project(...reviewer...)VALUES(..