Hi.
I renamed a resource that was assigned to a few users. This is in IM7.
When I accessed the user page to edit something, it gave me an exception, with an itemnotfound error referencing the old resource name.
Has anyone else come across this? Updating user didn't fix the problem.
Ankush
Did you do any explicit referencing of the OLD resource name e.g.
'accounts[xxx].attribute_name' in your form or workflow? Renaming the resource name does not automatically re-reference all them to the new name. You have to manually change them in each and every of the form and workflows *Unfortunately*.
No, this was a vanilla install of IM 7. I created a Solaris adapter and named it "Solaris". I then created resources accounts for certain users.
Then, I renamed the adapter to "Solaris 9". Thats when I started encountering this problem. On renaming it back to Solaris, it worked fine. Does it have anything to do with using a space in the resource name?
Thanks for the help!
Ankush
I see what you mean...
Just did a test on my own....if you rename your resource, it should be able to reassociate again...
But when I look into the user's profile, it still show the old resource name... If I do an update to it, the resource will not be found and an error will pop up.
I've previously submitted a similar case to Sun regarding renaming of resources, but there was no resolution.
I see that this is going to be a problem for large enterprise deployment where there are large number of resources...
Does anyone in the forum have a solution to this?
Message was edited by:
harrywkl
It seems that when i try to rename the same original resource to another name it worked.
On my previous test I renamed the original resource to a different name, then do a 'save as' to create another same resource instance and then change it to the name I want. This seem to cause IDM to get confused because there's a unique ID associated to the resource which is embedded in the user profile.
