Bug List Blank Title 78551

Yahoo Archive
1
Well, it didn't show up as pretty as when I pasted it into my previous message. Sorry.

On a separate note, there is also a list that has recently been started on Vmug (Vantage/Vista Midwest User Group). You'll need to get a username and password to see it. http://www.vantageusers.org/

For other resources, I posted a list to the Epicor Vista Forum a while back... http://forums.epicor.com/forum_posts.asp?TID=1365&KW=resource&PID=3528#3528

Matt


--- In vantage@yahoogroups.com, "vistapdmmatt" <mh@...> wrote:
>
>
> There is a list maintained by Epicor. You'll need your EpicWeb login to
> view it. I'm not sure how useful the list really is, but it does allow
> you to search for bug and enhancement requests. I've not found it
> completely easy to search. Anyway, here it is...
> https://epicweb.epicor.com/ReportServer/Pages/ReportViewer.aspx?%2fePort\
> al%2fSearchCRs&rs%3aCommand=Render&rc%3aParameters=true&rc%3aToolbar=tru\
> e
> <https://epicweb.epicor.com/ReportServer/Pages/ReportViewer.aspx?%2fePor\
> tal%2fSearchCRs&rs%3aCommand=Render&rc%3aParameters=true&rc%3aToolbar=tr\
> ue>
>
> Lets see if I can paste a sample in here...OK...here is a list of all
> open High priority change requests for Vantage...wow, it shows items
> open since 2000. if you leave it as an oepne ended search over all
> versions.
>
> CR Number Description Version Priority Open Date
> Status 5117MPS "Shopwrn in use by XXX" (2624) then (2661) 1
> 03/14/2001 Open 3151ESC JM In Job Closing the Backflush box is not
> updating. 1 11/25/2008 Open 3140ESC JM Error 'Record not
> available' in Job Closing 1 11/24/2008 Open 3136MPS Unable to
> Print Crystal Forms receive errors 1 01/19/2000 Open 3132ESC
> Error 'Unexpected Error' when trying to save a quote. 1 11/21/2008
> Open 3566ESC PM Purchasing suggestions not generating any
> suggestions. 2 02/09/2009 Open 27229MPS IM Retrieved
> transactions disappear when cursor is moved to part field 2
> 01/09/2008 Open 27513MPS ENG Drag and drop allows you to add the
> parent part as a material to itself 2 02/21/2008 Open 24303MPS
> UserFile.ValidatePassword is not avaiable via BPM, why? 2 03/08/2007
> Open 90BRK OM - Mfg cancel suggestion should be created when ... 2
> 01/23/2001 Open 27224MPS JM Production detail report is not printing
> all sub assemblies 2 01/08/2008 Open 12081MPS DELETE ME 2
> 07/13/2004 Open 658SYD Supplier price list the currency is greyed
> out. 2 02/15/2008 Open 1156ESC OM Pricelist Import Process 2
> 12/21/2007 Open 3140MPS PO forms are missing fields (ABLE TO
> DUPLICATE) after loading .610 2 01/19/2000 Open 1157ESC OM Price
> List not functioning correctly 2 12/21/2007 Open 27139MPS PC PO
> tracker does not show the receipt attachments 2 12/26/2007 Open
> 3165ESC PM Two subcontract suggestions create only 1 PO line 2
> 11/26/2008 Open 23257MPS JM labor edit Icon report is displaying
> labor rates 2 12/21/2006 Open 3422ESC JM Unexpected error when
> saving the job. 2 01/16/2009 Open 28032MPS 5/1 REP Table
> relationships are omitted when a Report Data Def is Duplicated 2
> 05/02/2008 Open 4640MPS PC Rules not showing on test rules report
> (remove -q) 3 12/13/2000 Open 1383ESC SR "Charge ID references
> invalid value" when changing amount to MSC charge 3 02/07/2008 Open
> 4570MPS AR - aging performance in customer tracker 3 11/27/2000
> Open
>
>
> --- In vantage@yahoogroups.com, "Michael McWilliams" <mmcwilliams22@>
> wrote:
> >
> > I put in a call yesterday just wondering if epicor keeps a list of
> reported bugs at a current patch level. Here is the response:
> >
> > Hello Mike:
> > We really do not publish a "bug list."
> > The closest document to that would probably be the change list that
> > accompanies any service pack or patch. Attached is the install guide
> > and change list for the Vantage 803.407C patch. The change list at the
> > end is cumulative for all patches (A,B,C) at the .407 service pack
> > level.
> > I hope this answers your question.
> >
> >
> _______________________________________________________________________
> >
> > I really think this is something they should consider doing. Sure it
> helps to know what you fixed, but it also helps to know what other
> problems you will be facing. We are all calling and reporting our
> problems to them anyway, & they are recording the version we are on. It
> would save so much time having that extra info ahead of time instead of
> trying to figure out something does not work when another user has
> already reported it.
> > It should not be that difficult for them to do this, & I am sure they
> do internally so why not publish it.
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>
2
I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:

Hello Mike:
We really do not publish a "bug list."
The closest document to that would probably be the change list that
accompanies any service pack or patch. Attached is the install guide
and change list for the Vantage 803.407C patch. The change list at the
end is cumulative for all patches (A,B,C) at the .407 service pack
level.
I hope this answers your question.

_______________________________________________________________________

I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it.
It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.
3
Typical. They don't keep a list of the things that are broken, just the things they fixed. Unfortunately, this seems to be a growing trend with most companies. Say what you want about Microsoft, but at least they have a very comprehensive knowledge base of what is broken and how to work around it or what you need to do to fix it.


________________________________
From: Michael McWilliams <mmcwilliams22@...>
To: vantage@yahoogroups.com
Sent: Friday, May 29, 2009 3:57:00 PM
Subject: [Vantage] Bug List





I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:

Hello Mike:
We really do not publish a "bug list."
The closest document to that would probably be the change list that
accompanies any service pack or patch. Attached is the install guide
and change list for the Vantage 803.407C patch. The change list at the
end is cumulative for all patches (A,B,C) at the .407 service pack
level.
I hope this answers your question.

____________ _________ _________ _________ _________ _________ _

I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it..
It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.







[Non-text portions of this message have been removed]
4
My point exactly, how do they fix it if they don't have a list of what is broken.

--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> Typical. They don't keep a list of the things that are broken, just the things they fixed. Unfortunately, this seems to be a growing trend with most companies. Say what you want about Microsoft, but at least they have a very comprehensive knowledge base of what is broken and how to work around it or what you need to do to fix it.
>
>
> ________________________________
> From: Michael McWilliams <mmcwilliams22@...>
> To: vantage@yahoogroups.com
> Sent: Friday, May 29, 2009 3:57:00 PM
> Subject: [Vantage] Bug List
>
>
>
>
>
> I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:
>
> Hello Mike:
> We really do not publish a "bug list."
> The closest document to that would probably be the change list that
> accompanies any service pack or patch. Attached is the install guide
> and change list for the Vantage 803.407C patch. The change list at the
> end is cumulative for all patches (A,B,C) at the .407 service pack
> level.
> I hope this answers your question.
>
> ____________ _________ _________ _________ _________ _________ _
>
> I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it..
> It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
5
You can search the SCRs and sort by priority. Not a great solution but at least you can get the real big uh-ohs that have been found.

-Ramsey


--- In vantage@yahoogroups.com, "Michael McWilliams" <mmcwilliams22@...> wrote:
>
> My point exactly, how do they fix it if they don't have a list of what is broken.
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> >
> > Typical. They don't keep a list of the things that are broken, just the things they fixed. Unfortunately, this seems to be a growing trend with most companies. Say what you want about Microsoft, but at least they have a very comprehensive knowledge base of what is broken and how to work around it or what you need to do to fix it.
> >
> >
> > ________________________________
> > From: Michael McWilliams <mmcwilliams22@>
> > To: vantage@yahoogroups.com
> > Sent: Friday, May 29, 2009 3:57:00 PM
> > Subject: [Vantage] Bug List
> >
> >
> >
> >
> >
> > I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:
> >
> > Hello Mike:
> > We really do not publish a "bug list."
> > The closest document to that would probably be the change list that
> > accompanies any service pack or patch. Attached is the install guide
> > and change list for the Vantage 803.407C patch. The change list at the
> > end is cumulative for all patches (A,B,C) at the .407 service pack
> > level.
> > I hope this answers your question.
> >
> > ____________ _________ _________ _________ _________ _________ _
> >
> > I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it..
> > It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
6
They do have a list. They just won't let it outside for fear competitors will beat them up with it. Not that any of the competitors are spotlessly flawless. Microsoft can get away with a little more forthrightness due to size and near monopoly position. There have been discussions within EUG to set up some sort of registered user access but even this has seemed to risky. There have also been rumblings by users about maintaining an "external" database but Epicor would not like that either which may be why nothing has happened along that line.

-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Michael McWilliams
Sent: Friday, May 29, 2009 3:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Bug List




My point exactly, how do they fix it if they don't have a list of what is broken.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Steven Gotschall <sgotschall@...> wrote:
>
> Typical. They don't keep a list of the things that are broken, just the things they fixed. Unfortunately, this seems to be a growing trend with most companies. Say what you want about Microsoft, but at least they have a very comprehensive knowledge base of what is broken and how to work around it or what you need to do to fix it.
>
>
> ________________________________
> From: Michael McWilliams <mmcwilliams22@...>
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Sent: Friday, May 29, 2009 3:57:00 PM
> Subject: [Vantage] Bug List
>
>
>
>
>
> I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:
>
> Hello Mike:
> We really do not publish a "bug list."
> The closest document to that would probably be the change list that
> accompanies any service pack or patch. Attached is the install guide
> and change list for the Vantage 803.407C patch. The change list at the
> end is cumulative for all patches (A,B,C) at the .407 service pack
> level.
> I hope this answers your question.
>
> ____________ _________ _________ _________ _________ _________ _
>
> I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it..
> It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





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

I concur !

I have asked for the same type of notification countless times. My last
request was to Joe Jasper and he was kind enough to listen to my concerns
but did say that this would be pretty hard to do given their current model
and it wasn't a concept that was fully supported by all of the EPICOR
executives. In EPICOR's defense I can see why a software company wouldn't
necessarily want to air their dirty laundry....right? From a customer's
perspective if a software vendor has a solid product with solid support
there is nothing to hide. I personally feel that a published list of
known bugs, and future fixes would cause the number of support calls to
plummet and those calls really necessary would be given adequate time to
make further attempts to close them on the first call.

We have had countless cases were we open a call, wait a day or two to get
a call back, and sometimes even do the voice mail jig for a few more days,
recreate the problem with a support person, wait a few more days or weeks
only to hear back from the development team that it is a known bug and it
will be fixed in an upcoming release. If we had known this in advance we
may not have even called if we could come up with a temporary solution
while waiting for the permanent fix. I think that the current support
model only increases the call volumes and increases the frustration level
for Epicor customers (and also likely on the part of the support personnel
as well). This is not a positive influence on improving customer service
levels and can leave a bad taste in your mouth for a long time.

I have had a long tenure as an Infor customer and they put known bugs in
front of their customers. ***AND*** all open customer enhancement requests
are put in front of all customers so that they can vote and prioritize
them in terms of the importance to their respective businesses. If I
submit an enhancement request and it is number 219 in the list I know d*mn
well that I had better develop my own solution rather than hammer on the
vendor. On the otherhand if my request is prioritized as number 2 then
when my itch gets scratched the vendor will also have dozens if not
hundreds of other happy customers along for the ride automatically. This
insures that the software maintenance dollars are used in such a way as to
be the most benefitial to the largest segment of the customer base. This
is truely a win/win partnership and I belive that it is the most
attractive model for customer support; bar none. It is difficult at best
for a software development team to get it right the first time even with
this customer centric model with customer driven input. Without it I don't
know how any support model will support customer's needs. Epicor takes our
enhancement requests one at a time and reviews them internally, then
reports back to the requestor one at a time and tells them what they have
decided to do with it. There has to be a better support model than that.
Waiting days/weeks to hear that it is "working as intended", or that "it
is a known bug targed for patch number XYX" has a few people around here
pretty edgy.

If ever Epicor would like to put a customer panel together to improve the
service model I would be more than happy to be involved. ERP
vendor/customer relationships must be win/win in order for both
organizations to thrive. The touch points between the customer service
team and the customers is the most important of any touch points in the
entire value stream. I feel that a better customer service touch point
would make a good EPICOR ERP solution even better.

There.....I'll step down off of my soapbox now and go home...
Dale.









Dale Walker
Director, Information Technology
Le Sueur Incorporated

507-665-6204 ext 277
www.lesueurinc.com


[Non-text portions of this message have been removed]
8
You can get a comprehensive list of all bugs (SCR's) by product by
version (and other search criteria) and export that and compile it in a
number of different ways. Our Midwest user group is working on a
project along those lines I do believe.



Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of dwalker@...
Sent: Friday, May 29, 2009 4:00 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re:Bug List





Michael,

I concur !

I have asked for the same type of notification countless times. My last
request was to Joe Jasper and he was kind enough to listen to my
concerns
but did say that this would be pretty hard to do given their current
model
and it wasn't a concept that was fully supported by all of the EPICOR
executives. In EPICOR's defense I can see why a software company
wouldn't
necessarily want to air their dirty laundry....right? From a customer's
perspective if a software vendor has a solid product with solid support
there is nothing to hide. I personally feel that a published list of
known bugs, and future fixes would cause the number of support calls to
plummet and those calls really necessary would be given adequate time to

make further attempts to close them on the first call.

We have had countless cases were we open a call, wait a day or two to
get
a call back, and sometimes even do the voice mail jig for a few more
days,
recreate the problem with a support person, wait a few more days or
weeks
only to hear back from the development team that it is a known bug and
it
will be fixed in an upcoming release. If we had known this in advance we

may not have even called if we could come up with a temporary solution
while waiting for the permanent fix. I think that the current support
model only increases the call volumes and increases the frustration
level
for Epicor customers (and also likely on the part of the support
personnel
as well). This is not a positive influence on improving customer service

levels and can leave a bad taste in your mouth for a long time.

I have had a long tenure as an Infor customer and they put known bugs in

front of their customers. ***AND*** all open customer enhancement
requests
are put in front of all customers so that they can vote and prioritize
them in terms of the importance to their respective businesses. If I
submit an enhancement request and it is number 219 in the list I know
d*mn
well that I had better develop my own solution rather than hammer on the

vendor. On the otherhand if my request is prioritized as number 2 then
when my itch gets scratched the vendor will also have dozens if not
hundreds of other happy customers along for the ride automatically. This

insures that the software maintenance dollars are used in such a way as
to
be the most benefitial to the largest segment of the customer base. This

is truely a win/win partnership and I belive that it is the most
attractive model for customer support; bar none. It is difficult at best

for a software development team to get it right the first time even with

this customer centric model with customer driven input. Without it I
don't
know how any support model will support customer's needs. Epicor takes
our
enhancement requests one at a time and reviews them internally, then
reports back to the requestor one at a time and tells them what they
have
decided to do with it. There has to be a better support model than that.

Waiting days/weeks to hear that it is "working as intended", or that "it

is a known bug targed for patch number XYX" has a few people around here

pretty edgy.

If ever Epicor would like to put a customer panel together to improve
the
service model I would be more than happy to be involved. ERP
vendor/customer relationships must be win/win in order for both
organizations to thrive. The touch points between the customer service
team and the customers is the most important of any touch points in the
entire value stream. I feel that a better customer service touch point
would make a good EPICOR ERP solution even better.

There.....I'll step down off of my soapbox now and go home...
Dale.

Dale Walker
Director, Information Technology
Le Sueur Incorporated

507-665-6204 ext 277
www.lesueurinc.com

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





[Non-text portions of this message have been removed]
9
You can also get a comprehensive list of bugs just by using the product on a daily basis!






________________________________
From: Rob Bucek <rbucek@...>
To: vantage@yahoogroups.com
Sent: Friday, May 29, 2009 4:06:03 PM
Subject: RE: [Vantage] Re:Bug List





You can get a comprehensive list of all bugs (SCR's) by product by
version (and other search criteria) and export that and compile it in a
number of different ways. Our Midwest user group is working on a
project along those lines I do believe.

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg com/>

(Click the logo to view our site)

____________ _________ _________ __

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of dwalker@lesueurinc. com
Sent: Friday, May 29, 2009 4:00 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Re:Bug List

Michael,

I concur !

I have asked for the same type of notification countless times. My last
request was to Joe Jasper and he was kind enough to listen to my
concerns
but did say that this would be pretty hard to do given their current
model
and it wasn't a concept that was fully supported by all of the EPICOR
executives. In EPICOR's defense I can see why a software company
wouldn't
necessarily want to air their dirty laundry....right? From a customer's
perspective if a software vendor has a solid product with solid support
there is nothing to hide. I personally feel that a published list of
known bugs, and future fixes would cause the number of support calls to
plummet and those calls really necessary would be given adequate time to

make further attempts to close them on the first call.

We have had countless cases were we open a call, wait a day or two to
get
a call back, and sometimes even do the voice mail jig for a few more
days,
recreate the problem with a support person, wait a few more days or
weeks
only to hear back from the development team that it is a known bug and
it
will be fixed in an upcoming release. If we had known this in advance we

may not have even called if we could come up with a temporary solution
while waiting for the permanent fix. I think that the current support
model only increases the call volumes and increases the frustration
level
for Epicor customers (and also likely on the part of the support
personnel
as well). This is not a positive influence on improving customer service

levels and can leave a bad taste in your mouth for a long time.

I have had a long tenure as an Infor customer and they put known bugs in

front of their customers. ***AND*** all open customer enhancement
requests
are put in front of all customers so that they can vote and prioritize
them in terms of the importance to their respective businesses. If I
submit an enhancement request and it is number 219 in the list I know
d*mn
well that I had better develop my own solution rather than hammer on the

vendor. On the otherhand if my request is prioritized as number 2 then
when my itch gets scratched the vendor will also have dozens if not
hundreds of other happy customers along for the ride automatically. This

insures that the software maintenance dollars are used in such a way as
to
be the most benefitial to the largest segment of the customer base. This

is truely a win/win partnership and I belive that it is the most
attractive model for customer support; bar none. It is difficult at best

for a software development team to get it right the first time even with

this customer centric model with customer driven input. Without it I
don't
know how any support model will support customer's needs. Epicor takes
our
enhancement requests one at a time and reviews them internally, then
reports back to the requestor one at a time and tells them what they
have
decided to do with it. There has to be a better support model than that.

Waiting days/weeks to hear that it is "working as intended", or that "it

is a known bug targed for patch number XYX" has a few people around here

pretty edgy.

If ever Epicor would like to put a customer panel together to improve
the
service model I would be more than happy to be involved. ERP
vendor/customer relationships must be win/win in order for both
organizations to thrive. The touch points between the customer service
team and the customers is the most important of any touch points in the
entire value stream. I feel that a better customer service touch point
would make a good EPICOR ERP solution even better.

There.....I' ll step down off of my soapbox now and go home...
Dale.

Dale Walker
Director, Information Technology
Le Sueur Incorporated

507-665-6204 ext 277
www.lesueurinc. 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]
10
I'm with you. M/S' stuff isn't always the best - but it is usually good enough - and they provide easily accessible support documentation, free code, etc., that no one else comes close to.

Rob




________________________________
From: Steven Gotschall <sgotschall@...>
To: vantage@yahoogroups.com
Sent: Friday, May 29, 2009 4:14:34 PM
Subject: Re: [Vantage] Bug List





Typical. They don't keep a list of the things that are broken, just the things they fixed. Unfortunately, this seems to be a growing trend with most companies. Say what you want about Microsoft, but at least they have a very comprehensive knowledge base of what is broken and how to work around it or what you need to do to fix it.

____________ _________ _________ __
From: Michael McWilliams <mmcwilliams22@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Friday, May 29, 2009 3:57:00 PM
Subject: [Vantage] Bug List

I put in a call yesterday just wondering if epicor keeps a list of reported bugs at a current patch level. Here is the response:

Hello Mike:
We really do not publish a "bug list."
The closest document to that would probably be the change list that
accompanies any service pack or patch. Attached is the install guide
and change list for the Vantage 803.407C patch. The change list at the
end is cumulative for all patches (A,B,C) at the .407 service pack
level.
I hope this answers your question.

____________ _________ _________ _________ _________ _________ _

I really think this is something they should consider doing. Sure it helps to know what you fixed, but it also helps to know what other problems you will be facing. We are all calling and reporting our problems to them anyway, & they are recording the version we are on. It would save so much time having that extra info ahead of time instead of trying to figure out something does not work when another user has already reported it..
It should not be that difficult for them to do this, & I am sure they do internally so why not publish it.

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







[Non-text portions of this message have been removed]
11
Actually they do have a list, they just won't publish it. With every
call they accumulate the problems and work the ones that they assign the
highest priority. Those are the ones that make the patches and/or
service packs.



Charlie Smith

Smith Business Services / 2W Technologies LLC

www.vistaconsultant.com <http://www.vistaconsultant.com/> /
www.2WTech.com









From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Steven Gotschall
Sent: Friday, May 29, 2009 4:15 PM



Typical. They don't keep a list of the things that are broken, just the
things they fixed. Unfortunately, this seems to be a growing trend with
most companies. Say what you want about Microsoft, but at least they
have a very comprehensive knowledge base of what is broken and how to
work around it or what you need to do to fix it.

________________________________
From: Michael McWilliams <mmcwilliams22@...
<mailto:mmcwilliams22%40yahoo.com> >
Sent: Friday, May 29, 2009 3:57:00 PM

I put in a call yesterday just wondering if epicor keeps a list of
reported bugs at a current patch level. Here is the response:

Hello Mike:
We really do not publish a "bug list."
The closest document to that would probably be the change list that
accompanies any service pack or patch. Attached is the install guide
and change list for the Vantage 803.407C patch. The change list at the
end is cumulative for all patches (A,B,C) at the .407 service pack
level.
I hope this answers your question.

____________ _________ _________ _________ _________ _________ _

I really think this is something they should consider doing. Sure it
helps to know what you fixed, but it also helps to know what other
problems you will be facing. We are all calling and reporting our
problems to them anyway, & they are recording the version we are on. It
would save so much time having that extra info ahead of time instead of
trying to figure out something does not work when another user has
already reported it..
It should not be that difficult for them to do this, & I am sure they do
internally so why not publish it.






[Non-text portions of this message have been removed]
12
There is a list maintained by Epicor. You'll need your EpicWeb login to
view it. I'm not sure how useful the list really is, but it does allow
you to search for bug and enhancement requests. I've not found it
completely easy to search. Anyway, here it is...
https://epicweb.epicor.com/ReportServer/Pages/ReportViewer.aspx?%2fePort\
al%2fSearchCRs&rs%3aCommand=Render&rc%3aParameters=true&rc%3aToolbar=tru\
e
<https://epicweb.epicor.com/ReportServer/Pages/ReportViewer.aspx?%2fePor\
tal%2fSearchCRs&rs%3aCommand=Render&rc%3aParameters=true&rc%3aToolbar=tr\
ue>

Lets see if I can paste a sample in here...OK...here is a list of all
open High priority change requests for Vantage...wow, it shows items
open since 2000. if you leave it as an oepne ended search over all
versions.

CR Number Description Version Priority Open Date
Status 5117MPS "Shopwrn in use by XXX" (2624) then (2661) 1
03/14/2001 Open 3151ESC JM In Job Closing the Backflush box is not
updating. 1 11/25/2008 Open 3140ESC JM Error 'Record not
available' in Job Closing 1 11/24/2008 Open 3136MPS Unable to
Print Crystal Forms receive errors 1 01/19/2000 Open 3132ESC
Error 'Unexpected Error' when trying to save a quote. 1 11/21/2008
Open 3566ESC PM Purchasing suggestions not generating any
suggestions. 2 02/09/2009 Open 27229MPS IM Retrieved
transactions disappear when cursor is moved to part field 2
01/09/2008 Open 27513MPS ENG Drag and drop allows you to add the
parent part as a material to itself 2 02/21/2008 Open 24303MPS
UserFile.ValidatePassword is not avaiable via BPM, why? 2 03/08/2007
Open 90BRK OM - Mfg cancel suggestion should be created when ... 2
01/23/2001 Open 27224MPS JM Production detail report is not printing
all sub assemblies 2 01/08/2008 Open 12081MPS DELETE ME 2
07/13/2004 Open 658SYD Supplier price list the currency is greyed
out. 2 02/15/2008 Open 1156ESC OM Pricelist Import Process 2
12/21/2007 Open 3140MPS PO forms are missing fields (ABLE TO
DUPLICATE) after loading .610 2 01/19/2000 Open 1157ESC OM Price
List not functioning correctly 2 12/21/2007 Open 27139MPS PC PO
tracker does not show the receipt attachments 2 12/26/2007 Open
3165ESC PM Two subcontract suggestions create only 1 PO line 2
11/26/2008 Open 23257MPS JM labor edit Icon report is displaying
labor rates 2 12/21/2006 Open 3422ESC JM Unexpected error when
saving the job. 2 01/16/2009 Open 28032MPS 5/1 REP Table
relationships are omitted when a Report Data Def is Duplicated 2
05/02/2008 Open 4640MPS PC Rules not showing on test rules report
(remove -q) 3 12/13/2000 Open 1383ESC SR "Charge ID references
invalid value" when changing amount to MSC charge 3 02/07/2008 Open
4570MPS AR - aging performance in customer tracker 3 11/27/2000
Open


--- In vantage@yahoogroups.com, "Michael McWilliams" <mmcwilliams22@...>
wrote:
>
> I put in a call yesterday just wondering if epicor keeps a list of
reported bugs at a current patch level. Here is the response:
>
> Hello Mike:
> We really do not publish a "bug list."
> The closest document to that would probably be the change list that
> accompanies any service pack or patch. Attached is the install guide
> and change list for the Vantage 803.407C patch. The change list at the
> end is cumulative for all patches (A,B,C) at the .407 service pack
> level.
> I hope this answers your question.
>
>
_______________________________________________________________________
>
> I really think this is something they should consider doing. Sure it
helps to know what you fixed, but it also helps to know what other
problems you will be facing. We are all calling and reporting our
problems to them anyway, & they are recording the version we are on. It
would save so much time having that extra info ahead of time instead of
trying to figure out something does not work when another user has
already reported it.
> It should not be that difficult for them to do this, & I am sure they
do internally so why not publish it.
>




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