Hi all,
This is a reoccuring issue for me that has resulted in different bugs or errors with OpenGround, but they're all linked to this issue. Every so often when creating a header, the data field will bug out for an unknown reason. (Crossreference these posts: https://communities.bentley.com/products/geotechnical1/f/openground-forum/237137/template-studio---cannot-generate-quick-log-for-user, https://communities.bentley.com/products/geotechnical1/f/openground-forum/237500/og-data-entry---unable-to-save-data-entry). For example, in the first link DepthRecovery was set up as 2 decimal points, however the calculation was occurring and then the number was being converted to 3dp and then into a string. This caused an issue with OpenGround Data Entry where if I entered new values into a row, it would error and not allow me to save, stating that DepthRecovery needs to be a decimal. This error carried over to report creation because the report expected a 2dp value, effectively disabling quicklogs.
This issue has now reoccured for a new group I created called FieldPlasticityTests. I set Depth and SampleReference as keyfields, and one of them bugged out with what I assume is the same type of error. In this instance, although I can delete Depth and SampleReference after clearing all data from them (by setting their calculations to an empty field), the database remembers that there was data in the field and now places invisible, empty, placeholder data into it. This means that I can't delete the group because it's technically a non-empty group. When this bug occurs with a header set as a keyfield, it can break the entire group. In addition, in this instance of the bug, data entered into the broken keyfields 'disappears' from OpengGround Data Entry. It's still in the database, but it won't show up in the data entry areas, and it won't print to a quicklog, see below where I tried to enter a depth of 5, but a depth of 5 was already entered previously and is now invisible.
I tried deleting all headers from the group, to see if I could get away with recreating them, but the database seems to remember the invisible data even if the headers are gone. If the headers are recreated with the same name, the data will revive.
All this being said, does anyone know how these corrupted headers are created? Is it something I'm doing while working on OpenGround Professional? Should I not have both OpenGround Professional and Data Entry open at the same time when working? This is the third time this has happened, and I'm slowly accumulating 'dead names' for headers / groups that I cannot use anymore.
Thank you,
-edit-
In this scenario, OpenGround support has determined that the Location ID controller field was somehow used in a calculation, which is why the header is italics in the screenshot below. In this instance, the corrupted keyfield was actually the Location ID. As there is no way to input or remove a calculation for Location ID, this bug cannot be fixed from the user side. OpenGround support 'resolved' the issue and closed my support ticket... by creating a new group named "FieldPlasticityTest" for me, leading me to believe that the official response is that there's is no solution for corrupted headers/groups, only the workaround of making a new header or group.
I would appreciate a response from Bentley Support on this issue as it's not an issue that can be dismissed with a workaround. For example, let's say I've been working on a OpenGround for 5 years and have hundreds of boreholes within my cloud. A new client requests that we complete a lab test that was previously not assigned a header. I create a new header and it corrupts the data for the entire group inwhich the header was created. I cannot just make a new header or group for this.
Hi Noah,
No, support has not provided any solutions. You must abandon that header (or group, if the corrupted header is a keyfield) and recreate it with a slightly different name.
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
Can you clarify if you were working in Professional or Template studio when this issue occurred? Thanks!
Hi Judy,
This issue typically occurs on OpenGround Professional, when you are creating or modifying a header or group. This issue can also occur on Template Studio, but the symptoms are different. In Template Studio, it causes the corrupted template to be inaccessible (cannot be opened or used).
I have not completed major changes to my configuration pack or templates since January and am unable to verify that this issue is fixed.