Some .408a upgrade notes

I guess it all depends on one's definition of support.




________________________________
From: Mark Wonsil <mark_wonsil@...>
To: vantage@yahoogroups.com
Sent: Wednesday, September 2, 2009 9:44:13 PM
Subject: RE: [Vantage] Re: Some .408a upgrade notes...

Â

> With all that said, I think they do need to fix anything and
> everything that was once working and was clearly broken in a
> subsequent upgrade, no matter how minor they may feel it is.

If they don't, they'll have to re-write that speech they gave a Perspectives
last year where they promised to support the older versions until you're
ready for Epicor 9.







[Non-text portions of this message have been removed]
If you are running a BAM using the flag change on Shiphead.invoiced it is
not working in 408 or 408A.

Steve


-----Original Message-----
From: Tom [mailto:tombosko@...]
Sent: August 11, 2009 11:20 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Some .408a upgrade notes...




This one was not good.

Several issues arose:

1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on
attachments and hit refresh, they reappear. But they only reappear for as
long as you have the customer open. (They are digging into that) Attachments
in other palces are fine

3) Didn't realize you must do the .408 release update before moving to
.408a. (thought I was told differently- my bad)

4) Configurator stopped working. Not bringing selections into the order.
This one is not good.(ticket open)

5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a
handful, of the 60+ BPMs, not to work after.

6) Report issues: After the upgrade any customized report paths were rest to
prior location instead of current defualt location. (most people don't mess
with this one- we have remote sites and thought moving them out there would
improve performance- it didn't)

7) Labor still not calculating correctly, was suppose to be fixed in the
release.(Still trying to get the right answer on what that should really be)

That is it for now but it is only day 2 of the post upgrade to .408a

Tom
Miner Enterprises







[Non-text portions of this message have been removed]
Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
Â
We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
Â
If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.

Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.



________________________________
From: Tom <tombosko@...>
To: vantage@yahoogroups.com
Sent: Tuesday, August 11, 2009 12:20:25 PM
Subject: [Vantage] Some .408a upgrade notes...

Â
This one was not good.

Several issues arose:

1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine

3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)

4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)

5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.

6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)

7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)

That is it for now but it is only day 2 of the post upgrade to .408a

Tom
Miner Enterprises







[Non-text portions of this message have been removed]
When you say that labor is not calculating correctly can you elaborate on this? We have an open call with the help desk about labor not calculating correctly and they claim that we are the first and only to report this. We upgraded to 408A about a week and a half ago from 408 and we did not have the issues we are seeing until after upgrading to 408A.

Robert Nupp

--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
> Â
> We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
> Â
> If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
>
> Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
>
>
>
> ________________________________
> From: Tom <tombosko@...>
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 12:20:25 PM
> Subject: [Vantage] Some .408a upgrade notes...
>
> Â
> This one was not good.
>
> Several issues arose:
>
> 1) Paypal flow link changed site and no one told us of the link change.
> 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
>
> 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
>
> 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
>
> 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
>
> 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
>
> 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
>
> That is it for now but it is only day 2 of the post upgrade to .408a
>
> Tom
> Miner Enterprises
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
The configurator is completely broken for us on both 408 and 408a. In 408 we were not able to open a configuration at all, either to modify it or to configure a part from the sales order. We create a new part number for every configuration. In 408a it say the part number already exist and will not let us create the part number.

Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
----- Original Message -----
From: Steven Gotschall
To: vantage@yahoogroups.com
Sent: Tuesday, August 11, 2009 11:57 AM
Subject: Re: [Vantage] Some .408a upgrade notes...


Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.

We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.

If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.

Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.

________________________________
From: Tom <tombosko@...>
To: vantage@yahoogroups.com
Sent: Tuesday, August 11, 2009 12:20:25 PM
Subject: [Vantage] Some .408a upgrade notes...


This one was not good.

Several issues arose:

1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine

3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)

4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)

5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.

6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)

7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)

That is it for now but it is only day 2 of the post upgrade to .408a

Tom
Miner Enterprises

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
408 broke the configurator for us also, but we got a one off patch to fix it. We are not seeing the problem you described in 408A. It does tell us that the part already exists (it always did tell us that if the part already existed in the part master), but either way it creates the part and puts it in the order.

One problem that 408 caused us that was never fixed was that Epicor decided on their own (and not tell anyone) to change the way the method is pulled in on a configured part. If a method for a configured part exists in the part master, then it defaults to that method when the method is pulled and not to the pre 408 way of doing things by pulling it from the configurator. Because of some of the limitations the configurator has on creating methods in the part master, our methods in the part master table was not an exact duplicate of what is created by the configurator itself. This caused us to scramble to make a lot of changes to get around this arbitrary decision on Epicor's part.

I had a very long conference call with a bunch of people at Epicor about this and they agreed to modify the configurator so that you could choose the default behavoir on how methods were pulled into jobs and quotes. I haven't heard a word from them since.



________________________________
From: Charles Carden <shadowcar1449@...>
To: vantage@yahoogroups.com
Sent: Tuesday, August 11, 2009 3:56:25 PM
Subject: Re: [Vantage] Some .408a upgrade notes...

Â
The configurator is completely broken for us on both 408 and 408a. In 408 we were not able to open a configuration at all, either to modify it or to configure a part from the sales order. We create a new part number for every configuration. In 408a it say the part number already exist and will not let us create the part number.

Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
----- Original Message -----
From: Steven Gotschall
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 11:57 AM
Subject: Re: [Vantage] Some .408a upgrade notes...

Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.

We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.

If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.

Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.

____________ _________ _________ __
From: Tom <tombosko@ameritech. net>
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 12:20:25 PM
Subject: [Vantage] Some .408a upgrade notes...

This one was not good.

Several issues arose:

1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine

3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)

4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)

5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.

6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)

7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)

That is it for now but it is only day 2 of the post upgrade to .408a

Tom
Miner Enterprises

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
Perhaps just in time for some, Epicor appears to have just released patch
8.03.408b!



https://epicweb.epicor.com/Support/VantageVista/Downloads/Vantage%20803400/P
atchGuide_ChangeList_803408B.pdf.aspx



Specifically, includes fixes for SCR's #63823 and #64186 related to Product
Configurator.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Steven Gotschall
Sent: Tuesday, August 11, 2009 4:39 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Some .408a upgrade notes...



408 broke the configurator for us also, but we got a one off patch to fix
it. We are not seeing the problem you described in 408A. It does tell us
that the part already exists (it always did tell us that if the part already
existed in the part master), but either way it creates the part and puts it
in the order.

One problem that 408 caused us that was never fixed was that Epicor decided
on their own (and not tell anyone) to change the way the method is pulled in
on a configured part. If a method for a configured part exists in the part
master, then it defaults to that method when the method is pulled and not to
the pre 408 way of doing things by pulling it from the configurator.
Because of some of the limitations the configurator has on creating methods
in the part master, our methods in the part master table was not an exact
duplicate of what is created by the configurator itself. This caused us to
scramble to make a lot of changes to get around this arbitrary decision on
Epicor's part.

I had a very long conference call with a bunch of people at Epicor about
this and they agreed to modify the configurator so that you could choose the
default behavoir on how methods were pulled into jobs and quotes. I haven't
heard a word from them since.

________________________________
From: Charles Carden <shadowcar1449@ <mailto:shadowcar1449%40sbcglobal.net>
sbcglobal.net>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, August 11, 2009 3:56:25 PM
Subject: Re: [Vantage] Some .408a upgrade notes...

The configurator is completely broken for us on both 408 and 408a. In 408 we
were not able to open a configuration at all, either to modify it or to
configure a part from the sales order. We create a new part number for every
configuration. In 408a it say the part number already exist and will not let
us create the part number.

Charles Carden
IT Manager
Manitex, Inc.
Georgetown, Texas
----- Original Message -----
From: Steven Gotschall
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 11:57 AM
Subject: Re: [Vantage] Some .408a upgrade notes...

Could you explain number 4 a little more? We haven't seen any problems with
the configurator on 408A.

We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As
far as number 4 goes, there is a warning when you install 408A that you need
to be on 408 first.

If you get an answer on number 2, could you please post it for all of us to
see? I beleive this was a problem in 408 also.

Number 1 really ticked us off. Even after we called Epicor, they didn't have
an answer for us. Our CFO found the answer on the PayPal site.

____________ _________ _________ __
From: Tom <tombosko@ameritech. net>
To: vantage@yahoogroups .com
Sent: Tuesday, August 11, 2009 12:20:25 PM
Subject: [Vantage] Some .408a upgrade notes...

This one was not good.

Several issues arose:

1) Paypal flow link changed site and no one told us of the link change.
2) In customer, all linked documents are gone..but if you click on
attachments and hit refresh, they reappear. But they only reappear for as
long as you have the customer open. (They are digging into that) Attachments
in other palces are fine

3) Didn't realize you must do the .408 release update before moving to
.408a. (thought I was told differently- my bad)

4) Configurator stopped working. Not bringing selections into the order.
This one is not good.(ticket open)

5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a
handful, of the 60+ BPMs, not to work after.

6) Report issues: After the upgrade any customized report paths were rest to
prior location instead of current defualt location. (most people don't mess
with this one- we have remote sites and thought moving them out there would
improve performance- it didn't)

7) Labor still not calculating correctly, was suppose to be fixed in the
release.(Still trying to get the right answer on what that should really be)

That is it for now but it is only day 2 of the post upgrade to .408a

Tom
Miner Enterprises





[Non-text portions of this message have been removed]
Sorry, folks, the fixes I previously referenced were included in .408a, not
408b



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
sysadmin@...
Sent: Tuesday, August 11, 2009 5:22 PM
To: vantage@yahoogroups.com
Subject: [Vantage] 8.03.408b patch



Perhaps just in time for some, Epicor appears to have just released patch
8.03.408b!

https://epicweb.
<https://epicweb.epicor.com/Support/VantageVista/Downloads/Vantage%20803400/
P> epicor.com/Support/VantageVista/Downloads/Vantage%20803400/P
atchGuide_ChangeList_803408B.pdf.aspx

Specifically, includes fixes for SCR's #63823 and #64186 related to Product
Configurator.






[Non-text portions of this message have been removed]
--- In vantage@yahoogroups.com, "Charles Carden" <shadowcar1449@...> wrote:
>
> The configurator is completely broken for us on both 408 and 408a. In 408 we were not able to open a configuration at all, either to modify it or to configure a part from the sales order. We create a new part number for every configuration. In 408a it say the part number already exist and will not let us create the part number.
>
> Charles Carden
> IT Manager
> Manitex, Inc.
> Georgetown, Texas
> ----- Original Message -----
> From: Steven Gotschall
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 11:57 AM
> Subject: Re: [Vantage] Some .408a upgrade notes...
>
>
> Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
>
> We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
>
> If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
>
> Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
>
> ________________________________
> From: Tom <tombosko@...>
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 12:20:25 PM
> Subject: [Vantage] Some .408a upgrade notes...
>
>
> This one was not good.
>
> Several issues arose:
>
> 1) Paypal flow link changed site and no one told us of the link change.
> 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
>
> 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
>
> 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
>
> 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
>
> 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
>
> 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
>
> That is it for now but it is only day 2 of the post upgrade to .408a
>
> Tom
> Miner Enterprises
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Charles,

We got a "one off" from Epicor. The ref for the one of is Epicor SCR: 64714. Hope that helps

Also had to run a 5905 conversion. It is thought the combo of those two items fixed the issue.

It is now working!

On to the next one!

Tom Bosko
Miner Enterprises
--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
> Â
> We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
> Â
> If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
>
> Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
>
>
>
> ________________________________
> From: Tom <tombosko@...>
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 12:20:25 PM
> Subject: [Vantage] Some .408a upgrade notes...
>
> Â
> This one was not good.
>
> Several issues arose:
>
> 1) Paypal flow link changed site and no one told us of the link change.
> 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
>
> 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
>
> 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
>
> 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
>
> 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
>
> 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
>
> That is it for now but it is only day 2 of the post upgrade to .408a
>
> Tom
> Miner Enterprises
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

From what the Engineers tell me it is not applying the rules once the selection is made and saved.

Oddly enough starting a new configured part worked..not existing parts. So I think the "one off" addressed that.

Got a fix and ran the 5905 conversion program. The fix was 64714
--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
> Â
> We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
> Â
> If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
>
> Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
>
>
>
> ________________________________
> From: Tom <tombosko@...>
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 12:20:25 PM
> Subject: [Vantage] Some .408a upgrade notes...
>
> Â
> This one was not good.
>
> Several issues arose:
>
> 1) Paypal flow link changed site and no one told us of the link change.
> 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
>
> 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
>
> 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
>
> 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
>
> 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
>
> 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
>
> That is it for now but it is only day 2 of the post upgrade to .408a
>
> Tom
> Miner Enterprises
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

From what the Engineers tell me it is not applying the rules once the selection is made and saved.

Oddly enough starting a new configured part worked..not existing parts. So I think the "one off" addressed that.

Got a fix and ran the 5905 conversion program. The fix was 64714
--- In vantage@yahoogroups.com, "robert.nupp" <robert.nupp@...> wrote:
>
>
> When you say that labor is not calculating correctly can you elaborate on this? We have an open call with the help desk about labor not calculating correctly and they claim that we are the first and only to report this. We upgraded to 408A about a week and a half ago from 408 and we did not have the issues we are seeing until after upgrading to 408A.
>
> Robert Nupp
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> >
> > Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
> > Â
> > We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
> > Â
> > If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
> >
> > Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
> >
> >
> >
> > ________________________________
> > From: Tom <tombosko@>
> > To: vantage@yahoogroups.com
> > Sent: Tuesday, August 11, 2009 12:20:25 PM
> > Subject: [Vantage] Some .408a upgrade notes...
> >
> > Â
> > This one was not good.
> >
> > Several issues arose:
> >
> > 1) Paypal flow link changed site and no one told us of the link change.
> > 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
> >
> > 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
> >
> > 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
> >
> > 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
> >
> > 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
> >
> > 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
> >
> > That is it for now but it is only day 2 of the post upgrade to .408a
> >
> > Tom
> > Miner Enterprises
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

My partner who handles that level of detail says it is not calculating burden correctly. This was suppose to be fixed in the .408 release..
Charles,

Are you still experiencing problems with your configurator? We are holding off moving from 8.03.407C to 8.03.408B because of Configurator problems. Configurators are essential for our operation. Do you believe Epicor has fixed their Configurator with the 8.03.408B update?

Thanks,
Dave
Xybix
8.03.407C P

--- In vantage@yahoogroups.com, "Charles Carden" <shadowcar1449@...> wrote:
>
> The configurator is completely broken for us on both 408 and 408a. In 408 we were not able to open a configuration at all, either to modify it or to configure a part from the sales order. We create a new part number for every configuration. In 408a it say the part number already exist and will not let us create the part number.
>
> Charles Carden
> IT Manager
> Manitex, Inc.
> Georgetown, Texas
> ----- Original Message -----
> From: Steven Gotschall
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 11:57 AM
> Subject: Re: [Vantage] Some .408a upgrade notes...
>
>
> Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
>
> We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
>
> If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
>
> Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
>
> ________________________________
> From: Tom <tombosko@...>
> To: vantage@yahoogroups.com
> Sent: Tuesday, August 11, 2009 12:20:25 PM
> Subject: [Vantage] Some .408a upgrade notes...
>
>
> This one was not good.
>
> Several issues arose:
>
> 1) Paypal flow link changed site and no one told us of the link change.
> 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
>
> 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
>
> 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
>
> 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
>
> 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
>
> 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
>
> That is it for now but it is only day 2 of the post upgrade to .408a
>
> Tom
> Miner Enterprises
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
They did a "one off" SCR and had us run the 5905 conversion program. Between those two items it fixed the issues. Odd thing about this issue is if you created a new part for the configurator, worked fine. I guess no one QA'd existing configured parts.

The attachments disappearing I am not happy with their answer. They say it will be fixed on 9.04.x. We are on 8.03.408b and they don't have plans to fix it, not acceptable. I had the functionality and it was working prior to .408.

Tom

--- In vantage@yahoogroups.com, "ofcwiz" <DavidH@...> wrote:
>
> Charles,
>
> Are you still experiencing problems with your configurator? We are holding off moving from 8.03.407C to 8.03.408B because of Configurator problems. Configurators are essential for our operation. Do you believe Epicor has fixed their Configurator with the 8.03.408B update?
>
> Thanks,
> Dave
> Xybix
> 8.03.407C P
>
> --- In vantage@yahoogroups.com, "Charles Carden" <shadowcar1449@> wrote:
> >
> > The configurator is completely broken for us on both 408 and 408a. In 408 we were not able to open a configuration at all, either to modify it or to configure a part from the sales order. We create a new part number for every configuration. In 408a it say the part number already exist and will not let us create the part number.
> >
> > Charles Carden
> > IT Manager
> > Manitex, Inc.
> > Georgetown, Texas
> > ----- Original Message -----
> > From: Steven Gotschall
> > To: vantage@yahoogroups.com
> > Sent: Tuesday, August 11, 2009 11:57 AM
> > Subject: Re: [Vantage] Some .408a upgrade notes...
> >
> >
> > Could you explain number 4 a little more? We haven't seen any problems with the configurator on 408A.
> >
> > We have seen numbers 1, 2, and 5 (BPMs break for us on every upgrade). As far as number 4 goes, there is a warning when you install 408A that you need to be on 408 first.
> >
> > If you get an answer on number 2, could you please post it for all of us to see? I beleive this was a problem in 408 also.
> >
> > Number 1 really ticked us off. Even after we called Epicor, they didn't have an answer for us. Our CFO found the answer on the PayPal site.
> >
> > ________________________________
> > From: Tom <tombosko@>
> > To: vantage@yahoogroups.com
> > Sent: Tuesday, August 11, 2009 12:20:25 PM
> > Subject: [Vantage] Some .408a upgrade notes...
> >
> >
> > This one was not good.
> >
> > Several issues arose:
> >
> > 1) Paypal flow link changed site and no one told us of the link change.
> > 2) In customer, all linked documents are gone..but if you click on attachments and hit refresh, they reappear. But they only reappear for as long as you have the customer open. (They are digging into that) Attachments in other palces are fine
> >
> > 3) Didn't realize you must do the .408 release update before moving to .408a. (thought I was told differently- my bad)
> >
> > 4) Configurator stopped working. Not bringing selections into the order. This one is not good.(ticket open)
> >
> > 5) Some BPMs "broke." We have a massive SC workflow and the upgrade caused a handful, of the 60+ BPMs, not to work after.
> >
> > 6) Report issues: After the upgrade any customized report paths were rest to prior location instead of current defualt location. (most people don't mess with this one- we have remote sites and thought moving them out there would improve performance- it didn't)
> >
> > 7) Labor still not calculating correctly, was suppose to be fixed in the release.(Still trying to get the right answer on what that should really be)
> >
> > That is it for now but it is only day 2 of the post upgrade to .408a
> >
> > Tom
> > Miner Enterprises
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
What I don't understand is why we are being " slightly forced" to go to ver 9.0. in other words epicor says they have no plans to fix bugs in vesion 8.03.xxx but they fixed it in version 9. I upgraded to 8.03 about 4 months ago and am still in process of getting things going and working around bugs. I agree with someone else who said that it is unacceptable to just "not" fix something. What the "excuse me" hell is all the support money for. There has to be some of that money allocated for this; right?

A Proud and loyal user of Vantage since 1999.

Thanx


-----
Stanley Machining's website has a new look.
Please visit us at: www.stanleymachining.com

[Non-text portions of this message have been removed]
I really don't want to defend Epicor, but I am surprised that they support so many old legacy products as they do. They haven't said they weren't going to fix problems in 8.03, matter of fact 409 is due out soon and they are currently working on 410. It is my impression that some of the "minor" problems in 8 will not be addressed as they move forward and more resorces are moved from 8 to version 9.

Now that I've washed the bad taste out of my mouth, let me do a little Epicor bashing. I think the reason they support old legacy products is because there are so few versions out there that are stable and have a minimal amount of problems. If Epicor could work out their development and testing problems and ensure that upgrades are at least that (an upgrade), then I would not have so many issues with upgrading my software and would not expect them to continue supporting old versions year after year.

With all that said, I think they do need to fix anything and everything that was once working and was clearly broken in a subsequent upgrade, no matter how minor they may feel it is.



________________________________
From: "Trzaska, Mark" <mtrzaska@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Wednesday, September 2, 2009 4:24:53 PM
Subject: [Vantage] Re: Some .408a upgrade notes...

Â
What I don't understand is why we are being " slightly forced" to go to ver 9.0. in other words epicor says they have no plans to fix bugs in vesion 8.03.xxx but they fixed it in version 9. I upgraded to 8.03 about 4 months ago and am still in process of getting things going and working around bugs. I agree with someone else who said that it is unacceptable to just "not" fix something. What the "excuse me" hell is all the support money for. There has to be some of that money allocated for this; right?

A Proud and loyal user of Vantage since 1999.

Thanx

-----
Stanley Machining's website has a new look.
Please visit us at: www.stanleymachinin g.com

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
I very slightly regret upgrading from 404b to 408b, since we modified 404b heavily to iron out some of the bugs and things that didnt make sense. The only reason we upgraded was because of the change in paypal. On the positive side, the number of bugs discovered in 408 so far has been a lot fewer than what has been discovered (by us internally anyway) in the past.

Thanks,
Kunal




________________________________
From: Steven Gotschall <sgotschall@...>
To: vantage@yahoogroups.com
Sent: Wednesday, September 2, 2009 3:05:46 PM
Subject: Re: [Vantage] Re: Some .408a upgrade notes...


I really don't want to defend Epicor, but I am surprised that they support so many old legacy products as they do. They haven't said they weren't going to fix problems in 8.03, matter of fact 409 is due out soon and they are currently working on 410. It is my impression that some of the "minor" problems in 8 will not be addressed as they move forward and more resorces are moved from 8 to version 9.

Now that I've washed the bad taste out of my mouth, let me do a little Epicor bashing. I think the reason they support old legacy products is because there are so few versions out there that are stable and have a minimal amount of problems. If Epicor could work out their development and testing problems and ensure that upgrades are at least that (an upgrade), then I would not have so many issues with upgrading my software and would not expect them to continue supporting old versions year after year.

With all that said, I think they do need to fix anything and everything that was once working and was clearly broken in a subsequent upgrade, no matter how minor they may feel it is.

____________ _________ _________ __
From: "Trzaska, Mark" <mtrzaska@stanleymac hining.com>
To: "vantage@yahoogroups .com" <vantage@yahoogroups .com>
Sent: Wednesday, September 2, 2009 4:24:53 PM
Subject: [Vantage] Re: Some .408a upgrade notes...


What I don't understand is why we are being " slightly forced" to go to ver 9.0. in other words epicor says they have no plans to fix bugs in vesion 8.03.xxx but they fixed it in version 9. I upgraded to 8.03 about 4 months ago and am still in process of getting things going and working around bugs. I agree with someone else who said that it is unacceptable to just "not" fix something. What the "excuse me" hell is all the support money for. There has to be some of that money allocated for this; right?

A Proud and loyal user of Vantage since 1999.

Thanx

-----
Stanley Machining's website has a new look.
Please visit us at: www.stanleymachinin g.com

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
> With all that said, I think they do need to fix anything and
> everything that was once working and was clearly broken in a
> subsequent upgrade, no matter how minor they may feel it is.

If they don't, they'll have to re-write that speech they gave a Perspectives
last year where they promised to support the older versions until you're
ready for Epicor 9.