Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com - InfoPath Dev
in

InfoPath Dev

Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com

Last post 03-19-2013 07:51 AM by jazaddict. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 03-14-2013 09:29 PM

    Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com

    Ugh....got this tonight.

    I googled it & made the xsn into a cab, Tried ripping out the offending lines from the manifest file in notepad..over& over & over....I prolly tried it 25 times or more; same error on  a new line.  It finallly started erring on forms & stuff that I know are current and necessary.

     Interestingly, I tried backup file from a couple of sessions back and while it'd open in IP, it gave me the same type of error when I extracted the manifest and tried opening in design.....wierd.

     Any hope here or am I gonna be set back to the previous save?

  • 03-17-2013 12:27 PM In reply to

    Re: Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com

    Hi Jazz with a Back Beat,

    Did your database change? If not, I'm guessing the XSN got corrupted in which case, it's back the "last known good".

    I guess it's all about timing.

    Cheers,

    Patrick Halstead
    Project Manager at Qdabra
  • 03-18-2013 05:32 AM In reply to

    Re: Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com

    well, by "did the database change", if you mean did I add any controls then "yes".

     ...but beyond that I have a question...when I rename the xsn to CAB, do I need to extract ALL the files to an editable location so that when I change the Manifest file it's surrounded by its companions?  Because I'd merely moved that one file & it occured to me that it might well never see the all those other files & thats why EVERY single control was coming up as a missing compontent errror???

  • 03-19-2013 07:51 AM In reply to

    Re: Error details: The keyref 'ApprovalGroup_2016' does not resolve to a key for the Identity Constraint '{http://schemas.microsoft.com

    No joy on extracting all files from the CAB (same result as just extracting the Manifest.xsf)....same issue: after using notepad to delete the offending lines referenced in the error message, more offending lines would come up continually....I concluded the entire thing was hosed beyond repair.

     

    HOWEVER!!!!!

     In MY case the most recent save was published to a custom form library, consequently the .xsn is retrievable from that location.  Here's how:

    • From your browser navigate to the library
    • Select Library Tools > Library > Connect & Export > Open with explorer
    • In the explorer window drill into the Forms folder and find the TEMPLATE.XSN file
    • This is your "project.xsn", so copy it from there and paste it to a location on your development PC
    • Right-click "Design", and it'll open in Infopath from which you can save as to your development folder. 

    Whew!  what a relief.   My newest mantra is "Rename Saves Often.....Rename Saves Often....."

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