Duplicate Key Issue with Custom Business Class One Field Key (Index)

Jeff Johnson

Hi,

We are having an issue with the following key field for a custom business class.  Receive duplicate key issue on index 10 and only 10.  It seems once 10 records are created in the business class (1-9), it gets stuck on index 10.  Receive duplicate key error on index 10.

GCSHCapExRequest is a KeyField

    Representation

        type is Numeric size 10

    Ontology

        business class is GCSHCapExRequest

        Context

            FinanceEnterpriseGroup

    Field Rules

        GCSHCapExRequest

            autosequence when blank

                minimize contention and gaps

What could we be missing here?  What is best practice for a key field for a custom business class.  Need just one index field to have unique records.

If we clear the business class - delete all records - say 33.  Import new records via ISD, the index starts again at 34, but we have seen where it goes back to 10 again after entering new records in the UI and save when expecting index to go to 35,36,37,etc.  Not sure why it is reverting back to 10 at times thus resulting in duplicate key error for index (10).

Thanks.

Jeff

cleverly

Do you observe any different behavior if you simplify a bit and use:    

    Field Rules
        GCSHCapExRequest
            autosequence
                minimize contention

?