Wooot…thanks a lot @rmehta for the Heads up on the merging of the tables since I am sure a lot of users would get a major shock in this merging of tables if they are using HR and have any kind of customization in it.
@rmehta thank you so much for this nice polished product. I tried ERPNext 7 beta in a mobile device, and it requires attention for mis-alignment of ui objects. For example when using the new POS, new and pay buttons are mis-aligned, when proceeded to pay only a part of the ui appears and unable to scroll to view the buttons. Mobility is a great plus for us, please consider this.
Good job!V7 will be more and more exciting if you add a feature on earning and deductions like if it can calculate income tax and overtime based on percentage or formula…it will be more exciting!thanks
Thanks for the update. Looking forward to version 7.
Curious to understand, the 3 points on "technical debt"s you’d mentioned, would they be included in version 7 release?
We have done some customization on Salary Slip Earning and Salary Slip Deductions and looking to see if we need to make changes to them when we take in the latest version. This would greatly help to plan our pipeline as well.
@rmehta With this merge of Earnings and Deductions to Salary Component … how will we separate when creating the Salary structure …as when you create a new one Salary Structure All options on Salary Component show up in both Earnings and Deductions …
I believe there should be a field or tick option for the item to be either Earning or Deduction …this because in my Country Angola we have many for both Earning and Deduction and to create a Structure for a company with more than 100 users will take for ever to separate or move to the right child table.
Hi All,
Don’t know if this was thought as I have raised about not having a Type of Component (Deduction/Earning) due to all fields when creating the Structure being added to both tables and giving a lot of work to remove …
Also have not tried yet the version but already making some changes to our local needs and need to know if on the Component the item is value 0 should not be shown on the SLIP. Kind of a way to have no empty fields shown.