Randy,

We already stumbled about situations where ARServer or one of its components 
picked the wrong system from. Why does it happen? Because the system forms are 
in most cases identified by field ids. There is a ARGetListSchema API call 
where one can specify which field(s) to look for. So for example the User form 
is usually identified by field ids 101, 102 and 104. The Email Messages form is 
identified by field 19006 (and the other email related forms have their own 
unique field id as well). In your environment multiple forms contain a field 
with id 19006. The Email Engine simply picks the first one in this case. I’m 
not sure if the form alias has impact on the sort order. As far as I know the 
sort order is related to the schema-id of the form. Creating an overlay on a 
base form can change the ordering too.

Like Chintan has noted and quoted from the docs .. avoid the use of this kind 
of reserved field ids. 
1) Don’t use archive feature for system forms. 
2) Don’t create a copy of a system form (if necessary create new ids for all 
reserved fields). 
3) Don’t join system forms (unless you change the field ids).

While it’s working again in your environment, it could break in any later 
version or as soon as you touch the wrong form.

-John-

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to