Susan, Like most "Core ARS forms" (my term) the form is identified by a set of ARS fields with specific field ID's. The ARS server is likely preventing you from violating a "golden rule" of only have one "Email Messages" form.
You can work around this.. kind of ... By copying the fields to a new form and either assigning new field ID's or letting the Admin tool auto pick them. ( I strongly suggest that you set them in accordance to your design practices. ) More specifically arstruct.h (v6.3) identifies the following fields for that form. I have no idea if you only change one if the field ID's if that is "enough" to avoid the golden rule or not. ( You might have to avoid all of the field ID's below and possibly others too.) /* Reserved fields for the Email Message form */ #define AR_RESERV_EMAIL_MSG_CNTNT_ATTCHMNT_ENCODING 18065L #define AR_RESERV_EMAIL_MSG_VALUES_ATTCHMNT_ENCODING 18066L #define AR_RESERV_EMAIL_MSG_MSG_ID 18082L #define AR_RESERV_EMAIL_MSG_DATE_SENT 18083L #define AR_RESERV_EMAIL_MSG_DATE_RECEIVED 18084L #define AR_RESERV_EMAIL_MSG_TO 18085L #define AR_RESERV_EMAIL_MSG_FROM 18086L #define AR_RESERV_EMAIL_MSG_REPLY_TO 18087L #define AR_RESERV_EMAIL_MSG_CC 18088L #define AR_RESERV_EMAIL_MSG_BCC 18089L #define AR_RESERV_EMAIL_MSG_SUBJECT 18090L #define AR_RESERV_EMAIL_MSG_MSG_BODY 18091L #define AR_RESERV_EMAIL_MSG_MSG_TYPE 18092L #define AR_RESERV_EMAIL_MSG_MAILBOX_ID 18093L /* reused */ #define AR_RESERV_EMAIL_MSG_ARSYS_SVR 18094L #define AR_RESERV_EMAIL_MSG_ATTCHMNT_POOL 18095L #define AR_RESERV_EMAIL_MSG_PRIORITY 18096L #define AR_RESERV_EMAIL_MSG_SENT_AT 18097L #define AR_RESERV_EMAIL_MSG_PARSE_MSG 18098L #define AR_RESERV_EMAIL_MSG_SEND_MSG 18099L /* reused */ #define AR_RESERV_EMAIL_MSG_EMAIL 18100L #define AR_RESERV_EMAIL_MSG_ARSYS_FORM 18101L #define AR_RESERV_EMAIL_MSG_CONTENT_TMP 18102L #define AR_RESERV_EMAIL_MSG_ORGANIZATION 18103L #define AR_RESERV_EMAIL_MSG_CONTENT 18104L #define AR_RESERV_EMAIL_MSG_FIELD_VALUE 18106L #define AR_RESERV_EMAIL_MSG_VALUES 18107L #define AR_RESERV_EMAIL_MSG_HEADER_TMP_ID 18108L #define AR_RESERV_EMAIL_MSG_FOOTER_TEMPLATE 18109L #define AR_RESERV_EMAIL_MSG_QUALIFICATION 18110L #define AR_RESERV_EMAIL_MSG_ARSYS_TCP_PORT 18111L #define AR_RESERV_EMAIL_MSG_ARSYS_RPC 18112L #define AR_RESERV_EMAIL_MSG_FORM_ID 19006L /* 30014L */ #define AR_RESERV_EMAIL_MSG_LOG_MSG_TXT AR_RESERV_EMAIL_ERR_LOG_MSG_TXT /* 18022L */ #define AR_RESERV_EMAIL_MSG_HDR_TMP_NAME 18135L #define AR_RESERV_EMAIL_MSG_CNTNT_TMP_NAME 18136L #define AR_RESERV_EMAIL_MSG_FTR_TMP_NAME 18137L #define AR_RESERV_EMAIL_MSG_MAILBOX_NAME 18139L /* reused */ #define AR_RESERV_EMAIL_MSG_HTML_CNTNT 18140L #define AR_RESERV_EMAIL_MSG_HTML_CNTNT_ATTCHMNT_ENCODE 18141L #define AR_RESERV_EMAIL_MSG_REPLY 18149L #define AR_RESERV_EMAIL_MSG_SEND_EMAIL 18150L #define AR_RESERV_EMAIL_MSG_SAVE AR_RESERV_EMAIL_ATTCH_SAVE /* 18151L */ #define AR_RESERV_EMAIL_MSG_ATTCH_TBL_FLD 18152L /* reused */ #define AR_RESERV_EMAIL_MSG_ATTCH_ID_CLMN 18153L /* reused */ #define AR_RESERV_EMAIL_MSG_ATTCH_NAME_CLMN 18154L /* reused */ #define AR_RESERV_EMAIL_MSG_ATTCH_TYPE_CLMN 18155L /* reused */ #define AR_RESERV_EMAIL_MSG_ERR_TABLE 18157L #define AR_RESERV_EMAIL_MSG_CLMN3 18158L #define AR_RESERV_EMAIL_MSG_CLMN7 18159L #define AR_RESERV_EMAIL_MSG_CLMN8 18160L #define AR_RESERV_EMAIL_MSG_LOG_MSG_ID 18161L #define AR_RESERV_EMAIL_MSG_MSG_PG_HLDR 18162L #define AR_RESERV_EMAIL_MSG_MSG_TAB 18163L #define AR_RESERV_EMAIL_MSG_ATTCH_TAB 18164L #define AR_RESERV_EMAIL_MSG_ADVANCE_OPT_TAB 18165L #define AR_RESERV_EMAIL_MSG_MSG_INFO_TAB 18166L #define AR_RESERV_EMAIL_MSG_ERROR_TAB 18167L #define AR_RESERV_EMAIL_MSG_CRM_SUPPORT 18168L #define AR_RESERV_EMAIL_MSG_BODY_PG_HLDR 18169L #define AR_RESERV_EMAIL_MSG_HTML_BODY_PG 18170L #define AR_RESERV_EMAIL_MSG_ADD_ATTCH 18171L /* reused */ #define AR_RESERV_EMAIL_MSG_MOD_ATTCH 18172L /* reused */ #define AR_RESERV_EMAIL_MSG_DEL_ATTCH 18173L /* reused */ #define AR_RESERV_EMAIL_MSG_EXISTING_ATTCH 18174L /* reused */ #define AR_RESERV_EMAIL_MSG_EXISTING_ATTCH_ID 18175L /* reused */ #define AR_RESERV_EMAIL_MSG_ADD_EXISTING 18176L /* reused */ #define AR_RESERV_EMAIL_MSG_REFRESH_TBL 18177L /* reused */ #define AR_RESERV_EMAIL_MSG_PG_HLDR2 18178L #define AR_RESERV_EMAIL_MSG_TMP_TAB 18179L #define AR_RESERV_EMAIL_MSG_VAR_REPLACE_TAB 18180L #define AR_RESERV_EMAIL_MSG_ATTCH_ALTERNATIVE 18181L #define AR_RESERV_EMAIL_MSG_PLAIN_TXT_BODY_PG 18191L #define AR_RESERV_EMAIL_MSG_FORM_HDR_LABEL AR_RESERV_EMAIL_ASSOC_FORM_HDR_LABEL /* 18193L */ #define AR_RESERV_EMAIL_MSG_SUB_HDR_LABEL 18224L #define AR_RESERV_EMAIL_MSG_RTF_CONTENT 18209L #define AR_RESERV_EMAIL_MSG_HIDDEN_PG_HLDR AR_RESERV_EMAIL_ASSOC_HIDDEN_PG_HLDR /* 18210L */ #define AR_RESERV_EMAIL_MSG_ATTACHMENT_GUID_COLUMN 18212L #define AR_RESERV_EMAIL_MSG_RTF_CONTENT_ENCODE 18215L #define AR_RESERV_EMAIL_MSG_INCOMING_MAILBOX_ID 18220L #define AR_RESERV_EMAIL_MSG_HTML_BODY 18290L #define AR_RESERV_EMAIL_MSG_CRM_READ_STAT 18291L #define AR_RESERV_EMAIL_MSG_CRM_MAX_RETRIES 18292L #define AR_RESERV_EMAIL_MSG_CRM_RETRY_COUNT 18293L #define AR_RESERV_EMAIL_MSG_CRM_SMTP_SVR_RET_CODE 18294L #define AR_RESERV_EMAIL_MSG_CRM_LAST_LOG_ENTRY 18295L #define AR_RESERV_EMAIL_MSG_CRM_EMAIL_LOG 18296L #define AR_RESERV_EMAIL_MSG_ATTCH 18297L #define AR_RESERV_EMAIL_MSG_CRM_SUBMITTED_FORM 18298L /* reused */ #define AR_RESERV_EMAIL_MSG_IN_REPLY_TO 18299L #define AR_RESERV_EMAIL_MSG_DISPLAY_ADVANCED_OPT 18304L #define AR_RESERV_EMAIL_MSG_COLUMN 18235L #define AR_RESERV_EMAIL_MSG_COLUMN2 18236L #define AR_RESERV_EMAIL_MSG_COLUMN4 18237L -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 9/17/07, Susan Palmer <[EMAIL PROTECTED]> wrote: > ** > Hi all, > > Since our system is more crm than helpdesk and we're implementing the v7 > Email system I want to be able to relate all email messages we send to our > customers to their Site records. We want to be able to view them whether > we're on their Sire record, Change, Task or HD records. Sounds pretty > straight forward. > > Well originally I thought I could just use the AR System Email Messages form > and I created the additional fields I needed on the form. I couldn't get > the workflow to write to the record. So then I thought it would be better > to save that form with our own naming convention so I could delete the > records from the original form keeping performance levels good. > > But I cannot do a Save As Form on that form. I get an error 55 (The listed > item was not successfully imported .... associated messages ... but there > isn't any so I don't know what the issue is.) > > I don't see any indication of what the problem is in either the api or sql > logs. > > I know I could make the form from scratch and create the fields but I'm > wondering what the issue is with the Save As. Anyone else come across this? > > Thanks for your help, > Susan > > ARS v701P2 > Oracle 10g > Windows 2003 > Admin ARs v701P3 > Windows XP > > __20060125_______________________This posting was > submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
