none
The values in the lookup table must be unique to a given level RRS feed

  • Question

  • This 2007 installation was migrated from 2003 some years ago.

    Lookup table on task level has two values (level 2) which have the same value.

    Whenever you try to edit the lookup table values (add, edit or delete values) you get the forementioned message.

    Investigation in the database reveals that only the first value (sort index is the only difference between the two records) is used within the project tasks.

    How can we delete the duplicate value, which is not used apparently?

    Thanks

    Wednesday, March 14, 2012 9:35 AM

Answers

  • Finally found a solution!

    Export to Excel revealed there were (amongst the many records) several duplicates we overlooked in the first place.

    Removind ALL duplicates solves the issue... of course...

    • Proposed as answer by Kashif Nizam Monday, April 2, 2012 1:14 PM
    • Marked as answer by winnes Monday, April 2, 2012 1:15 PM
    Monday, March 19, 2012 9:04 AM

All replies

  • I would change the name directly in the database.  Probably not supported, but I don't another way of getting past that error.

    Ben Howard [MVP] blog | web

    Wednesday, March 14, 2012 6:51 PM
    Moderator
  • Been there, done that... same thing.
    Been going through a lot of tables (Published/Draft) to find referenced fields.

    Only thing that comes to my mind is writing a piece of code (VBA/PSI) that:

    - Creates new custom field and lookup table (no duplicates of course)
    - Records all (task) custom field values (in all projects and tasks) in temporary store
    - Writes these values back into the new task lookup tables values (for all projects and tasks)
    - Use of this custom field in reports, views etcetera will need to be verified

    After verification and testing, old lookup table and custom field will be erased

    Unless someone would still come up with better alternatives

    Wednesday, March 14, 2012 7:18 PM
  • Finally found a solution!

    Export to Excel revealed there were (amongst the many records) several duplicates we overlooked in the first place.

    Removind ALL duplicates solves the issue... of course...

    • Proposed as answer by Kashif Nizam Monday, April 2, 2012 1:14 PM
    • Marked as answer by winnes Monday, April 2, 2012 1:15 PM
    Monday, March 19, 2012 9:04 AM
  • Thanks for the Post It Really Works.

    There are two values in my Lookup with doulbe space with the same text.

    'EPM does not Consider Double space as a single space'

    Thanks & Regards 

    Rishav Sujati

    EPM Technical Consultant

    Friday, January 24, 2014 2:04 PM
  • Hi Winnes,

    I know this become old post but currently i am facing the same issue in my env.

    When we trying to update/modify/create a new field in look up table, getting the below error.

    Error: 

    The lookup table could not be saved due to the following reason(s): 
    The values in the lookup table must be unique to a given level.

    As suggested, i have checked the fields in lookup table but no duplicate records exist(checked while exported values to excel and DB also).

    With enabling verbose ex logs, we are getting the below error:

    Error is: LookupTableDuplicateSiblingsDisallowed. Details: . Standard Information: PSI Entry Point:   Project User: <<farm account>> Correlation Id: <<ID>>  PWA Site URL: <<site url>> SSP Name: Project Server Service Application  PSError: LookupTableDuplicateSiblingsDisallowed (11053).

    Could you please suggest us in this request. thank you in advance. 

    Gangadhar

    Tuesday, February 5, 2019 7:27 AM