-
Notifications
You must be signed in to change notification settings - Fork 3.9k
fix: set default user value only if enabled #20715
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.
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
Conversation
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing. |
keep alive |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed within 3 days if no further activity occurs, but it only takes a comment to keep a contribution alive :) Also, even if it is closed, you can always reopen the PR when you're ready. Thank you for contributing. |
keep alive |
@surajshetty3416 can you take a look at this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vorasmit Can you share the behaviour after fix? How does it resolve the issue?
It looks like it'll still set same value if "is_default" is checked.
Following is the screenshot of the setting in user permission:
Existing Behaviour:
Issue:
When there is more than one Warehouse field in a doctype, it sets the default for all the fields. Most of the time, it's not supposed to be the same. eg: from_warehouse has to be different from to_warehouse.