For what it's worth, I'd approach the BPM a little different. Instead of
doing a check when people are retrieving a record, then figuring out how to
change it, why not just do a BAQ up front that shows all the offending
customer names, then fix your existing data once and for all. Then, you
only need to put in a BPM that edits whenever someone adds a new customer or
changes the name of an existing customer. It's a much easier BPM to
create, and won't have nearly the impact on performance that checks
everytime someone retrieves a customer record.
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Vic Drecchio
Sent: Thursday, June 28, 2012 10:25 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] BPM Primer help (8.03.409C)
Calvin,
http://tech.groups.yahoo.com/group/vantage/files/BPMs/
There's a great PowerPoint Presentation in there by Rob Bucek. He put
together a nice little tutorial.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
c.krusen1
Sent: Thursday, June 28, 2012 8:23 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] BPM Primer help (8.03.409C)
Can anyone point me to some decent literature on implementing a BPM.
My first BPM project would be one that checks the Customer.Name field to see
if it has an '&' in it, if so, change it to 'and'. Ex: 'AT&T' would be
changed to 'AT and T'. This is needed as the Avalara TaxConnect can't have
an '&' in the customer's name .
I'd implement the BPM to make the change when ever a Customer record is
retrieved. I'd want it to change the Name field in the Customer table, not
just the name fetched from the Customer table.
Thanks in advance.
Calvin
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2437/5098 - Release Date: 06/28/12
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2437/5098 - Release Date: 06/28/12
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
doing a check when people are retrieving a record, then figuring out how to
change it, why not just do a BAQ up front that shows all the offending
customer names, then fix your existing data once and for all. Then, you
only need to put in a BPM that edits whenever someone adds a new customer or
changes the name of an existing customer. It's a much easier BPM to
create, and won't have nearly the impact on performance that checks
everytime someone retrieves a customer record.
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Vic Drecchio
Sent: Thursday, June 28, 2012 10:25 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] BPM Primer help (8.03.409C)
Calvin,
http://tech.groups.yahoo.com/group/vantage/files/BPMs/
There's a great PowerPoint Presentation in there by Rob Bucek. He put
together a nice little tutorial.
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
c.krusen1
Sent: Thursday, June 28, 2012 8:23 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] BPM Primer help (8.03.409C)
Can anyone point me to some decent literature on implementing a BPM.
My first BPM project would be one that checks the Customer.Name field to see
if it has an '&' in it, if so, change it to 'and'. Ex: 'AT&T' would be
changed to 'AT and T'. This is needed as the Avalara TaxConnect can't have
an '&' in the customer's name .
I'd implement the BPM to make the change when ever a Customer record is
retrieved. I'd want it to change the Name field in the Customer table, not
just the name fetched from the Customer table.
Thanks in advance.
Calvin
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2437/5098 - Release Date: 06/28/12
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2180 / Virus Database: 2437/5098 - Release Date: 06/28/12
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]