Integration Center choking on a Custom Folder subtype

Went through the Developers Guide's AddressBook example tweaking names and such and my custom subtype folder works well with OpenText. My custom LLNode children and WebNodes work as I want and the "Add Items" list behaves beautifully.

The only problem is when our Data Migration people try to create the custom folder In OpenText Integration Center they get an error. They are creating a regular folder and then updating the subType. The folder creates, but then throws the following error:

Content Server 2010 (LAPI): Could not find object manager for object type: 5111.

Any "oh yeah" moments out there? I could have come up with a brand new way of messing this up, but misery loves company and I'm usually not that creative!

Any advise is greatly appreciated!

Bobby

Find more posts tagged with

Comments

Hans Stoop

Hi Bobby,

AFAIK there is no supported way of changing the subtype. Issues you may run into aare that facets and search do not have registered the correct subtype.

As to your original problem, you problem need to add support for your own subtype to the Integration Center.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Montag, 12. August 2013 23:12
To: eLink Recipient
Subject: Integration Center choking on a Custom Folder subtype

Integration Center choking on a Custom Folder subtype

Posted bybjbrimm@tva.gov (Brimm, Bobby) On 08-12-2013 17:06

Content Server 2010 (LAPI): Could not find object manager for object type: 5111.

Any "oh yeah" moments out there? I could have come up with a brand new way of messing this up, but misery loves company and I'm usually not that creative!

Any advise is greatly appreciated!

Bobby

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

Bobby_Brimm

Thanks, Hans!

I will look for Integration Center doc on custom subtype support. I would think that custom folders are not that rare, so surely there is some documentation on this site... just gotta put on my detective's hat.

The plan is to create the custom subtype normally for new content, but our Migration team said that Integration Center could not create the subtype directly so he was creating an empty folder and trying to change the subtype.

If/When I find the magic words, I'll post them here for the next person!

Bobby

Bobby_Brimm

Final Update. We decided to leave the custom folder out of the Migration equation. After Migration, we will run recursive code to change all folders from a specified point down from subtype = 0 to our new subtype using llFolderType.NodeUpdate(node,updateInfo,context ).

Bobby