Make unique naming cover all areas

Last I tried, when I upload, to a projects directory, a file that I classify as a facilities document, it generates a name based on my setup but it doesn't check to see if that number already exists in the vault (specifically the Master folder).  I believe this is a weakness in the system since unique naming is an important aspect of document practices.   Is there a reason why this isn't set up as such since you have the technology to check within projects for uniqueness.  I bring this up because I ran into this problem and it negates the power of the technology. I end up having to first find the last sequence in Master.  Manually name the first upload, then proceed with automatic for the rest of the uploads.

  • Guest
  • Jun 27 2019
  • Shipped
Meridian Cloud
  • Attach files
  • Admin
    Coen Vromans commented
    22 Jun, 2022 01:32pm

    This feature is introduced in Meridian Cloud 2021.1

    Attachments Open full size
  • Admin
    Coen Vromans commented
    13 Apr, 2021 07:59am

    The problem of the unique sequence numbers is caused by an initial data import with existing sequence numbers. When new documents are added in Meridian de numbering syntax starts from scratch and does not take into account the imported documents. This ability to set the next sequence number is introduced in Meridian Cloud 2021.1 with spike MPS-34008

    Attachments Open full size
  • Admin
    Arjen Bos commented
    27 Nov, 2019 03:49pm

    We have seen different scope of handing out numbers between customers.

     

    We see three options:

     

    - Dependent on all properties: 

         PRJ1-CLS1-00001

         PRJ1-CLS2-00001

         PRJ2-CLS1-00001

    - Dependent on project only

         PRJ1-CLS1-00001

         PRJ1-CLS2-00002

         PRJ2-CLS1-00001

    - Global 

        PRJ1-CLS1-00001

         PRJ1-CLS2-00002

         PRJ2-CLS1-00003

        

    We are gathering more input and may  allow changes accordingly. 

    Attachments Open full size
  • Admin
    Arjen Bos commented
    12 Nov, 2019 02:38pm

    Let's discuss this input in a future meeting to better understand your requirement.

    Attachments Open full size
  • Chris Tsangarides commented
    9 Jul, 2019 01:15pm

    Hi Coen,

    Thank you for your additional suggestion for automatic naming/numbering of Project & Generic Document types. The additional suggestion relates to, but it’s not the same as the suggestion from

    For that reason, I have created a new Idea with your suggestion:

    https://accruent1.aha.io/ideas/ideas/NBL-I-37

    In the future, please create a new Idea for new or related suggestions.

    We will continue the discussion in this Idea about the verification of file names throughout the repository so that Meridian avoids duplicate file names.

    Chris Tsangarides
    Product Manager
    Accruent

    Attachments Open full size
  • Coen Vromans commented
    9 Jul, 2019 07:29am

    Hi Chris, At the moment the usage of the sequence numbers is only available for Facility Documents in Power User. Meridian Cloud Business customers need automatic naming for Project Documents and Generic Documents.

    FacilityDocumen...
    GenericDocument...
    Attachments Open full size
  • Chris Tsangarides commented
    8 Jul, 2019 10:01pm

    Thank you for your suggestion.

    Can you help me understand if this occurred in the past few days?

    I ask this because the configuration of the sequence number was adjusted, and this may have caused the issue.

    Either way, please let me know if this is repeatable or an isolated case. This will help prioritize the work within development.

    Chris Tsangarides
    Product Manager
    Accruent

    Attachments Open full size
  • Coen Vromans commented
    4 Jul, 2019 12:29pm

    I really like the idea to have automatic naming in Meridian Power and Meridian Explorer for Generic and Project Documents

    Attachments Open full size

Related ideas