Ah, hadn’t thought of that. Makes sense as to a reason why the change.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On Behalf Of Tom J. Christie
Sent: Thursday, September 12, 2013 11:44 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Different between MasterUpdate and Update
I remember a discussion about this at a session at Insights in 2012. My memory is fading, but if I recall correctly, they said it was introduced to increase transactional speed. Running a large number of separate BO calls to
the server is slower than sending one.
Epicor has been receiving complaints forever regarding speed issues, particularly in SO, so the goal seems quite likely. How much it helps and such is something I don't really know.
I have found it more difficult though for BPM purposes, particularly as it hasn't been implemented in a very consistent manner. Par for the course though.
Tom Christie | Information Technology Manager | AGM Container Controls, Inc.<http://www.agmcontainer.com/> |
tchristie@...<mailto:tchristie@...> | t: 520.881.2130 ext 2176
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Joe Englert
Sent: Thursday, September 12, 2013 7:36 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Different between MasterUpdate and Update
There are many parameters and a super wide dataset because it's lumping everything into one call. My point is that, why would they replace an interface update call with UpdateMaster - which you can see in a trace (if multiple rows is the primary driver) when
you can't edit multiple rows? I think they thought it would be easier for us if everything was consolidated into one call. I don't think they thought it through and I hope they've abandoned it after 607A.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Jose Gomez
Sent: Thursday, September 12, 2013 10:29 AM
To: Vantage
Subject: Re: [Vantage] Different between MasterUpdate and Update
I am blurry on some of the details in terms of the Business Logic it does take a LOT more parameters and returns a lot more info. So there's that... In terms of the multiple dirty rows I've done it with the BO not sure about the UI. This info came from hall
way meeting at insights 2 years ago with one of the engineers... So take it as you will.
Jose C Gomez
Software Engineer
T: 904.469.1524 mobile
E: jose@...<mailto:jose@...>
http://www.josecgomez.com
[Description: Image removed by sender.]<http://www.linkedin.com/in/josecgomez> [Description: Image removed by sender.] <http://www.facebook.com/josegomez> [Description:
Image removed by sender.] <http://www.google.com/profiles/jose.gomez> [Description: Image removed by sender.] <http://www.twitter.com/joc85> [Description: Image
removed by sender.] <http://www.josecgomez.com/professional-resume/> [Description: Image removed by sender.] <http://www.josecgomez.com/feed/> [Description:
Image removed by sender.] <http://www.usdoingstuff.com/>
Quis custodiet ipsos custodes?
On Thu, Sep 12, 2013 at 10:26 AM, Joe Englert <englertj@...<mailto:englertj@...>> wrote:
Since the interface only allows for editing one SO at a time, how could there be a need for updating multiple rows? Can you tell me what you mean by a bit more checking of Business Logic? In my experience (not specifically SO, would have to look) it's a craps shoot as to whether Update will actually trigger method directives when UpdateMaster is used. I thought it was just a wrapper method.
From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>] On Behalf Of Jose Gomez
Sent: Thursday, September 12, 2013 10:12 AM
To: Vantage
Subject: Re: [Vantage] Different between MasterUpdate and Update
Per what Epicor told me a long time ago, master update allows for multiple dirty rows and does a bit more checking of Business Logic. (Specifically in SO Entry) however In my experience it does call the Update Method.
Jose C Gomez
Software Engineer
T: 904.469.1524<tel:904.469.1524> mobile
E: jose@...<mailto:jose@...>
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez>
Quis custodiet ipsos custodes?<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
On Thu, Sep 12, 2013 at 10:08 AM, Joe Englert <englertj@...> wrote:<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
At some point starting between 602 and 607A, they started rolling various methods that happened during update time into one method called UpdateMaster that included the other bo calls. It was a big deal to us during our conversion because suddenly, related methods were no longer being triggered (on some screens). Trace logs became less useful because we didn't have visibility into all that was being triggered during an update. It's hit and miss with our version on which screens use UpdateMaster or the standard update. Also hit and miss whether or not bo methods are hidden from the trace log when UpdateMaster did replace Update. It's also called MasterUpdate on some screens. Also hit and miss whether or not the component events will fire whether or not they appear in the trace logs.<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
I would experiment with a message box on both methods to see if both fire or only the master.<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of lisa.saren@...
Sent: Thursday, September 12, 2013 10:01 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Different between MasterUpdate and Update<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
Hi everybody,<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
Whats the difference between the MasterUpdate and Update when creating a BPM in for example the SalesOrder BO?
Kind regards,<http://www.linkedin.com/in/josecgomez>
Lisa<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
<http://www.linkedin.com/in/josecgomez>
[Non-text portions of this message have been removed]
