As my org moves from AGOL to Portal, I've run into a frustrating (and eventually tedium inducing) issue in that when I export data from a Survey that has been published to the Portal, it uses the field names as column headers rather than using the label or bind::esri:fieldAlias column as appropriate. This happens regardless of whether I export from the feature layer in the Portal directly or from the Survey123 data tab. The display names/aliases are visible in the Portal when I view the data/fields. The exports from the Survey version I still have in AGOL use the label/alias for the column header. The original publication of the survey in Portal contained the aliases.
We have associated SQL tables and other tools that are based on the field aliases that were set-up. Field aliases being used do not adhere to the no capitalization rule, but I'm not sure if that matters here.
Edit: Forgot to actually ask a question
Is there a setting somewhere that I am missing that would result in the export using the "display name" or alias instead of the field name?
