Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key - InfoPath Dev
in

InfoPath Dev

Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key

Last post 11-26-2012 05:50 AM by DC Forms. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 11-20-2012 07:39 AM

    • DC Forms
    • Top 150 Contributor
      Male
    • Joined on 06-14-2012
    • Washington, DC
    • Posts 76

    Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key

    I have a document type that I believe Ernesto helped me set up. I am attempting to update the database connection string. The new connection string validates, but am unable to save the change because I am receiving a validation error.

    I do not recall how this document type was originally set up without the table having an identity column. See the attached image for illustration.


  • 11-24-2012 11:08 AM In reply to

    Re: Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key

    Hi DC Forms,

    Do you have one of the fields marked as "Key"? If not, that could explain why you're getting the error message. We present that message to prevent people from creating an incorrect mapping since you will need a key field.

    I will forward this to Ernesto and ask him to contact you first thing Monday.

    More soon,

    Patrick Halstead
    Project Manager at Qdabra
  • 11-26-2012 03:59 AM In reply to

    Re: Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key

    Can you compare the design of the new and the original tables? I'm guessing that the original table had a primary autoincrement key, and thus the SQL mapping was saved without a key defined in DAT.

    Let us know what you find. Thanks.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 11-26-2012 05:50 AM In reply to

    • DC Forms
    • Top 150 Contributor
      Male
    • Joined on 06-14-2012
    • Washington, DC
    • Posts 76

    Re: Unable to Update Document Type > Database > Connection String, Validation Error: No Identity Column & No Primary/Foreign Key

    Ernesto,

    You are correct. The SQL Server Import and Export Wizard did not maintain the Primary Key and (Is Identitiy) setting for the ID column when I migrated the database.

    FYI, after making the database changes I did have to exit the the document type settings in DAAT (going back to the catalog) and then went back in to the document type database settings to change and save the new connection string. It appears the database configuration is cached in DAAT- I kept getting the error when trying to save the new connection string after the database changes were made. I had the document type's database tab open as I made the database changes.

Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.