nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Exporting data from Survey123 with names instead of labels

SwathiIyengar

Hi all,

We need to export data from Survey123/ArcGIS Online using field names instead of labels. I know this question has been asked a few times in the past (in 2017, in 2019, and earlier this year).

One of the solutions suggested, "changing DisplayName in the AGOL Feature Layer to be the value you want to see in Excel, the next Excel export will pickup the change." How does one do this?

Another solution suggested populating the column bind::esri:fieldAlias - to confirm, that would look something like this (assuming we want the name fields to appear in the excel/csv exports)?

type	name	label::English (en)	bind::esri:fieldAlias	label::Persian (per)
begin group	householdinfo	A. PRELIMINARY INFORMATION / ADMINISTRATIVE SURVEY DATA	householdinfo	A.اطلاعات اولیه / داده های اداری نیازسنجی

Thanks!

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

IsmaelChivite

Hi @SwathiIyengar No news on this one. For clarity, Survey123 is limited to what the export capabilities of ArcGIS Online and ArcGIS Enterprise provide. The solutions provided in the links you include are still valid.

SwathiIyengar

Hi @IsmaelChivite ,

Thanks - with regard to one of the solutions, can you provide some additional instructions (see below)

One of the solutions suggested, "changing DisplayName in the AGOL Feature Layer to be the value you want to see in Excel, the next Excel export will pickup the change." How does one do this?

Thanks!

MicZatorsky_AEC

Find the feature layer that your survey uses > Data tab > Fields tab

Select a field, change the name. For example:

SwathiIyengar

@MicZatorsky_AEC - thanks a million!

RichardRogers1

Are there any plans to resolve this? An option to choose actual column headers ("name") rather than field aliases ("label") would save much trouble on the next step in the data workflow (in my case, pushing data into a separate database).

ConsueloMartinez

It doesn't work TT

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.