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

Batch editing for layers containing contingent values

katie.quantrell@rspb.org.uk_RSPB

Hi,

When trying to apply the new batch editing functionality (that was released as part of the June update), to a layer I have in experience builder, I received an error messages stating "Editing attributes for multiple features is not available for layers with contingent values".

This is so disappointing as this functionality would be so useful to improve user experience by enabling users to batch update statuses of records for example, without the need to do this individually on every record.

Would it be possible to enable this functionality for layers containing contingent values? Ideally including the ability to batch update the contingent value fields. But if this is not possible, enabling the other fields in the layer (that don't use contingent values) to still be batch edited? Rather than this functionality not being available on the whole layer.

Many thanks

Find more posts tagged with

In Product Plan

Status: In Product Plan

Comments

Craig Gillgrass

@Katie_Macintyre_Atmos this is still on the roadmap. It will not be in the next release of Online (scheduled for later this month) but we are looking at it for one of the follow on releases this year.

Katie_Macintyre_Atmos

Will this functionality be added soon? We can't move off Web App builder without the ability to batch update attributes. The fields we need to update aren't part of the contingent values but it still won't allow it.

katie.quantrell@rspb.org.uk_RSPB

Thank you for getting back to me, and its great that this is already in the roadmap. Will definitely provide a real benefit when this is in place. Many thanks.

Craig Gillgrass

@KatieQuantrell this is on the roadmap for batch editing, but could not make this release. We don't have a release assigned yet to do this work, but it is in the plan.