If a field is both in the detail view and the side panel full edit will "conflict"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Kharg
    Senior Member
    • Jun 2021
    • 462

    #1

    If a field is both in the detail view and the side panel full edit will "conflict"

    Summary:
    When a field is present in both the detail view and the side panel, entering full edit mode only allows editing of the duplicated fields in the side panel. The same fields in the detail view do not enter edit mode.

    Tested and reproduced in the demo (EspoCRM 9.1.8).
    No errors in the console log or in the logs file.

    Steps to Reproduce:
    1. Go to the entity manager.
    2. Visit the layout manager of an entity and add an existing field from the detail view to the side panel.
    3. Visit a record and press the Edit button to enter full edit mode.
    4. Observe that the duplicated fields in the detail view do not enter edit mode, while those in the side panel do.

    Actual Behavior:
    Only the duplicated fields in the side panel are editable in full edit mode; the same fields in the detail view remain in view mode.

    Expected Behavior:
    - It should not be possible to add the same field to both the detail view and the side panel.
    Or
    - If a field is duplicated, both instances should be editable and stay in sync, or the UI should prevent editing in one location if syncing is not possible, preventing going into inline edit.

    Recording:


    Click image for larger version  Name:	image.png Views:	0 Size:	120.7 KB ID:	120801
  • yuri
    EspoCRM product developer
    • Mar 2014
    • 9295

    #2
    Two fields conflicting on the same form is an expected behavior. Not a bug.

    Regarding the restriction to add. It was there, at least for one side I believe. Maybe not implemented for another.
    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


    • Kharg
      Kharg commented
      Editing a comment
      Thank you, I thought it could be an expected behavior but did not find any past topics or reference in the documentation.

      Disabling inline edit while in full edit mode could also be a "solution" as well, preventing duplicated fields would be the best solution probably.

    • yuri
      yuri commented
      Editing a comment
      Disabling edit won't be enough to prevent all issues.
  • yuri
    EspoCRM product developer
    • Mar 2014
    • 9295

    #3
    Implementing it for the side panel layout is bit tricky. I treat it as not a bug, but not implemented.
    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
      yuri commented
      Editing a comment
      Moreover, these are separate views and their layouts are loaded separately, which complicates handling this scenario. Removing the field after both views are ready could be a viable solution.
      Last edited by yuri; Today, 05:54 PM.

    • item
      item commented
      Editing a comment
      Please, consider too when a field is read-only. In my case, i have some read-only in both detail->tab and on side-panel.

    • yuri
      yuri commented
      Editing a comment
      It's not possible without complete overhaul. Even if I wrote it from scratch, I would implement it the way as it's now, otherwise, it would complicate things drastically for a very small benefit.
Working...