Template Studio - Cannot Generate Quick Log for User

Hi all, 

I just started getting this error.

 

Context: I added some new picklist range symbols to add shading of the quantity of recovery for each sample on a borehole log strip. This involved adding a depth for recovery, and color picklist with connector color boxes. 

The error occurs with these presets 

But it doesn't occur if I don't use Depth Recovery as the base

As far as I know I have Depth Recovery set up correctly. 

Thanks, 

Parents
  • Hi all, 

    This error was tied to the DepthRecovery header which was broken for an unexplained reason. When a new header was created with the exact same settings and calculation, but different name, the problem was resolved. This error is similar to: https://communities.bentley.com/products/geotechnical1/f/openground-forum/237500/og-data-entry---unable-to-save-data-entry

    Additional notes for those troubleshooting: 

     

    • For some reason, even though there's data in DepthRecovery, I can delete it. 
    • Recreated DepthRecovery with the same name. Didn't add a calculation field this time.
    • Somehow the data within the DepthRecovery header was saved, even though it was deleted and recreated.
        

     

    • Note that the exclamation mark error states that DepthRecovery must be a decimal value, so perhaps OpenGround thinks the calculation is running as a string or something?
    • Set DepthRecovery calc to Remarks to clear all fields.
    • Removed DepthRecovery calculation. Now I'm able to enter DepthRecovery values

       
    • However as soon as I change a blow count value, the DepthRecovery reverts to 3dp, which creates the error again


    • If I revise the DepthRecovery back down to 2dp, it works. However this method disallows calculations


      Next attempt
    • Delete DepthRecovery
    • Create new header called DepthRecovered with all same settings as DepthRecovery
    • Weirdly I can still delete this field even though it contains data. I can even delete DepthBase now, I thought that was a keyfield?
    • It works!
       
Reply
  • Hi all, 

    This error was tied to the DepthRecovery header which was broken for an unexplained reason. When a new header was created with the exact same settings and calculation, but different name, the problem was resolved. This error is similar to: https://communities.bentley.com/products/geotechnical1/f/openground-forum/237500/og-data-entry---unable-to-save-data-entry

    Additional notes for those troubleshooting: 

     

    • For some reason, even though there's data in DepthRecovery, I can delete it. 
    • Recreated DepthRecovery with the same name. Didn't add a calculation field this time.
    • Somehow the data within the DepthRecovery header was saved, even though it was deleted and recreated.
        

     

    • Note that the exclamation mark error states that DepthRecovery must be a decimal value, so perhaps OpenGround thinks the calculation is running as a string or something?
    • Set DepthRecovery calc to Remarks to clear all fields.
    • Removed DepthRecovery calculation. Now I'm able to enter DepthRecovery values

       
    • However as soon as I change a blow count value, the DepthRecovery reverts to 3dp, which creates the error again


    • If I revise the DepthRecovery back down to 2dp, it works. However this method disallows calculations


      Next attempt
    • Delete DepthRecovery
    • Create new header called DepthRecovered with all same settings as DepthRecovery
    • Weirdly I can still delete this field even though it contains data. I can even delete DepthBase now, I thought that was a keyfield?
    • It works!
       
Children
  • Hi all, 

    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