Announcement

Collapse
No announcement yet.

Field value not saved

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Field value not saved

    Hello, today I discovered a bug in a range integer field.

    When I input a value in either the min or max sub-fields of the Range Integer field, the value is saved and no error is displayed. However, the field value disappears after a page refresh. The value is not written to the DB even prior to the refresh.

    The field is used in Real Estate Requests to filter the properties based on the number of bedrooms.
    I could not find another field that exihibits the same behaviour.

    I am almost certain this bug showed up after upgrading from 5.1.2 to 5.2.2. Real Estate extension version was 1.2.1. Upgrading to 1.2.2 did not solve the issue.

    Thank you for your help. Should you need any file or db dump, feel free to ask.
    Have a nice weekend!

  • #2
    Hi,

    I can't reproduce. Is this a custom field?

    Comment


    • #3
      Hello,

      in custom/Espo/Custom/Resources/metadata/entityDefs/RealEstateRequest.json
      1) remove in your field "notStorable":true option;
      2) check if json is valid;
      3) save;
      4) Clear Cache in Administration.

      Thanks
      Last edited by tanya; 06-04-2018, 09:32 AM.

      Comment


      • #4
        Hello yuri tanya, thank you very much for your kind help.
        Tanya's solution fixed the problem, though I don't understand how that field became notStorable.

        Have a nice day! Cheers

        Comment

        Working...
        X