Should we not to carry-over a status field value when duplicating a record?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yuri
    Member
    • Mar 2014
    • 8453

    Should we not to carry-over a status field value when duplicating a record?

    Should we not to carry-over a status field value when duplicating a record? But leave it default.

    Use case. When we duplicate a completed Meeting, in most cases we wouldn't need the status to be 'Completed'. Should we have such a logic for all entity types?
    8
    Set the status to default
    75.00%
    6
    Carry-over the status from a duplicated record
    25.00%
    2

    The poll is expired.

    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.
  • item
    Active Community Member
    • Mar 2017
    • 1476

    #2
    Hi,
    i have vote "Set the status to default"...
    I see other vote "Carry-over the status from a duplicated record" but if explain why, we can understand

    So maybe :
    "duplicate" or "clone"

    And what about "duplicate checker" ? Clone can bypass duplicate checker ?

    Brainstorming

    Yuri, very nice idea this post


    EDIT : https://forum.espocrm.com/forum/deve...3-clone-entity
    Last edited by item; 11-02-2023, 08:20 PM. Reason: edit : in the past i have asked this i think
    If you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks.​

    Comment

    • yuri
      Member
      • Mar 2014
      • 8453

      #3
      Duplicate checking is applied for duplicates I believe, supposed to.
      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

      • bradaks
        Active Community Member
        • Aug 2017
        • 251

        #4
        We have clients that duplicate a custom entity for ease of creation. Status for us should always be set back to default as it is a new record that requires a new workflow to be complete.

        Comment

        • yuri
          Member
          • Mar 2014
          • 8453

          #5
          Implemented https://github.com/espocrm/espocrm/issues/2885
          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

          Working...