Appreciate the feedback!
Yes, sadly I previously tried the options you suggested with no luck.
I am trying to utilize the integer for the 'lyr_dpth' field both inside and outside the repeat structure. This is to auto-fill a layer depth inside the repeat and to use the layer depths for 3D layer symbology with photos of each layer outside the repeat (3D scenes don’t symbolize repeat tables unless I ‘jenk-them’ into feature classes using illegal auto-filled hidden geo-points).
- Funny part is, I get a -1 value (inside and outside the repeat) for any integer or note field using an indexed-repeat(${lyr_dpth}, ${lyr_calcs_rpt}, 1).
- Sorry about the -1 index. It was just to show that I tried it, and it returned a –1.
- Funnier part is, I do get the get the text value for 'lyr_dpth' (representing desired integer value) when using the selected-at(${lyr_dpth}, position(..)-1), and layer_count: count-selected(${lyr_dpth})
Tried your version, and the indexed repeat value still displays -1, for 'lyr_dpth' both on the published and unpublished side of Survey 123 Connect for the ‘lyr_dpth’ integer I was trying to get.
All I know about indexed-repeats, is if it can’t find the index, it returns a -1. Setting the layer_count seems to return a value. Usually, the repeat structure is as you said, so index 1, gives you the first value, 2 the second… Unfortunately, my index of 1 gives -1, 2 gives -2.
Maybe I am missing a repeat count somewhere for my indexed repeat to call from?
Pulling an integer elevation would be very useful in Geology, to Soils, Water, Ice, and Snow core visualization in 3D with photo's per layer.
I'm just hoping to get a non -1 value to be returned for an indexed repeat. My rookie skills can return a value in excel, but no success in Survey 123. I must be missing one very valuable step?
Nathan
Attached both of our files.