Repeats: Is it possible to use a repeat to calculate but not keep the resulting related table?

[AlfredBaldenweck]

I'm experimenting with a form right now and I'm using repeats as a counter, so that whenever the user sees a certain plant, he creates another record in RepeatA, and when he sees a different plant, he makes a record in RepeatB, etc. 

The values of the repeats are then calculated to get the ratio of one to the other, etc. 

I only care about the calculations.

Is it possible to use the repeats but not end up with the related tables created by using them? I really don't need 6 extra tables that have single-field records with a value of "1".

I'm looking for something akin to bindtype:null.

Is this possible?

[MobiusSnake · Accepted solution]

I don't know of a way to do what you're describing, but if all you require are counts and ratios, wouldn't integer questions with the "spinner" appearance do what you need?  I've done something similar to what you're describing and that's what we went with.

[Neal-Kittelson · Accepted solution]

Why not skip the repeats and add a spinner appearance on your 6 species fields (I assume they are integer).  This would act as a counter, and you can do the  "bind::esri:fieldType = null" on those field, and just capture your ratio fields.  To me it seems this would be less complicated for the end user as well.

[AlfredBaldenweck]

Well, as it turns out, both of you had a much better solution than what I had come up with. Thanks!

I'm going to leave this open for a little bit before marking you two as the solutions.

[TylerGraham2]

Repeats are related tables. I don't think you can create a repeat in Survey123 without it creating a corresponding table.  However, you can use the bind::esri:fieldType to null for the questions so it won't include the question in the table.  You'll probably still end up with a bunch of records in the repeat that are just GlobalIDs and the like though.  

[AlfredBaldenweck]

Yeah, that's the thing-- I want it to store calculations and stuff along the way, but I don't need them at the end; just the final answer. My example here was for straight numbers, so the spinner suggestion worked great, but for things like "Good, Fair, Bad", where the lowest score wins, I'd really just like to get the lowest score and not have a billion related records that really don't do anything for me.