My first guess on this issue.

You have an EXISTING archive form for this form that at some point has been 
turned off.  We do not delete the archive form as it has data in it.

Now, you turn it back on and the system is creating the archive.  For the most 
part, it is already there.  However, at some point, you have added a unique 
index that was not there previously.  When the system is trying to create the 
archive form and apply the index, there is data in the archive that is 
violating the unique index so it cannot be created.  This is returning an error 
during create of the archive.  That causes the request to turn on archiving to 
return an error and then to deactivate archiving for that form as there is not 
a valid archive form.

So, what data is in your archive form already?
Is there a unique index on your form that is being violated by data already in 
the archive?
Can you clean the data that is not unique or remove the data from the archive 
form before you try and turn it on?
Is the unique index valid for the data (it seems to be as you are not having 
trouble with the production form, then why may there be dups in the archive 
data?)

At one point, we did not clone the indexes to the archive, only the form 
definition.  We do clone it now to keep the same rules on your archive as is on 
your regular data.

Anyway, this is my guess.  The second error that you are shown is the detail 
for why you are getting the first error.  It seems to come back to a unique 
index violation in the data when trying to apply an index.

Doug Mueller

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Madhu V
Sent: Sunday, April 19, 2015 7:10 AM
To: [email protected]
Subject: Archive form's view is not available in Database

Hi,
 
We are facing some problems while saving a regular form and getting the below 
error (Screen shot).
The form has got archival form and but which is not visible after we got this 
warning message.

Few Observations:
 
We had verified that there is enough memory.
We tried disabling the archival feature and creating the new fields but same 
warning repeated.
Old Data still exists in the Archive table.
The archive from is not visible via Developer Studio.
The main form has no isues.
 
Please let me know your views on this.
 
Regards
Madhu

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to