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.

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

Feat: Single Settings Page + Default Naming Series for payment Entry #410

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

Madcheese101
Copy link

  • Added a new doctype called POSAwesome Settings for Global Settings across POS Profiles.
  • Added the ability to set a default naming series for payment entries from the POSAwesome (can be set at the new doc - POSAwesome Settings)
  • If the default naming series is set in the POSAwesome Settings (the new doc) then it will use that instead of the default value of the original field in the payment entry doctype.
image

Added a new doctype called POSAwesome Settings for Global Settings across POS Profiles.

Added the ability to set a default naming series for payment entries from the POSAwesome (can be set at the new doc - POSAwesome Settings)
@yrestom
Copy link
Contributor

yrestom commented Dec 5, 2023

How this settings will handle multi company scenario?
Do you think also we should add option for Sales invoice naming series?
And maybe we should add them in POS Profile ?

@Madcheese101
Copy link
Author

  • I am not very sure how this works in multi-company scenarios, however, this gets the metadata of the doctype after applying the property setters from Property Setter fields.
  • You already can select the default naming series for a sales invoice from POS Profile.
  • I decided to add them to a separate settings page since it would be applied for all pos profiles in a company, however, if this doesn't work well with a multi-company scenario then placing it in POS Profile would solve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants