Silent Import and Custom fields as required fields

Hi,

Problem: my software imports documents, that have required fields: Custom1, Custom2.
I have read a TechArticle: 52768 , which says:
"Validated custom fields, 1-12, 29-30, ...[cut] are not supported by ContextItems.
You may, however, catch the OnInitDialog Event of the dialog then call SetAttributeValueByID to preset validated fields 1-12, 29-30 ...",
but in my case I have no OnInitDialog Event, because I have no Dialog. Am I right ? Any solutions?

Thank you,
A-S

Find more posts tagged with

Comments

jny

Hi,

Problem: my software imports documents, that have required fields: Custom1, Custom2.
I have read a TechArticle: 52768 , which says:
"Validated custom fields, 1-12, 29-30, ...[cut] are not supported by ContextItems.
You may, however, catch the OnInitDialog Event of the dialog then call SetAttributeValueByID to preset validated fields 1-12, 29-30 ...",
but in my case I have no OnInitDialog Event, because I have no Dialog. Am I right ? Any solutions?

Thank you,
A-S

Would you show the code you use for your importing? If you use the ImportCmd as demonstrated in the technical article 52768, you should be able to set up a dialog (which is the NewProfileDlg Object) off the ImportCmd Object.

Stat

...you should be able to set up a dialog (which is the NewProfileDlg Object) off the ImportCmd Object.

Yes. You are right, but the problem is : if document has required fields then I need to give them to the context items. These are for example, custom1 and custom2. Till context doesn't recieve these fields I will see Profile Dialog. It's written in Article 52768 "Validated custom fields, 1-12, 29-30, ...[cut] are not supported by ContextItems"

jny

Yes. You are right, but the problem is : if document has required fields then I need to give them to the context items. These are for example, custom1 and custom2. Till context doesn't recieve these fields I will see Profile Dialog. It's written in Article 52768 "Validated custom fields, 1-12, 29-30, ...[cut] are not supported by ContextItems"

Unfortunately, there are no contextitems for any of the validated lookup fields.

I see two approaches to get around this for you:

1. Use the low-level (imanage.dll) api's to create a document object and checkin the file. Like so:

[C#]

=========================

// Server name
const string SERVERNAME = "DSS_WIN2003SERV";

// File path to upload/import to WorkSite
const string importFile = @C:\Temp\test.docx; // -- Arbitrary example of a local file path

// Create an instance of the DMS (root) object
ManDMS dms = new ManDMS();

// Add a server to the session object
IManSession sess = dms.Sessions.Add(SERVERNAME);

// Log onto a session
sess.TrustedLogin(); //TrustedLogon

try
{
if(sess.Connected) //Session is connected
{
// Get target database
IManDatabase db = sess.Databases.ItemByName("WS8DSS1");//sess.PreferredDatabase; //Arbitrary example of a target db
// Create a document object
IManDocument doc = db.CreateDocument();

// Profile document with required fields
doc.SetAttributeByID(imProfileAttributeID.imProfileAuthor, sess.UserID);
doc.SetAttributeByID(imProfileAttributeID.imProfileOperator, sess.UserID);

// Get target document class object
IManDocumentClass docclass =
db.SearchDocumentClasses
("DOC", imSearchAttributeType.imSearchBoth, true).ItemByIndex(1);
if (docclass != null)
{
doc.SetAttributeByID(imProfileAttributeID.imProfileClass, docclass.Name);
if (docclass.SubClassRequired)
{ // Get target subclass
IManDocumentClass subclass =
docclass.GetSubClasses
("", imSearchAttributeType.imSearchBoth, true).ItemByIndex(1);
if (subclass != null)
doc.SetAttributeByID(imProfileAttributeID.imProfileSubClass, subclass.Name);
}

// Get target document application type from import file path
IManDocumentType doctype = db.GetDocumentTypeFromPath(importFile);
if (doctype != null)
doc.SetAttributeByID(imProfileAttributeID.imProfileType, doctype.Name);

//Or you may hardcode the app type if you're certain of it.
//doc.SetAttributeByID(imProfileAttributeID.imProfileType, "WORD"); // Assuming the upload file is a Word document.

// Arbitrary example of validated CLIENT/MATTER fields values
doc.SetAttributeByID(imProfileAttributeID.imProfileCustom1, "5400");
doc.SetAttributeByID(imProfileAttributeID.imProfileCustom2, "Y");

// Commit profile and upload physical file to the WorkSite database
IManCheckinResult result = doc.CheckInWithResults
(importFile, imCheckinDisposition.imCheckinNewDocument, imCheckinOptions.imDontKeepCheckedOut);
if (result.Succeeded)
{
MessageBox.Show("Imported document as number/version: " + doc.Number.ToString() + "_" + doc.Version.ToString());
}
else
{
// Display errorlist
for (int i=0; i <= result.ErrorList.Count; i++)
{
string serror = result.ErrorList.ItemByIndex(i).AttribID.ToString() + ": " + result.ErrorList.ItemByIndex(i).Description;
MessageBox.Show(serror);
}
}
}
}
}
catch(Exception ex)
{
// TODO: handle errors
MessageBox.Show(ex.Message);
}

=========================

2. If your Custom1/2 fields are required by a particular doc class, then you could add a non-required class first when invoking your ImportCmd. After the document is imported successfully, you may use the imanage.dll API's to update the profile with the intended doc class and custom 1/2 fields that are required by it. You may do so by calling the SetAttributeByID Method (as demonstrated above) off of the imported document object returned by the "ImportedDocument" ContextItem. Don't forget to call Update() afterwards.

Stat

Unfortunately, there are no contextitems for any of the validated lookup fields.

I see two approaches to get around this for you:

1. Use the low-level (imanage.dll) api's to create a document object and checkin the file. Like so:

[C#]

=========================
[cut]
=========================

2. If your Custom1/2 fields are required by a particular doc class, then you could add a non-required class first when invoking your ImportCmd. After the document is imported successfully, you may use the imanage.dll API's to update the profile with the intended doc class and custom 1/2 fields that are required by it. You may do so by calling the SetAttributeByID Method (as demonstrated above) off of the imported document object returned by the "ImportedDocument" ContextItem. Don't forget to call Update() afterwards.

Thank you for your help. It was very helpfull