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
Currently, the system has a generic Naming Settings doctype that does not differentiate between Companies.
Hence, currently, any transaction that gets created is in general sequential order even if the companies are different.
Eg:
Naming Setting Serial for Sales Invoice : SINV-###
Some companies/organizations may find this useful but a considerable few other companies will find this difficult to work with.
Hence, we would need Company selection in Naming Settings to specify the company and the transaction the Naming Sequence is applicable for.
Secondly, working with the current sequence is also a major challenge when a new company is added to the existing company and both of them are expected to have same sequence or different sequence while also maintaining the sanity and tracability.
The text was updated successfully, but these errors were encountered:
Currently, the system has a generic Naming Settings doctype that does not differentiate between Companies.
Hence, currently, any transaction that gets created is in general sequential order even if the companies are different.
Eg:
Naming Setting Serial for Sales Invoice : SINV-###
Companies:
Reliance Insurance
Reliance Petroleum
Invoice Number || Company
SINV-001 || Reliance Insurance
SINV-002 || Reliance Petroleum
Some companies/organizations may find this useful but a considerable few other companies will find this difficult to work with.
Hence, we would need Company selection in Naming Settings to specify the company and the transaction the Naming Sequence is applicable for.
Secondly, working with the current sequence is also a major challenge when a new company is added to the existing company and both of them are expected to have same sequence or different sequence while also maintaining the sanity and tracability.
The text was updated successfully, but these errors were encountered: