Yeah I've never actually tried createEntry in a join, you could say its broken but I believe its just not fully implemented, remember that a join form in remedy is nothing but a DB View which joins 2 T tables and stores relationships and joinIDs in a separate table. So by using createEntry against a join may work and create the entry, you will not get a return ID or a JoinEntryID since data is not stored in the join so (its like sending data down a black hole), rather in the underlying tables that create the link.
I agree this makes it very difficult when trying to work with the CMDB which is a mess of Joins ontop of Joins, easy solution if you require an ID to return is to look at the base forms of the join and push directly to those, which will then inherent into the Join. Hope this helps at least a bit, I've only begun API work with the C API myself so my word is far from an experienced cry. If you find a way to get that information returned I'd love to hear it. Cheers, -------- Curtis Gallant -----Original Message----- From: John Baker [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 11:24 AM To: [email protected] Cc: Curtis Gallant Subject: Re: Java AR API weirdness Chris, It must be a bug. I'm looking at the Entry in the debugger once it's been created, and the EntryKey Object has three values: * EntryID ("") * JoinEntryID (null) * SchemaID ("The Join Form") Clearly the JoinEntryID should have a value, and therefore I deem it broken. Which is a little annoying for anyone attempting to work with the CMDB. John _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
