Does anyone have any interest in voting for something that allows us to control what fields get copied by default when copying a record? For example, copying a quote, order, po, job, etc. What if we had control over what fields got copied and which defaulted to standard behavior. For example, sales person on quotes. Copying a quote brings them over, but if you changed salespeople since the quote was created, you’d want it to default to source the salesperson from master…
In short, make something for us to control how copying works. I think most people probably have BPMS or data directives to intervene right now yeah?
Yeah I don’t know. Maybe just make an include/exclude control with all the different fields on there from each master record. So exclude would mean, revert to default business logic and include would mean, copy over from previous quote… Maybe it would get twisted though and you’d be breaking business logic itself by including some and excluding others…
What if they exposed the copy process as a business object method, instead of something internally ?
They could have a default behavior, but it would allow us to intervene.
I haven’t looked in a minute, but I’m pretty sure there are already some methods you can hook onto… my point being though is that this idea would take care of having to code default BO behavior for each field that you want to intervene on
On one hand yes, but on the other hand no - most of the objects have 100+ fields. I think it would make the copying process super heavyweight if they had to go analyze which fields to copy based on another data source. This is the kind of thing that is so easy to control with a bpm it would be hard for me to vote for it, compared to other stuff that I need them to fix because its not possible to just throw in a bpm to do what I want.
Understandable. Ideas aren’t meant to “fix” bugs right?
Something about the way you put this makes it feel like ideas are “fixing” functionality:
I guess what I am saying is, why make everyone make the same BPMs. Maybe make it a part of the standard product and make sure that it’s not heavyweight and works well.
Ideas is the only conduit to request fixes for design flaws. Imo there are a multitude of things epicor will not accept as a bug for the simple fact that somebody designed it wrong. Doesn’t mean its not a bug.
That’s true. What about being able to create a template record, like a template part, or template customer, etc. And then when you create a new record you can elect to use the template. That way its not some new configuration screen where you have to know all the fields to set,
One of my recent requests was to ensure that when a user copied a quote it would copy line quantities and discounts, however i have had other customers who want to just copy the core details.
There are so many options/fields available that i think it would make “copy” form too confusing for a user if they were presented with “all” fields available.
If you want to see how i have “targeted” fields to copy, happy to share the BPM
Also, the idea would be that you set this at a company level or maybe a customer level as an administrator to avoid having your users select it every time they copy a quote. Does that make sense?
In other words, you set it once at a company level or customer level or whatever levels we all come up with and then your user doesn’t have to select it each time.
Happy to send over to you but the lowest version that i have is 10.2.700 and i see that you are on 10.2.500 - let me know if you want me to post a “how to” on this
