ĪĪ¹ @anon81228582 , if I have understood your scenario correctly, if you use a single-select field in a branch and then add the same field to another branch it will NOT show up in the āAvailable fieldsā part of the āConnected toā list. However, if you scroll down to the āAlready in useā part of the āConnected toā list you can still select the custom field you want, even if it is in use. Asana will simply have a warning triangle saying that it will essentially overwrite the first entry with the next.
However, this is not necessarily an issue if you use the same single-select field in more than one branch within the same primary question, as long as the path of your formās branches will lead the submitter to select from this field only once.
If for some reason you cannot do that, then the below example concludes with a workaroundā¦
Say you have a āUniverseā single-select field which is connected to the options that each are a branch to a further question related to that āuniverseā
If āStarwarsā is selected then within its branch you can have the following question that draws from the āJediā field for answers on peopleās āfavouriteā choice
But if āStarwarsā is selected and then you also have a 2nd question within that same branch, you can still use the same (Jedi) choices as you did with the first question, which may make sense, however this will clearly create a problem for your results (as the yellow triangle icon will note).
The form will overwrite the choices for āfavouriteā with the choices for āleast favouriteā because you are using the same Single-select field for both answers. To solve this, you can (manually) create a duplicate of the āJediā single-select field (with the same options) and rename them both these fields to āFavourite Jediā and āLeast Favourite Jediā respectively so you can collect the correct answer to each question separately.
Hope that helps! 