I have a BAM that sends Packing Slips to APM. I would like to write a rule that looks at the table emailaddress field and see if there is a value with a @.
I have tried:
fieldname operator Value
EmailAddress MATCHES @
EmailAddress MATCHES %@%
EmailAddress MATCHES *@*
Nothing is sent to APM with any of these values. What is a wildcard I can use?
Try the ASCII character? CHR(064)
Brenda
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 2:28 PM
To: EPICOR UG - EPICOR (vantage@yahoogroups.com)
Subject: [Vantage] BAM and Wildcards
I have a BAM that sends Packing Slips to APM. I would like to write a rule that looks at the table emailaddress field and see if there is a value with a @.
I have tried:
fieldname operator Value
EmailAddress MATCHES @
EmailAddress MATCHES %@%
EmailAddress MATCHES *@*
Nothing is sent to APM with any of these values. What is a wildcard I can use?
Thank you for your reply. That did not work.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 1:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RE: BAM and Wildcards
Try the ASCII character? CHR(064)
Brenda
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 2:28 PM
To: EPICOR UG - EPICOR (vantage@yahoogroups.com)
Subject: [Vantage] BAM and Wildcards
I have a BAM that sends Packing Slips to APM. I would like to write a rule that looks at the table emailaddress field and see if there is a value with a @.
I have tried:
fieldname operator Value
EmailAddress MATCHES @
EmailAddress MATCHES %@%
EmailAddress MATCHES *@*
Nothing is sent to APM with any of these values. What is a wildcard I can use?
I believe any characters in Value are automatically enclosed in quotes in the resulting phrase.
Maybe a workaround would be a BPM to keep a UD boolean field updated in the UserFiles when the @ character occurs.
Then you could check that UD field in your BAM?
Are we talking about the contact/person table? Is it possible that the email address would not have a valid email address? If yes, why?
That would preclude the email address check and you would not have to filter the email address. All you would need to know is if the data in the address existed or not.
Charlie Smith
CTCharlie@...
Cell: 860-919-1708
Office: 817-860-9862
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 1:28 PM
To: EPICOR UG - EPICOR (vantage@yahoogroups.com)
Subject: [Vantage] BAM and Wildcards
I have a BAM that sends Packing Slips to APM. I would like to write a rule that looks at the table emailaddress field and see if there is a value with a @.
I have tried:
fieldname operator Value
EmailAddress MATCHES @
EmailAddress MATCHES %@%
EmailAddress MATCHES *@*
Nothing is sent to APM with any of these values. What is a wildcard I can use?
Just for the heck of it I tested this again
This one worked for me in a BAM rule...
(UserFile) EmailAddress MATCHES *@*
E9.05.702A - Progress
I’ll try that again on Monday.
William R. King
IT Analyst
Topura America Fastener, Inc.
1070 Monterey Court - Bowling Green, KY 42101
Voice: 270-901-1579
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 4:19 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BAM and Wildcards
P.S.
Just for the heck of it I tested this again
This one worked for me in a BAM rule...
(UserFile) EmailAddress MATCHES *@*
E9.05.702A - Progress
Recently updated APM and tested again successfully with
the MATCHES *@*
Thanks for all the help.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Friday, April 24, 2015 10:31 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: BAM and Wildcards
I’ll try that again on Monday.
From:
vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, April 23, 2015 4:19 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BAM and Wildcards
P.S.
Just for the heck of it I tested this again
This one worked for me in a BAM rule...
(UserFile) EmailAddress MATCHES *@*
E9.05.702A - Progress