What always worked for me, is to import with an additional zero to the end, like this: "123.95 USD 0". That's *a lot* simpler than using additional workflow. In this example, the 0 is the epoch value for the currency conversion date. If you are not using other currencies and the conversion functions in AR System (and I have yet to run into a client that does) then you will be just fine without it. -- Michiel Beijen Software Consultant +31 6 457 42 418 Bee Free IT + http://beefreeit.nl
On Jun 10, 2009 5:47 PM, "Rick Cook" <remedyr...@gmail.com> wrote: ** Kay, I noticed the same problem in 6.3. The workaround (I won't call it a fix) was this: 1) Create a character field in the form into which you are importing the data, or identify an existing one that isn't being used. 2) Create a Filter that fires on Merge that moves the data from the character field to the currency field. 3) Map your import to push the currency data to the character field. 4) When you are done, you can delete the character field (if you created one) and the Filter. Rick On Wed, Jun 10, 2009 at 8:39 AM, Fariss, Ron <ron_far...@aigvalic.com> wrote: > > ** > Kaye, > > Y... _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
