Danila,
As noted in our previous comments in this thread, the ARLoadARQualifier method only deals with qualifications expressed in terms of fields from a single form. So I suggest you use one of the approaches given below (ordered in what I think is easy/practical to more hard/complete): 1. Simply create the qualifications "by hand" - Instead of trying the conversion from readable string qualification to internal structure, build the structure itself. It is verbose, but actually not that hard to build the qualification. As a helper in this process, you can create a qualification of your liking in one of the Join forms within Admin Tool, then get that object (GetSchema) in your code, see how the qualification looks in terms the nested objects and their values. With this evaluation in your hand, now simply create a qualifier object just like that simply within your code. 2. As previously noted, try using Java API or .NET API - may be just a tiny program that does this specific thing and writes back the data to a temp file or some thing; which your rest of the code can grab. Just a thought. A word of caution though - you might be tempted to convert rest of your code too into one of these, by looking at the ease of use etc. :-) 3. There is some what of a round about way to parse the qualification programmatically. There is this application special command that can do this task: Application-Parse-Qual-SField <form1> <form2> <qualification_string> Converts a Set Fields or Push Fields filter qualification string into an internal representation. [Look for Special Commands documentation within AR System 7.0 Workflow Objects book] Well, how would you use this you ask? Put such a filter in a "Qualification string accepting form", put a set fields action that assigns value into a "Parsed Qual CharField" using assignment expression as $PROCESS$ Application-Parse-Qual-SField <form1> <form2> <qualification_string> Now, you would submit an entry on to this form (i.e CreateEntry API call in your code) with form1, form2, qualification_string field values filled in; and on submit, the filter would fire and do its magic and store the parsed qualification into the Parsed Qual CharField field. Assuming, all goes well, you can now do a get entry on the just created entry and look for the value in this field to extract what the readable qualification string was parsed into. BTW, what you get here is an encoded string representation of the qualification. This can be loaded into a qualifier object using ARDecodeARQualifier method. Yes, I know this is quite a round about way to do what you want to do. 4. Finally, if you have to have this qualification parser/formatter library; although I would not encourage considering all the special cases/nuances etc, feel free to go for it! I am sure it will be wonderful if we made the qualification processing logic as easy to use API, it would really help and avoid folks like you spending energy on these kinds of things instead of focusing on whatever specifically they're trying to solve. Regards Appajee ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Beketov Danila Sent: Wednesday, May 23, 2007 2:06 AM To: [email protected] Subject: How to create JOIN schema with Remedy C API Hi, listers It's me with the same question. How to create join qualification with Remedy C API? I use ARCreateSchema to create join form, but I don't know how to specify join criteria in ARCompoundSchema structure. Of cause, join criteria must consist of fields, which are in different forms. Danila __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
