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 issue when setting no attributes updatable - geometry only

ChristopheS

Hi All,

I have to modify features, but geometries only, attributes should not be shown nor updated.

So, as by default Editor fieldConfig is exposing all attributes, I tried to empty it with null, [] or [{}].

Unfortunately all these values are causing many issues and errors in the javascript console.

https://codepen.io/Chris_Siveco/pen/dyvKzNP

Is there a way to edit only geometries with the Editor widget ?

Regards

Chris

Find more posts tagged with

Accepted answers

JeffreyWilkerson

How about leaving the fields in but not allowing them to be edited, such as:

 fieldConfigs: [{
     name: "HazardType",
     label: "Hazard Type",
     editable: false,
     direction: "asc"
},
{
    name: "descrip",
    label: "Description", 
    editable: false,
     direction: "asc"
},
{...

There is also a 'showNoValueOption' setting that might work (not much help on it). Or maybe the 'visibilityExpression' that ties to an Arcade expression that is always false?

https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FieldConfig.html#showNoValueOption

All comments

JeffreyWilkerson

That second option looks a lot simpler 😁

ChristopheS

Actually, with something like I made it work :

 const pointInfos = {
              layer: pointLayer,
              fieldConfig: [{
                name: "HazardType",
                label: "Hazard type",
                editable: false,
                visibilityExpression:"1==2" //Here is the Trick not to have any attributes editable nor shown !
              }]

BUT, after reviewing my codepen code, I also made it work with a regular fieldConfig: []

So, may be there was a bug in my original codepen.

Thank you Jeffrey

JeffreyWilkerson

How about leaving the fields in but not allowing them to be edited, such as:

 fieldConfigs: [{
     name: "HazardType",
     label: "Hazard Type",
     editable: false,
     direction: "asc"
},
{
    name: "descrip",
    label: "Description", 
    editable: false,
     direction: "asc"
},
{...

There is also a 'showNoValueOption' setting that might work (not much help on it). Or maybe the 'visibilityExpression' that ties to an Arcade expression that is always false?

https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FieldConfig.html#showNoValueOption

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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