This is happening:
That “(1)” is seemingly invincible. I’ve set data privacy rules and search constraints in a way that the user will never see the other entry that has the same name.
What happens is that this store has a list of customers. Fine. And every customer has a list of products. “Alface branca” is a product, and every customer of that shop has a thing named “Alface branca” under his product’s list, however the price for each customer is different, that’s why I need them to be different things (clones) for each customer’s list.
In other words, the products have the same name but different prices and different “from which customer it is” fields. So if I constrain the search for customer, only his product will show up, that’s what I show in the picture, only that specific customer’s product with his own price has showed up.
However another customer also has that “alface branca” with another price, then since these things have the same name one of the customer’s search result shows up with this (1).
What are strategies to defeat this and not show the (1) in this case?
Thank you for the attention.
Edit: More explanation as I’m aware this is a case by case thing.
My tables (data types) are like this:
I have this thing called Base Product…
And every customer has a personal catalogue, because every customer is priced differently. The catalogue is a list of the thing I’ve shown above, the Base Product, inside the Customer thing.
So when the user (is a store) searches for a Base Product name to put into the customer’s order, for example, Tomato, only one Tomato entry will appear (like in the first image) due to search constraints and privacy roles, however it will appear with (1) or (2).
How can I better organize this so that (1) is prevented? I really tried reading the forum, but every case is unique and I couldn’t come up with anything based on the concept shown to others.