This is an invalid type of primary key for the autosplitkey

upasanisandipupasanisandip Member Posts: 405
Hi,
I am getting error in Purchase Order Entry
This is an invalid type of primary key for the autosplitkey facility. It should be Integer/BigInteger/Decimal/GUID.


Anyone knows about this solution.


Thanks,
Sandip.

Comments

  • vikasvikas Member Posts: 46
    Hi,

    To use the autosplit facility, the primary key of the source table must end with a Integer Integer/BigInteger/Decimal/GUID.

    Like, in Purchase Line table the primary key is "Document Type,Document No.,Line No.", which ends with Integer (Line No. is a Integer type)
  • Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    Did you change the default sorting on the subform?
  • upasanisandipupasanisandip Member Posts: 405
    Hi Mark Brummel,
    Yes I have changed the default sorting order system in subform.

    How can I solve this problem?


    Thanks,
    Sandip.
  • Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    You need to change the default order back.

    Why do you want to sort the lines differently? Mabye there is another solution.
  • DenSterDenSter Member Posts: 8,307
    Don't EVER change the primary key of ANY standard Navision table. That's all I have to say about that :).

    By the way, for autosplitkey to work, you need to have an integer as the last field of the Primary key of the table.
  • Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    DenSter wrote:
    Don't EVER change the primary key of ANY standard Navision table. That's all I have to say about that :).

    By the way, for autosplitkey to work, you need to have an integer as the last field of the Primary key of the table.
    ]

    I do not think he has done that. He has changed the sorting of the form, not the primairy key.

    But nontheless I fully agree with you never to change primairy keys in navision.
Sign In or Register to comment.