June 2026 Update - Issue with intersect calculations

Question

Hi. This was working perfectly pre June 2026 update.

I have an intersect calculation here, using FeatureSetbyName $map. It also uses a field which is hidden by conditional visibility to select the project area if project areas overlap.  The way it is designed if there are no project areas to choose, the field does not appear, and it instead gets the value from the single project area

Since the update, when I draw the feature it does not calculate but I move it slightly after drawing it, it does. This is currently not practical for the end user.

(see attached gif)

Kind regards, Willy

Craig Gillgrass · Answer

BUG-000186071is a different issue @David_McRitchie

We're looking at it but do not have a timeline for a fix.

David_McRitchie · Answer

Hey Willy,

I had a support case come in that matches this behaviour. This got logged under BUG-000186071.

It is currently in the Product Plan so hopefully will be resolved soon. If you want to be updated on its status I would recommend raising a support case with your distributor and ask that they attach the defect to your subscription.

WillyG · Answer

Thank you @CraigGillgrass  Yes. That resolved the issue we were having. Thank you very much