Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Can't save Agent form with Agent specialties #151

Closed
garrettgirard opened this issue Jul 7, 2015 · 4 comments
Closed

Can't save Agent form with Agent specialties #151

garrettgirard opened this issue Jul 7, 2015 · 4 comments
Labels
1 - Bug Incorrect behavior of the product impact:unknown pri:normal Should be resolved before releasing but may be deferred to the next release res:fixed (deprecated) Problem has been fixed
Milestone
v7.3.1

Comments

@garrettgirard
Copy link

In KUHerps - master

For databases using Agent Specialties, if you add Agent Specialties to the Agent form and attempt to save you will get an error.

Error message:
IntegrityError at /api/specify/agent/
(1048, "Column 'OrderNumber' cannot be null")
@garrettgirard garrettgirard added pri:normal Should be resolved before releasing but may be deferred to the next release 1 - Bug Incorrect behavior of the product labels Jul 7, 2015
@garrettgirard garrettgirard added this to the prerelease milestone Jul 7, 2015
@benanhalt benanhalt modified the milestones: prerelease, next-release Jul 10, 2015
@benanhalt benanhalt modified the milestones: prerelease, next-release Oct 1, 2015
@benanhalt benanhalt modified the milestones: prerelease, next-release Apr 6, 2016
@benanhalt benanhalt removed this from the prerelease milestone Mar 17, 2017
@yvonneekanim
Copy link

I tested this on a new database and I seem to be getting a different error message when I add agent specialties. I can save the agent form otherwise.
agentspecialties

@garrettgirard
Copy link
Author

Yvonne and I just went back and looked at this, and it's still the same error.

@garrettgirard garrettgirard removed qa:n/a todo:verify Needs Verification labels Jul 6, 2017
@benanhalt
Copy link
Contributor

Can we check if this is still happening? I think it's possible this was the same problem as #460.

@benanhalt benanhalt added the todo:verify Needs Verification label Feb 19, 2019
@yvonneekanim
Copy link

This is fixed. Specialties can be saved with no error

@benanhalt benanhalt removed the todo:verify Needs Verification label Feb 19, 2019
@benanhalt benanhalt added this to the next-release milestone Feb 22, 2019
@benanhalt benanhalt added the res:fixed (deprecated) Problem has been fixed label Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - Bug Incorrect behavior of the product impact:unknown pri:normal Should be resolved before releasing but may be deferred to the next release res:fixed (deprecated) Problem has been fixed
Projects
None yet
Milestone
v7.3.1
Development

No branches or pull requests
3 participants
@benanhalt @garrettgirard @yvonneekanim