I’m in a phase like this right now.
Let’s see.
The number 69 appears several times in the data.
I want to count it and display it like this:
69 - 4
just like the other numbers
show it and count how many times it appeared
I’m in a phase like this right now.
Hi dear,
Before even trying to solve this issue, I’d like to understand what those data actually represent, because this is a somewhat unusual procedure.
It might be possible to simplify it, and perhaps even simplify the way you’re storing the data in the first place.
If you’re not interested in that and, if I understood your request correctly, you simply need to count how many times 69 appears in the list, you can use two for each loops, one to iterate through the first level of lists and another to iterate through the second level.
Then, if item = 69 set the var to var + 1.
Friend,
It is essentially a product check based on numbers, where each number represents a specific product.
This allows me to retrieve the data and display results for each number, making it possible to track how many times a person selected it.
It involves a date, a number, and the frequency with which it was processed during the month…
If possible/interested to use extension then You may this tiny extension to make complex work to simple…
Hi dear,
Thanks for adding more details.
I’ve put something together, but I hope I understood your intention correctly.
At the moment, I see that your procedure leads to this (I’m not sure whether it’s correct or not 
)
But if you want to count how many times a number appears across all the sublists in cesta, this is what you could do.
Would that work for you?
Friend,
That’s basically it, but I’d like the last saved number to show up indicating where and when it appeared.
Like this: 69 - 3 Front 1 - 2 - 3 Date 07/08/26—though, of course, that’s impossible since there are 8 different positions where these numbers could appear.
So, the way I imagine it, it would look like this: 69 - 3 Front 1 - 3 - Date 07/08/26
This is new to me, what do you mean by that? Do you have a variable that keeps track of the “last saved number”?
V1.1 better?
Now you can reference the front and qtd for each number.
I need to step away from the PC for a bit, when I’m back, I’ll fix the trailing " - " in front.
I’ll also add the date, but you’ll need to tell me which index it should refer to if there are different dates.
Thanks, my friend…
I’ll post it soon.
V1.2 (Maybe the final version )
The date field is populated with the date of the last matching item found.
Interesting note:
This works thanks to reference semantics (I hope that’s the correct term).
By pointing to the path (key front), and therefore to a list, we can useadd item to listdirectly on it.It’s really useful to know
It looks like we’re running into an error.
The front end isn’t being pulled; I’m trying to do it from here…
Hi,
Sorry, I had mistakenly understood that front was the index where the number appears 
.
I’ve now corrected the soma_dados function.
Hi dear,
If this topic has been resolved, I’d ask you to close it and open a new one with this request.
SPOILER: Recreate the layout in a new screen and then create a schema to use with RL.
1 Like