Yes, but the 'Individually for each event' user variable setting applies a single value across all selections in the event, whereas I need different values specific to each selection to become available to each selection across the event. It seems I can have values 'per selection' OR 'for each event', but not 'per selection for each event'. Hopefully the following clarifies a bit more:
Stage 1:
A set of triggers manages the calculations for the probability of a top two finish (which is the sum of its 1st place probability + the sum of the probabilities of all the ways it can finish second, as defined by odds available in the win market (i.e. 1/back_price)). This is set to calculate iteratively so that it can manage any number of runners, but without requiring a trigger set for every possible number of runners. This setup provides a "toptwo" user variable, with the value set "individually per selection", such that each and every selections "toptwo" has a different value (i.e. the probability that the specific selection itself will be in the top two).
Stage 2:
I want that final 'toptwo' output value (i.e. the resolved value only), for each and every selection, to be visible in all other markets of the event for at least the selection itself (i.e. 'toptwo' has the specific value for each selection regardless of which market in the event it is used in), and potentially/ideally so that it can be available for other selections use (i.e. via 'r_1_toptwo' or similar). However, I just can't seem to get the selections own 'toptwo' value to apply to that selection across the event:
Using "Individually for each event" will transfer a value, but it takes only one (the last) selections 'toptwo' value and applies it to all selections.
Adding an extra 'toptwo' = 'toptwo' trigger with no conditions and "Individually per selection" will not transfer anything beyond the market it was created in, as the 'toptwo' expression was not calculated in other markets.
Adding identifiers to the variable might have made "Individually for each event" workable (e.g. 'toptwo_sel_index' or 'sel_index_toptwo'), but parsing order doesn't seem to permit this.
I've even tried doing it 'for each event' for one selection at a time, but this also applies the value to the event rather than the selection.
It seems like this should be something relatively simple to do, but I just can't seem to figure out how...