Personal Email accounts - Backend validation failure (Monitored Folders - Junk)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Jakub Grufik
    Senior Member
    • Aug 2022
    • 361

    Personal Email accounts - Backend validation failure (Monitored Folders - Junk)

    Hello,

    after upgrading to espo v 7.2.0 we are facing issues with creating a Personal Email Account. In Monitored Folders, we are used to use 2 folders - INBOX which is default, and JUNK which is spam folder.(screen1) After upgrade we are getting Error 400: Bad request Backend validation failure, Field: monitoredFolders, Validation: valid (screen2) after adding JUNK Folder to be monitored. When we select just INBOX everything is fine and we can save it. With JUNK we are not able to save it.

    If I try to edit the already existing Personal Email account that has JUNK folder saved I am able to remove JUNK save it, but when I add JUNK again I am not able to save it even when it was there before.

    I checked our email settings and the Spam folder is enabled and it seems like it is working properly.

    Any idea what could have happened?

    Thanks a lot!
    Click image for larger version

Name:	junk2.jpg
Views:	582
Size:	12.5 KB
ID:	83066Click image for larger version

Name:	junk1.jpg
Views:	427
Size:	14.7 KB
ID:	83067
  • Jakub Grufik
    Senior Member
    • Aug 2022
    • 361

    #2
    Sorry, I forgot to insert screen from console

    Comment

    • yuri
      Member
      • Mar 2014
      • 8417

      #3
      Will be fixed in the next version. Bummer that we missed that while testing.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      • yuri
        Member
        • Mar 2014
        • 8417

        #4
        Fix: https://github.com/espocrm/espocrm/c...86f762426cca7e
        If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • Jakub Grufik
          Senior Member
          • Aug 2022
          • 361

          #5
          Hey yuri,

          thanks a lot!

          Comment

          • shalmaxb
            Senior Member
            • Mar 2015
            • 1592

            #6
            I get the same error with a custom field (enum) in a custom entity. Though I did not configure any validation in that field.

            Comment

            • TripitakaBC
              Junior Member
              • Dec 2021
              • 5

              #7
              I concur with shalmaxb - I am getting an error 400 - Field Validation Error on a custom field that previously worked before upgrade. I am on 7.2.4

              Comment

              Working...