ArcObjects Geoprocessing valid input workspace object types

Question

While attempting to automate the writing of records to the reviewer table utilizing the GP tool Write To Reviewer Table, is there an object type that is acceptable input for the in_reviewer_workspace parameter?

I have tried IWorkspace, IFeatureWorkspace, ISqlWorkspace, and a direct Catalog path to a connection file. The path is the only thing that has been successful. All other input objects return invalid parameter type for in_reviewer_workspace.

I am developing in C# at 10.3.1:

gp5.AddToolbox(@C:\Program Files (x86)\ArcGIS\ArcGISDataReviewer\Desktop10.3\ArcToolbox\Toolboxes\Data Reviewer Tools.tbx);

gp5.OverwriteOutput = true;

IVariantArray parameterswritedr = new VarArrayClass();

parameterswritedr.Add();

parameterswritedr.Add("Session " + drsessionid + " : " + sessionname);

parameterswritedr.Add(featurestowritetodr);

parameterswritedr.Add("OBJECTID");

parameterswritedr.Add("originname");

parameterswritedr.Add("reviewstatus");

gp5.Execute("WriteToReviewerTable", parameterswritedr, null);

DheerajVarshnay · Accepted Answer

The in_reviewer_workspace parameter of Write To Reviewer Table geoprocessing tool supports IWorkspace object type however the IWorkspace object should be created in such a way that IWorkspace.PathName property value is the database connection path. For example if you create the IWorkspace object using WorkspaceFactory.OpenFromFile(connectionFilePath,0) the GP tool should work successfully but if you create IWorkspace object using WorkspaceFactory.Open(connectionPropertySet,0) you might get the following error:

"ERROR 000622: Failed to execute (Write to Reviewer Table). Parameters are not valid.
ERROR 000623: Invalid value type for parameter in_reviewer_workspace."

This is the same behavior for all geoprocessing tools that take IWorkspace as one of the input parameters. I will recommend using "Create ArcSDE Connection File" geoprocessing tool to create the required sde connection file.

If you don't want to create the sde connection file you can use the approach used in Write Results to Reviewer Table: A Developer Sample instead of using the Write To Reviewer Table geoprocessing tool. Although this sample was created using 10.1 you should be able to use the same code in 10.3.1.