Well then, they are not arranged in a list, so cannot be indexed.
I am afraid you will have to get a long equation that calls each text_input by name, the system does not have any way knowing you want to add those.
In classic, you could have made a list that refers to each of those text_input, and you could then use the content of each of those components in a loop that would access them each in sequence, but that is one of the feature they apparently have not yet deployed in X. Classic also has those text entry event that could behave like a button click, so could push the data into a list using an index specific to each text field.
If your values were in a list, that would have meant that the individual text_entry were already explicitly associated to a specific element of the list somewhere else in your code.
There isn’t much you can do with the current components that would not imply quite a bit of code.
One approach would be to replace all your text entry with a button that is showing on TOP (or in the same place) as the text entry. When you click in a button to enter data in it, the logic takes a note of which button is currently having the focus, cause the button to become invisible while makes the text entre become visible. When the entry is done, then someone evidently has to click somewhere else, so the logic would know to take the text entry value, push that in a list at the index location, use that value again as a caption to the button (so the value is visible). You still have an issue when the very last entry is in since there is no other button left to click, unless you make one to call for getting the total.
As I said, not matter how you look at it, it is not straightforward with the current version of X…