A Repeat will always be a table. There can only be one GPS point in the form and that becomes the FC.
I have a bunch of tables in mine and mapping an attribute of a repeat table if rather hard. You need to make that table spatial somehow. Table support is spotty.
Here are some options.
Form
-You can add a Lat and Long to the repeat table and have it calc in from the main part of the form. Then use these via XY event layer to turn them into FCs. Again not dynamic.
-If it is a specific field (like species for me) then outside the repeat add a field that has a list of all the values from the repeat. The new join () is perfect for this. join(", ", ${repeatfield}). Then you can do Def Query on the FC - for example ListField contains "Value".
If in AGOL
-Do a Join features from the table back to the FC (Feature Class). This is of course static and would need to be redone on each add.
-You can use Arcade in a web map to query the related table and display results in a popup. But it is popup only and you cannot change colors based on the field or anything. Also it will show in a attribute table put you must click each one to show the value.
Code is like this - I found a better way to write it but I cannot find it
var tbl = FeatureSetByName($datastore,"LayerName");
var sql = "SpeciesList = 'JUMO' And PrimaryKey = '" + $feature.PrimaryKey + "'";
Console(sql);
var species = Filter(tbl, sql);
var cnt = Count(species);
return iif(cnt > 0, "Yes", "No")
In ArcMap IF it is brought into a SDE or GDB
-You can use subquiers which are pretty slick
PrimaryKey IN (SELECT PrimaryKey FROM tblDetail WHERE SpeciesList = 'ARTR2')
Ops Dashboard you can do it kind of.
Hope it helps. I beat on this for a day or so and never really got it to what I wanted. Once it is a table you are pretty stuck. In the end I am going with the List in the FC using join() but not fully tested yet.