Not really a thought but an option if you haven’t tried it already. You can attempt to add the attachment to the pool itself and let the server find the first available attachment field. According to the help for the run process, it should work.
Scott Illari 908-601-8948 <http://www.linkedin.com/in/scottillari> http://www.linkedin.com/in/scottillari From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Frex Popo Sent: Wednesday, February 04, 2009 10:36 AM To: arslist@ARSLIST.ORG Subject: Re: ARERR [310] Value has wrong data type for the field ** Not a silly question :) the field is in fact an attachment field and not the attachment pool. --- En date de : Mer 4.2.09, LJ Longwing <lj.longw...@gmail.com> a écrit : De: LJ Longwing <lj.longw...@gmail.com> Objet: Re: ARERR [310] Value has wrong data type for the field À: arslist@ARSLIST.ORG Date: Mercredi 4 Février 2009, 16h26 ** Silly question...is field 1000003962 an attachment field on that form? According to the docs, the field must be an attachment field, not a pool _____ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Frex Popo Sent: Wednesday, February 04, 2009 8:15 AM To: arslist@ARSLIST.ORG Subject: ARERR [310] Value has wrong data type for the field ** Dear all, ARSERVER 7.1.00 Patch 004 OS: WINDOWS SERVER 2003 DB was SQL Server 2005 Client 7.1.0 Patch004 I hope this is not another bug as I already came across two this week which I reported to BMC. I have a filter set a field, which adds an attachment to an attachment pool in the CTM:People form which fires on modify. The log shows that the filter executes a set action an fails with the error: ARERR [310] Value has wrong data type for the field Here an extract from the filter log: 0: Set Fields <FLTR> <TID: 0000001952> <RPC ID: 0000067665> <Queue: Fast > <Client-RPC: 390620 > <USER: Demo > PERFORM-ACTION-ADD-ATTACHMENT 1000003962 "C:\Photos\00109125J.jpg" <FLTR> <TID: 0000001952> <RPC ID: 0000067665> <Queue: Fast > <Client-RPC: 390620 > <USER: Demo > Exit code: 0 Value: 0 <FLTR> <TID: 0000001952> <RPC ID: 0000067665> <Queue: Fast > <Client-RPC: 390620 > <USER: Demo > Value has wrong data type for the field <FLTR> <TID: 0000001952> <RPC ID: 0000067665> <Queue: Fast > <Client-RPC: 390620 > <USER: Demo > **** Error while performing filter action: Error 310 Here is the client API log showing the ARSetEntry error: ARSetEntry results Return Code: ERROR Status List: 1 items Status Struct: Message type: ERROR Message number: 310 Message: Value has wrong data type for the field Appended: I tried this in another server installation on a SQL SERVER 2000 Databse and it works just fine. Any thoughts on this? Many thanks frex __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _____ Ne pleurez pas si votre Webmail ferme. Récupérez <http://fr.rd.yahoo.com/mail_fr/taglines/caramail/*http:/fr.docs.yahoo.com/mail/transfert_mails.html> votre historique sur Yahoo! Mail __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"