It would be nice to be able to add a customer account number when creating a new customer as well as just their name. Xero has an option to assign account numbers to customers which is handy when sending out statements as customers can use their account number as a reference when making payment. Right now I have to add account numbers manually in xero once the customer has been created in DEAR.
There is a unique identifier. The customer name must be unique (but it is not case sensitive). Customer codes are a legacy from days of very expensive storage. They are not very friendly, generally speaking ,and in practice I don't have a single client who is missing them (technical users are perfectly happy with the guid provided by the API) which suggests there are good workarounds. When I first started with migrations I suggested appending the customer code of the old system to the customer name e.g. in s, so searchable, but no one was ever interested.
Xero, by the way, treats contact names in the same way as Dear. Xero did eventually add an account code field (optional). I should survey my users to see how many use it ... not many, I think.
The generalised feature request would be for additional attributes to be optionally mandatory and optionally unique. I would like this, particularly being able to make a field mandatory, and I think I already requested this (Unleashed now has 'required' extra fields, but only for products and they are not yet integrated into reporting: Dear is still miles ahead.)
As for payment references, it would be much better for customers to reference an invoice number when making payments, rather than an account code, which wouldn't tell you which invoice is being paid, a funny point when you consider this is a topic about unique identifiers.
This would also be helpful when using your integrated POS and setting up a loyalty program. I could offer a loyalty card to customers with a unique barcode or number sequence that represents that customers account number.
@Tristan Thomas, I agree about solving problems for the market rather than custom specific requests.
However, the heart of the issue here, is that DEAR does not create or use a unique identifier for Customers. Using customer name as the uniqueness constraint prevents it from syncing properly with QBO.
While using Additional Attributes as you outlined above is interesting, there is no way to enforce a uniqueness constraint in an Additional Attribute.
i have also asked for this feature. an additional field that can be searched for where we can have a unique number for assiging to that account.
i have had customers ask what is their account number so that they can include it in EFT payments so that their payment is allocated to their account correctly.
so far we have not had an issue but with well over 1000 active accounts, we expect sooner or later a payment received might be allocated to the wrong account without this simple data.
further more, when i pay all our suppliers, i put in the account number that is on their statement, it helps temp staff allocate payments correctly.
also, lots of our customers still come in and say their old account number because it's quicker for me to put in an account code that search through all the businesses, whose name starts with the town we are opperating in.
in Retail manager that we came from, we used to have letters like "RSSW" as an account code for customers with an account and numbers like "180" for COD customers.
YES! Additional Attribute are searched in both the Sale list and the Customer list through the DEAR front-end.
You CANNOT search for Additional Attributes through the API for either Sales or Customers (at this time; May 2017)
@Michael Davis I don't think it's always fair to want a system to conform to your particular workflow. Generally the idea behind a unique identifier like an account number is that it never changes.
Using DEAR, for example, you could assign one Additional Attribute field for a unique ID. Another Additional Attribute field could be assigned as a drop-down for your various account classes.
DEAR's in-built functionality allows you to edit a customers credit terms from the customer dashboard.
If you have 4000 customers it would be pretty simple and error-free to use a spreadsheet to update their details rather than do it manually.
@Michael Davis I'm not suggesting you don't try to improve DEAR by logging requests for improvements. I'm just trying to show that it's often impossible to implement existing workflows with new software and sometimes there are functional work-arounds which you can use rather than waiting for the software to be built.
I'd love to see your (1) and (2) suggestions implemented. Why don't you start a new Feature Request for each of these and see if other DEAR users agree?
For (3) you can search a Sales by Product Details Report for a single SKU giving sales info on just that one product.