Hi all,
I just ran into an error with field calculations where absolutely zero field calculations will save correctly. I was revising the Calculation Expression in the Description header within the Discontinuity group when I encountered this bug.
I thought that the corruption bug might only apply to the Description header, so I tried making another header within the Discontinuity group named DiscontinuityDescription. This new header also runs into the same error and I fear that if I edit any other header calculation expressions, they will 'break' due to this bug.
The screenshots above only show DiscontinuityType in the calculation expression, however I tried many types with multiple expressions that have worked before and still run into this bug.
In addition, when I try to delete the new DiscontinuityDescription header, it does not let me, stating that it's a core field. This does not make sense as Bentley does not allow users to create core fields, therefore this is a bug side effect.
In addition, this bug disables retrieving Discontinuities group data from the cloud in OG Professional and OG Data Entry. Also, if data is entered, it can be saved once, however if you try to edit the same row of data again, it will state that there's an unknown error saving data.
Please advise. I will be submitting a high priority service request ticket with this forum post as a reference.
Thanks,
Hi Joseph
I'll do a response through the Service Request
This issue has been resolved. A Bentley Developer informed that this issue occurs when working on OpenGround with poor internet. When making changes to headers, OpenGround currently sends several requests to the server to make changes. If your internet falters at any point while those changes are being sent, it will result in a corrupted header bug.
The developer assured me that this is being patched in January. The patch will aggregate the requests into one packet so that they cannot be partially sent to the server due to poor internet. If you are experiencing this issue, reach out to Bentley Support and request that a developer reset the header for you.
Answer Verified By: Joseph Ang