More on CustomAttributes

System

Hello Techies--

Special thanks for the answer regarding CustomAttributes--the database settings will solve my need for assigning known status values, (e.g. WIP, Approved, Released, etc.) however, I also need to store dynamically created change request values generated from an outside database, then imported back to WorkSite. I'll need to offer the end user the ability to assign/deassign these values to a document set, as well as offer them a "search by" CR# feature once assigned. So, therein is my design concern.

I understand that CustomAttributes 13-28 do not need to be pre-assigned--however, neither do these fields appear on the default "Properties" window for docs. So, does this translate to developing new profile/search templates through the dialog editors?

Thanks,
--p

Paula DiTallo - Middleware Architect/ .NET Developer
plditallo@metro-design-dev.com

jny

The InsertParentCustomField and InserChildCustomField methods are used to add dynamic metadata to validated (lookup) fields, 1-12, and 29-30, which is exposed by the IManAdmin.dll 8.0. (Please note that these methods are only available in the 8.0 version of the IManAdmin.dll. and that this is a hidden interface and currently does not support late-binding.)

[VB Example code]

Dim dms As New IMANADMIN.NRTDMS
Dim sess As IMANADMIN.NRTSession
Dim db As IMANADMIN.INRTDatabase2

Set sess = dms.Sessions.Add("<servername>")
sess.Login "<NRTAdmin_User>", "<password>"

Set db = sess.Databases(1)
db.InsertParentCustomField nrCustom1, "Custom1 name", "Custom1 description", True
db.InsertChildCustomField nrCustom2, "Custom1 name", "Custom2 name", "Custom2 description", True

NOTE: For adding new values to non-parent/child validated fields, i.e., Custom3, Custom4, etc., use InsertParentCustomField method.