And what is our point? You did not even explain what your screen shot is showing. Whatever it is, you have been warned by the application that you have duplicates. Manager will not prevent that. Users employ many different schemes for identifying documents. In some cases, duplicates are intentional.
I see the issue. Basically two suppliers can issue purchase invoices with the same reference number but Manager will make it seems like duplicates even though they are not.
I’m not sure how best to solve this issue. But I don’t think we should have 2 reference number fields (internal & external).
One way to solve this would be for suppliers to be able to configure reference number prefix. And all reference numbers would have this supplier prefix.
2 Likes
Before spending time thinking about this, I believe you should wait for @MCasper to reveal why the post was created in the first place. Does he believe there is a bug? Is he suggesting a change to the program? Or is he just illustrating a recently discovered feature?
In my opinion, that raises the possibility of more confusion. Suppliers won’t create prefixes for themselves. So users would have to do it. Then, if you’re entering suppliers’ reference numbers, you’ve got different ones than the suppliers sent to you. And you still would have the issue of how to prevent duplicates, if that is your goal. It’s not a stretch to think that ACME Steel and ACME Metal Products would both send a sales invoice numbered 1234. So you would get into layers of duplicate prevention.
I believe the program already includes adequate notification of duplicates. Resolution should be up to the user without further complications.
thies what i mean
Yes, so what, you get the alert and can change it. Not sure what the issue is or remedy you seek. The alert exists to show you exactly what you see.
And, of course, when Manager issues a Sales Invoice to a customer, that customer may find that the reference/invoice number is duplicated by another of his suppliers
There really is no way to solve this problem
Not sure if this is a problem. For some it may be an issue at best and the alert helps to take action if needed.
1 Like
The duplicates must be linked to the partner’s name
1 Like
What information do you expect beyond what is already shown? The program already gives you exactly what you are asking for.
I agree with @Tut, how will we reconcile a supplier account if none of the references match?
That said, the solution proposed by @lubos is good for the purpose at hand (i.e. identifying duplicates) provided that this altered reference is a backend system field and that the actual reference number don’t get altered.
2 Likes
so it’s not duplicated
I am sorry, @MCasper, but your posts are not making sense. You complain about duplicates, then say “it’s not duplicated.” You complain duplicates are not linked to suppliers, but post a screenshot that clearly shows they are. I cannot understand your issue if you even have one.
So far, you have not said what you think is wrong, if that is what you are trying to say. If you think something is wrong, you must say why.
Manager checks for duplicates based on Reference and
@MCasper wants the Manager to check for duplicates based on Supplier Name + Reference.
But I agree that there is the addition of a new field to record the Reference Number from the Supplier and we can still use automatic references in Manager for internal purposes.
1 Like
Let’s not guess what someone else wants. I have been trying to discover that without success.
Currently recording suppliers ref no through a custom field. so no issues with duplicates. Only issue is it doesnt get desplayed in statements. That can happen too if you record Supp Ref# in Description field.
1 Like
What I want is clear, you just don’t want to understand
First of all, I think that there is a duplicate of the reference number isn’t the issue. The bigger issues is how that reference number is attached to the Supplier or Customer.
In this case it’s a database issue. The fact that there are duplicates is just a happen stance here. If the reference numbers aren’t linked to the Supplier or Customer, then that is the main reason why there’s an issue. The reference number should be attached to the Supplier or Customer.
This allows the One to many relationship to be better defined and also searchable in a much better fashion. In fact searching for duplicates in this fashion is really a waste of the system’s time. The ONLY time duplicates would really matter, is if you are getting the same reference number from the exact same Supplier or Customer. If the Supplier or Customer is different, then it’s no big deal.
Now keep in mind I’m strictly speaking about the back end. The database… Not the front end UI for the user. I’m not sure how @lubos is doing it on the back end with the database, but if he’s not using the Supplier or the Customer as the One part of the relationship, then I think he should look into it.
With my Transportation Management System we have a lot of One to One, One to Many & Many to Many relationships in the database. And they all are connected to a Shipper, Consignee, Trucking Company and Vendor. And we never have issues with duplicates. And there are a lot of them. Because when you break it down, THIS particular duplicate is just an integer in a field. Nothing more.
There’s no issues with the database, for two reasons:
-
Manager isn’t a relational database. Though some relations are maintained for practical reasons, Manager is mostly an object database with Purchase Invoices being children of Suppliers and not relational tables.
-
The id field for Invoices is the system field
Keywhich is GUID string and this is the only identifier needed for the internal mechanics of Manager to work.
This makes much more sense.
Thanks for the clarifications.