We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This also happens when attempting to sort IP addresses and Aggregates on their respective list views
Sort prefixes/ip address/aggregates appropriately
500 for FieldError
exception FieldError: Cannot resolve keyword 'prefix' into field. Choices are: _custom_field_data, broadcast, children, created, description, id, is_pool, last_updated, network, parents, prefix_length, role, role_id, site, site_id, status, status_id, tagged_items, tags, tenant, tenant_id, vlan, vlan_id, vrf, vrf_id
The text was updated successfully, but these errors were encountered:
More IPAM field type bugs. This also affects IPAddress and Aggregate objects.
IPAddress
Aggregate
This can be solved with a quick fix to the respective column objects by adding an order_by argument. (See: https://django-tables2.readthedocs.io/en/latest/pages/ordering.html#ordering-by-accessors)
order_by
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Environment
Steps to Reproduce
This also happens when attempting to sort IP addresses and Aggregates on their respective list views
Expected Behavior
Sort prefixes/ip address/aggregates appropriately
Observed Behavior
500 for FieldError
The text was updated successfully, but these errors were encountered: