Hi John,
Apparently, it's a know issue:
SW00380659 - "ARERR 9070 - Message not in catalog" while creating join with
the User form
I can't see any details on the defect but in my case, I was including several
of the special fields from the User form including "Login Name", Password,
"Group List" and "Assigned To". Fortunately, I was able to renumber the
Password field on the join form without losing any inherent functionality, so I
have a workaround.
Hope this helps someone.
Larry
On Jan 14, 2011, at 12:11 PM, Reiser, John J wrote:
> Larry,
>
> I ran into this a few years back but I can't swear it was the same error
> message.
> There is something funky about using too many core fields in joins. My errors
> occurred when trying to send email notifications and I had field ids like
> 101, 103, 104 & 106 included in the join.
> My error message kept including the 106 field id as the problem but it was
> another core field that we removed because we needed to the Group ID.
>
> ---
> John J. Reiser
> Remedy Developer/Administrator
> Senior Software Development Analyst
> Lockheed Martin - MS2
> The star that burns twice as bright burns half as long.
> Pay close attention and be illuminated by its brilliance. - paraphrased by me
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
