Can I stop "Merged With" from removing duplicates

I’m trying to display order details in a Multiline Input in a Repeating Group.
This requires displaying the QTY of Items from Supplier A and Supplier B in a list, joined with “Line_Break”
This works when the Qtys from each supplier are different. EG When Customer A has ordered 2 items supplied by Supplier A and 1 by Supplier B.
The trouble seems to come when they’ve ordered the same number of items from Supplier A and Supplier B (which is going to be the norm as they’ll normally order 1 from each) but, I understand from a search here that it’s normal behaviour for “Merged with” to remove duplicate values so that means there’s no value displayed for Supplier B (I might be wrong about this)

Is there something other than “Merged With” that I can use that won’t remove duplicates?

Here’s a simplified screenshot of my problem created in XLS:

Screen Shot 2022-04-21 at 12.21.38

This is the actual formula that’s creating the problem…
Screen Shot 2022-04-21 at 12.22.51

Can anyone dig me out?


Explore :unique elements

1 Like

Hi there, @joefarrowsmith… the use of the multiline input is interesting (to me, at least), and I don’t know if you are going to be able to accomplish what you want with that element. I might be way off here, but is there a reason you are using a multiline instead of a repeating group inside of a repeating group? Your orders are obviously unique things in a data type, so it seems like you could avoid the duplicates issue if you were displaying those unique things (and their associated fields) in a repeating group.

Apologies if I missed the mark here, but that’s what came to mind when I read your post (and even played around with the multiline input thing a bit, but to no avail, of course).


1 Like

Thank you. I’ll check that out.

Hi Mike

That’s a good suggestion. Thank you.
The main reason I’m using a Multiline input is down to my lack of knowledge. It struck me that on a big order with lots of items it would provide a scroll bar so it would be better than a standard input or even a text to present the data to a user.
As for RG within RG, I can see what you’re saying and I’m going to have a go at that - I wasn’t completely sure I could do that but it does make sense. My brain tends to panic and threatens to implode when it comes to doing things across multiple tables using the joined up structure of my DB as I’ve always struggled with relational DB design but this one does work so I shall try it. Thank you…I reckon this will get me there. I’ll have a play.
All the best

1 Like

I think where I’m having difficulty is with the relational design in my DB. Basically, when a User orders items, they pick those items from a product list and they can pick as many different items as they like with differing quantities of each. When that order is recorded, it’s given a UniqueOrderRef and the User’s Details, Date etc of the Order are recorded in the Orders table and the Contents of the Order with all the items are recorded in an OrderDetails table with the same UniqueOrderRef - (In my understanding, this basically gives me a 1 to 1 relationship between Orders and Order Details instead of a 1 to many) That means that the items are all listed in one cell in the Order Details table. At this stage it might be quite a large upheaval to the database to change this but I’m considering it. Once that’s done, then the RG in a RG to present the data to users will make more sense. If I can’t work out the new design though, I might revert to concocting some kind of Multiline input tool thing.
Don’t know if that makes sense but I think my design is what’s causing the limitation here so I’m very grateful to you for your time and your suggestion about the RG in a RG because I can now improve the DB. Thank you.

1 Like