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

Edit Widget Questions

JasonNielsen

Is there a way to change the order of the attribute fields in the edit widget so they are not alphabetical but rather following the order they are in the xml file?

My second question is 2.0 didn't support snapping but it was mentioned that it would be something later on. Can somebody let me know when they think this would be implemented?

Thanks,

Jason

Najděte více příspěvků označených jako

Accepted answers

All comments

NajyaBatool

Hi ESRI FLEX Team,

"For future versions, we are considering an API enhancement to once again support the earlier workflow within the Edit widget." BJORN

Any further developments on the API?

Thanks,
Najya

NajyaBatool

Hi. We've also upgraded from 2.5 to 3.0 and I'm struggling to reorder fields in the Edit widget. Does anyone know if this issue was resolved in 3.1?

Thanks,
Najya

BjornSvensson

When you create a new feature in a feature service that has attachments, the edit widget doesn't let you add attachments right away. A feature has to be created fist, then edited again if you want to add attachments. Does anyone know what to change to fix this?

Short answer: This is how it works in the ArcGIS API 3.0 for Flex (which is different from 2.x) and the underlying ArcGIS Server (an attachment can't be added until a feature has been created and exist on the server).

Long answer: At 2.x when you clicked to create a feature, the request to create the feature was sent first, then the input boxes for attributes (and attachments) was popped up.

ArcGIS 10.1 added the capability to allowed people to create, but not update, features �?? which (with the 2.x logic) would never work, as you wouldn't be able to set the attributes at all in this particular case.

At 3.0, the created feature is not sent to the server until the attributes have been popped up and user clicked OK. Since you cannot add attachments to a feature until it exists, this also means that you can�??t add an attachment in the same request. For future versions, we are considering an API enhancement to once again support the earlier workflow within the Edit widget.

JosVroegop

Code in previous post has some weird behavior. When you create a new feature in a feature service that has attachments, the edit widget doesn't let you add attachments right away. A feature has to be created fist, then edited again if you want to add attachments. Does anyone know what to change to fix this?

JosVroegop

I modified the standard 3.0 edit widget with code examples from Harold Bostic's post. Im not a flex programmer but it seems to work like it should. Maybe it's usefull to someone so here's a compiled and sourcecode version of my frankenstein.

edit widget 3.0.zip

PamTurner

Is there a comparable fix to reorder/turn fields off in the 3.0 flex viewer. I thought the default Field Inspector option would do it but I can't find any documentation to set it up and have tried all the usual search locations. Any guidance would be appreiciated. I'm trying to move from 2.5 to 3. Thanks in advance.

NeoGeo

Thanks to everyone that contributed!! I finally figured out my problem. For people who need a compiled version, here is a compiled swf (version 2.5). I included a small HowTo and and examle xml file as well as the mxml that was uploaded previously.

Thanks again everyone!!

EditWidget_layer_order_mods.zip

FrankRoberts

Sorry but hopefully this helps someone. the answer to my above question is that the behavior I saw was from having the addfeature tag ( found in the editwidget.xml) set to false. When you do this it must not allow or accept clicking on the widget. So then you can't turn it off.

FrankRoberts

When the widget loads, it automatically turns on all the layers, independent of what you may have switched on or off. That seems to be the default behavior even in the sample provided at ESRI (I guess). However, with mine after the edit widget layer loads up and turns on all the layers, I can�??t turn them off in the edit widget. I�??m looking at the config file for the edit widget and am not seeing anything that would allow me to enable or disable this function.

Anyone know how to allow me to turn layers off?

ToddLaQuay

I am also not a programmer and numbering the aliases only works if you have fields 1 to 9, when you add that 10th field in, it gets placed between 1 and 2 (ex 1, 10, 2, 3) I have about 60 editable fields and order is important to the non GIS users to follow their forms and fill in. Does anyone have a suggestion for this issue?

UPDATE: I found in other DB forums where they said to pad with 0's giving equal number of characters and that solved the issue. (ex 01,02,...09,10,11)

RachelS

Thanks for this Heather, this is a good work around in the mean time.
On the plus side I've discovered that flex honours hidden fields without needing to add code unlike webadf.

I have one other query I don't see on the forum all my text boxes are quite large. Is there any way of adjusting their size as it seems defaulted to the one size regardless of how many characters the field is in the mxd.

Thanks

Rachel

heatherGrybas

Hi Rachel,

I had the same problem as you. I have several datasets that can be edited with the edit widget and they all have a number of fields that have to be filled in. The best work around I could find (since I know nothing about programing) was to number each field in the order you want using the field aliases. So for example when your alias might look like "1. [Name]" then go on to two ( " 2. [Name]") and so on in the order you want the fields to appear. The edit widget should list them according to number. It really wasn't the way I wanted my field names to look in the editor but at least they were in the right order.

good luck!

-Heather

RachelS

Thanks Philipp,
That's shame, I hope it goes into the code gallery soon, as it's a very useful widget.
The Edit Widget unfortunately doesn't respect the changes made to the field Order in the mxd, although it honours field aliases. I don't know why the default order is alphabetical, since the way you would have the fields ordered in the mxd, is the way they should show in the flex.
Rachel

philippschnetzer

Rachel,

The code above requires a function be inserted into mxml...so you are out of luck using only the compiled version. However, you may have some success if you go to properties of your layer in ArcMap and hit the Fields tab - there you can check on/off certain fields, re-order and create aliases - as far as I know the Edit widget respects those changes made in the field properties...

RachelS

Hi,
I'm new to Flex, I'm not using Flex API just the standard Flex out of the box. But I need to reorder my fields and I need to hide some fields, since I can't use the mxml code, will I be able to carry out this using just the first bit if code the above posts say to paste into the xml?
I'm using Flex 2.5 and have so far been able to edit the widget and config file to edit my dataset, but I'm now stuck on reordering fields and hiding fields.

PLease help.
Thanks
Rachel

Anonymous User

I posted this idea a while ago but have just come across the issue again & came across this post.

Appreciate your support to getting this introduced @ the feature service level configuration.

Brad

mgiles86

I am using an SDE database and I do have access to enable feature service. My problem is that i have three layers that are editable: Working Points, Working Lines, Working Polygons. These three layers need to be grouped in my TOC. Since I cant group feature services in the TOC on the flex side, I am forced to group the layers in the mxd and call the service as dynamic using the MapServer feed...

HaroldBostic

It's just how the REST endpoint was implemented. That way you can perform CRUD operations at a feature level or over an array of features. If you have access to the data being published, you can simply enable feature service access when publishing your map. Also, be sure you are using an SDE database if you want to leverage the editing capabilities.

See the specification for more detail -> http://services.arcgisonline.com/ArcGIS/SDK/REST/overview.html

mgiles86

Can somebody explain why this only works for layers type feature - using the FeatureServer rest feed. The layers that are editable in my application are type dynamic and the edit widget does not honor the field orders from the xml..

mei09

this has been an interesting thread.

I was wondering if anyone has been able to dyamically change the fields that are availabe for editing during different stages, i.e:
1) create new features : all attribute fields are editable
2) update existing features: only some fields are editable

would appreciate if anyone could point out if this is possible and which event should be used to capture this?

thanks
mei

KarlWilson

Thanks Ben.

OK I got it working, the issue was human error on my part. I had been modifying the EditWidget.mxml of a different project to the one I was compiling. Duh.

I've updated the attachement on my previous post with the correct EditWidget.mxml.

Karl

BenKane

Karl,
If you succeeded in compiling it with the modifications then it is all about the <fieldnames>, <fieldlabels> and <hiddenfields> tags in the xml file. Specify the order you want the fields to display in the attribute inspector window with <fieldnames> and assign aliases in <fieldlabels> in the same order. Any field you put in <hiddenfields> do not put in within the other two tags. This should work, worked for me...

Ben

I'm having difficulty getting this to work for 2.4.

I've copied in the code between the /*MODIFICATIONS*/ comments in hbostic's post to the basewidget_widgetConfigLoaded function within the if (configXML) statement, and added the createFieldInspectors function. I assume the rest of the EditWidget.mxml displayed was from a version previous to 2.4.

I also added the import com.esri.ags.components.supportClasses.FieldInspector; statement and added the closing slash in the </editablelayers> xml tag, as mentioned by NeoGeo.

When I run the widget I see no difference in the widgets behaviour. Can anyone who has managed to get this to work please offer some help? (jvroegop maybe?)

Cheers,
Karl

Attached is my full EditWidget.mxml

KarlWilson

I'm having difficulty getting this to work for 2.4.

I've copied in the code between the /*MODIFICATIONS*/ comments in hbostic's post to the basewidget_widgetConfigLoaded function within the if (configXML) statement, and added the createFieldInspectors function. I assume the rest of the EditWidget.mxml displayed was from a version previous to 2.4.

I also added the import com.esri.ags.components.supportClasses.FieldInspector; statement and added the closing slash in the </editablelayers> xml tag, as mentioned by NeoGeo.

When I run the widget I see no difference in the widgets behaviour. Can anyone who has managed to get this to work please offer some help? (jvroegop maybe?)

Cheers,
Karl

Attached is my full EditWidget.mxml

EditWidget.zip

dmitrypylnev

Hi! There is a question whether it is possible in a widget in the fields of attributes to write fractions? (field on the GIS server fractional numeric)

JosVroegop

Thanks guys, just what i was looking for. 😄

Used the code from Harold Bostic's post in 2.4 viewer, works like a charm.
Esri should make this standard functionality for the edit widget in my opinion.

Ahmad_TarmiziTalib

does these codes work with flexviewer-2.3.1 and acrgis 10 (i notice some differences between the original edit widget code posted above with mine)? i tried both codes too but seems like they did nothing for me. the arrangement is still alphabetical. what could possibly went wrong? =\

NeoGeo

Just trying to get the code posted here to work but not having much luck. I am trying the last version posted. In the xml posted a closing slash is missing on one of the tags, I added import com.esri.ags.components.supportclasses.FieldInspector because the compiler didn't know what a field inspector was, and I added back in the labels which appeared to have been removed in the posted code (the ok button didn't even have a label), and of course I added the new sections in the xml file. What else am I missing? There is no change in the widget's behavior from the original when I run it...

JonFisher

Greetings all!

I'm finding the code samples here to be very useful, especially the extention of functionality controlled by the EditWidget.xml file, but can anyone point me to a good comprehensive review of all the base tags that the EditWidget understands out of the box?
- Bob

The ESRI help page lists the tags that work out of the box:
http://help.arcgis.com/en/webapps/flexviewer/help/index.html#/Edit_widget/01m30000000v000000/

Anonymous User

Greetings all!

I'm finding the code samples here to be very useful, especially the extention of functionality controlled by the EditWidget.xml file, but can anyone point me to a good comprehensive review of all the base tags that the EditWidget understands out of the box? Or are the ones that come in the base widget xml code the only ones that it does? I've been looking for a good disussion on this but have so far not come up with a good definitive answer ...

Case in point, I can add my outFields list directly when coding a FeatureLayer directly in an application but am not finding a compatible xml option in either the base config.xml for the flex viewer or the EditWidget.xml file. Same goes for the ClassBreaksRenderer ...

- Bob

ThomasSchultz

Sorry, I was debugging at the wrong point. Setting the formItemsOrder property to "fieldInspector" is not my issue. My field inspectors are also creating correctly. But my fields are still out of order. Any help would be greatly appreciated.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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