You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- this leads me to /en/456-admin/auth/group/add/?_to_field=id&_popup=1
? is it correct that the "department" i a "group"?
fill the fields with examplary data like that and save:
This results in this:
click save at the request web form. This results in an error message and an empty value of the department field.
FYI:
the department field is not part of the requests model but the inherited model Base1. There department is defined like this:
department = models.ForeignKey(
'auth.Group',
blank=True,
null=True,
on_delete=models.CASCADE,
verbose_name=_("Department"),
related_name="%(app_label)s_%(class)s_department_related",
)
is it even required to have department as an mandatory field in request model (in Base1 it is marked as null=True)?
PS: maybe it is an MSSQL problem? MSSQL is not capable of doing database-side regular expressions. I already transferred one on python side to make it compatible. Maybe department also uses regular expressions to filter?
PPS: I think it is a permission problem. I had a superuser with blank groups and permissions. Now I added every permission to my user and now I see something in the departments dropdown.
The text was updated successfully, but these errors were encountered:
No. Group is a parent model for the Department. Department should be added as Department, not a Group.
Please read here how to add Departments.
And one more thing. You are trying to add Request using admin site and being in superuser role. To do this, you must first select the department for which you want to add a Request.
It is better to use CRM site for this being in sales manager or operator role. Then everything will be easier.
There is something odd with the "department" field in the Requests model.
information about test parameter:
How to reproduce the bug:
? is it correct that the "department" i a "group"?
This results in this:
FYI:
the department field is not part of the requests model but the inherited model Base1. There department is defined like this:
is it even required to have department as an mandatory field in request model (in Base1 it is marked as null=True)?
PS: maybe it is an MSSQL problem? MSSQL is not capable of doing database-side regular expressions. I already transferred one on python side to make it compatible. Maybe department also uses regular expressions to filter?
PPS: I think it is a permission problem. I had a superuser with blank groups and permissions. Now I added every permission to my user and now I see something in the departments dropdown.
The text was updated successfully, but these errors were encountered: