Changing the author of a workspace

Hi, everybody:

I'm trying to create a C# program that using the iManage dll can change (under some functional circustances) the author of an existing workspace.

I'm using the next sentence:

currentWS.SetAttributeByID(imProfileAttributeID.imProfileAuthor, newAuthor);

but I'm getting an exception advising me that this property is a readonly one.

It would be possible do it???

Thanks in advance

Find more posts tagged with

Comments

Carbon

So, do you have control over this environment? The first thing that comes to mind is that someone else is editing the properties of the WorkSpace, locking it in the docmaster table.

The second thing that comes to mind is the fact that you can't change the Owner of a WorkSpace through the GUI, so I wonder if the API would have access to that option also? The only way I've been able to do it is via SQL.

dopey

You need to have full access to the workspace - either being owner or having an acl with your name or group on it providing full access.

To debug, you can look at the workspace's EffectiveAccess property. This should be imAccessRight.imRightAll or it won't work.

I just did a quick test, and as owner of the workspace I could change the owner to somebody else with the code

ws.Owner = ws.Database.GetUser("godzilla");
ws.Update();

ManoloMadrid

It works perfectly.

Thanks, thanks, thanks

ManoloMadrid

Perhaps I've been too optimistic. In one example it worked perfectly but in other it didn't.

I'm going to check deeply but I think that is going (it has to) work

ManoloMadrid

Unfortunately I was too optimistic.

When I enter in Filesite with the new Owner, I see the updated workspace in the "My Folders folder" !!!Good signal!!!.

But when I check the workspace properties I see that the old Owner continues being showed (also after restarting Filesite).

I´ve checked the database tables and I've found that the is correctly updated in the Projects table, but not in the Docmaster table (the XML related with the project).

It's supossed that I have to look for that document and update the owner too ???

Thanks in advance

Migrateduser

You cannot really safely change the owner of a WorkSpace after it has been created through the 3-tier API.

Arwin

In our experience it is perfectly possible, but you need to do both of the options suggested here. The first will change it on the workspace profile (docmaster) and the second will change it in the Projects table:

currentWS.SetAttributeByID(imProfileAttributeID.im ProfileAuthor, newAuthor);
ws.Owner = ws.Database.GetUser("godzilla");

Ben_inform

I just tried this and this worked:
m_workspace.owner = iDB.GetUser(Me.txtNewOwner)
m_workspace.Update

but this failed:

Call m_workspace.SetAttributeByID(imProfileAuthor, Me.txtNewOwner)

with a 'property is read only' message.

The end result is the owner is not changed.
ANyone actually dont this as opposed to think you can in theory ?

Is is possible to get the docnum for the xml webdoc and then do and api search and then updat that ??

Arwin

Which version are you using?

I find that sometimes I need a different approach - I always use this for Documents, Tabs, DocumentFolders and DocumentSearchFolders. Sometimes Worksite's API seems to be a little inconsistent on these matters, unless of course I'm overlooking something myself.

Assuming that you have sufficient rights to change the Author (which typically you should if you can change the Owner), you can try this:

myAdditionalProperty = myWorkspace.AdditionalProperties.ItemByName("iMan___" & CStr(AttrId))

If myAdditionalProperty Is Nothing Then
myAdditionalProperty = myWorkspace.AdditionalProperties.Add("iMan___" & CStr(AttrId), Value)
Else
myAdditionalProperty.Value = Value
End If

So far I've used exactly what you've got above though. But I notice you are using Visual Basic 6.0, whereas I am using Visual Basic .NET. Even there, I've come across some weird differences.

I also like to use the UpdateWithResults feature and the IManage.IManProfileUpdateResult object. Even here the implementation is a bit shoddy (sometimes it returns nothing, which means ok, sometimes the errorlist is nothing, which is ok, etc.), but I wrote this function to compensate for it and parse it to maximum effect:

Private Function reportProfileUpdateResults(ByVal myResults As IManage.IManProfileUpdateResult) As Boolean
Dim i As Integer
Dim sAttr As String
If myResults Is Nothing Then Return True
If myResults.ErrorList Is Nothing Then Return True
For i = 1 To myResults.ErrorList.Count
'do something with the error item, for instance:
debug.print(myResults.ErrorList.ItemByIndex(i).Description)
Next
Return myResults.Succeeded
End Function

By the way, this forum needs a code tag. Smiley Wink

Your final suggestion is a definite no. That should never be necessary, and on the API level, those two are not typically separate objects. The docmaster is used as a property container for several types of objects. From the looks of things, this will likely be replaced in future through the use of NVPS tables or similar tables dedicated to meta-data, which should finally get rid of the current limited number of metadata fields.

jny

Unfortunately I was too optimistic.

When I enter in Filesite with the new Owner, I see the updated workspace in the "My Folders folder" !!!Good signal!!!.

But when I check the workspace properties I see that the old Owner continues being showed (also after restarting Filesite).

I´ve checked the database tables and I've found that the is correctly updated in the Projects table, but not in the Docmaster table (the XML related with the project).

It's supossed that I have to look for that document and update the owner too ???

Thanks in advance

In 8.x, you may change the workspace ownership like so:

//Assuming:
//ws is a valid workspace object
//newOwner is a valid user object
if(true == ws.IsOperationAllowed(imModifyFolderOp))
{
ws.Owner = newOwner;
ws.Profile.SetAttributeByID (imProfileAttributeID.imProfileAuthor, newOwner.Name);
ws.Update();
}

dabird

By the way, this forum needs a code tag.

You can insert code snippets in your post, like so: [code]Here is my code block[/code]

Here is my code block