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; } } }

Editor Widget — Expand field to show lenghy text value

Bud

I have an editor widget in an Experience Builder app that has a field with an 800-character text value.

experience builder 7.png

It's hard to read the text value when it's crammed into a single-line textbox. Could Experience Builder be enhanced so that the textbox can be made permanently larger?

Or add a manual expand toggle like this?

experience builder 8.png

Encuentra más publicaciones etiquetadas con

Widget

Status: Abrir

Comentarios

LindsayRaabe_FPCWA

This setting is available, but not in Experience Builder itself. You need to open the webmap in Field Maps Designer (or the Map Viewer) and on the Form config pane, you can set that field to Text - Multiline. This is then honoured by the Edit Widget in Experience Builder. It even includes the little handle for expanding the text box as you suggested.

Edit text multiline.png

Edit Widget in Experience Builder:

Edit Widget.png

Bud

@LindsayRaabe_FPCWA

Thanks! I see what you mean about forms being available in the Map Viewer (I'm not using Field Maps). As someone who isn't an expert in web GIS, I either didn't know that or forgot.

Forms aren’t just for ArcGIS Field Maps anymore

LindsayRaabe_FPCWA

Glad I could help! From memory it was something that was developed in the webmap after Field Maps Designer was released, obviously because not all webmaps are intended for Field Maps use.

Bud

@LindsayRaabe_FPCWA

I configured the form in the web map and saved the changes. The multi-line text boxes are shown in the web map edit tool:

screenshot 24.png

screenshot 22.png

But when I preview my existing Experience Builder app, the fields are still shown as single-line in the editor widget.

screenshot 23.png

Any idea what I'm doing wrong?

Bud

The solution was to change the Configure fields setting from Customize to Use layer settings.

LindsayRaabe_FPCWA

@Bud Glad you figured it out. I hadn't had a chance to look into this deeper then it fell off my radar.

Únete a la Conversación

Inicia sesión para publicar, seguir contenido y más. ¿Nuevo aquí? Regístrate gratis.