BAM Auto Print 9.05

Yahoo Archive
1
OK here is one way I do the autoprint of Shop Dispatch Report.

Create a new user called something other than "Reports".. funny story, I created a user called "Reports" then tried to print and it just kept crashing. Seems it was building a string path for the report .xml but since it was called "Reports" and the folder the report is in is also called "Reports" it kacked out with \reports/reports. Probably the only person to ever do this...

Anyway, once you create a new user, give them only permissions to run the report(s) you need. Then set up a recurring daily schedule for say 6:00AM in your System Agent.
Now set up a new Epicor Icon and a new .mfgsys that is linked to the Icon with the Autologon Username and Password set in the .mfgsys

Now log-in to Epicor as this new user, launch the Shop Dispatch Report and print it to the preferred printer but use the Scheduled Report options to submit it on the new schedule at 6:00AM.

Exit Epicor.

Next, set the Windows Task Manager to launch the new Epicor Icon at 7:00AM and the system will launch your new Epicor app with the new .mfgsys autologon for the new user and print out the generated report because it automatically prints out missed reports when you login.

Hope this helps someone.

Regards,

George Hicks
Pacific Consolidated Industries
2
Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.

Any ideas?

I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
3
We are on 9.05.600b and are using BAM/auto print rules heavily on several forms.

You do have to setup the BAM with a rule and then setup the Report Data Defn auto printing section as well.

Brad Boes
Metalworks


--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
> Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
>
> Any ideas?
>
> I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
>
4
We are getting something similiar in 9.04.505c.

It was working, we swapped our printer an now it wont work.

We are getting a COMPLETE in the history tasks, but we are getting an error in
the reports section.

It tells us to preview the report for the error.

When we do preview it, there isnt an error.

Any ideas?




________________________________
From: brad_boes <bboes@...>
To: vantage@yahoogroups.com
Sent: Thu, 6 January, 2011 21:23:49
Subject: [Vantage] Re: BAM Auto Print 9.05

Â
We are on 9.05.600b and are using BAM/auto print rules heavily on several forms.

You do have to setup the BAM with a rule and then setup the Report Data Defn
auto printing section as well.

Brad Boes
Metalworks

--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
> Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting
>in the System Monitor Reports Tab "System error has occured...", when we Print
>Preview to see the error we get an Unhandled exception "Invalid Report Type or
>Print Driver specified". I get this for both Sales Order PickList and Sales
>Order Acknowledgement. When I reported this, I was told someone else reported
>the same error with AR Invoices but no response back from developement yet.
>
> Any ideas?
>
> I'm trying to figure out if the problem is with my setup or its truely a bug
>that I have to work around.
>







[Non-text portions of this message have been removed]
5
Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.

--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
> Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
>
> Any ideas?
>
> I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
>
6
Has this issue been resolved? We are on Epicor 905.603 and we are seeing the exact same issue with auto printing through BAM's and support is telling us they can't replicate it on their system.

Did you get a work around or a one-off fix for this?

--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
>
>
> Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
>
> --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> >
> > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> >
> > Any ideas?
> >
> > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> >
>
7
I'm told it will be fixed in 9.05.609.
I worked around it with a screen customization to submit the print job to the task agent. Let me know if you want sample code.

Dan

--- In vantage@yahoogroups.com, "Robert" <robert.nupp@...> wrote:
>
> Has this issue been resolved? We are on Epicor 905.603 and we are seeing the exact same issue with auto printing through BAM's and support is telling us they can't replicate it on their system.
>
> Did you get a work around or a one-off fix for this?
>
> --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> >
> >
> >
> > Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
> >
> > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > >
> > > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> > >
> > > Any ideas?
> > >
> > > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> > >
> >
>
8
Yes, could I get the sample code you created to work around this issue?
Thank you!



Robert Nupp





[Non-text portions of this message have been removed]
9
I wouldn't mind seeing some sample code on this as well, Dan.

Thanks


--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
>
>
> I'm told it will be fixed in 9.05.609.
> I worked around it with a screen customization to submit the print job to the task agent. Let me know if you want sample code.
>
> Dan
>
> --- In vantage@yahoogroups.com, "Robert" <robert.nupp@> wrote:
> >
> > Has this issue been resolved? We are on Epicor 905.603 and we are seeing the exact same issue with auto printing through BAM's and support is telling us they can't replicate it on their system.
> >
> > Did you get a work around or a one-off fix for this?
> >
> > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > >
> > >
> > >
> > > Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
> > >
> > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > >
> > > > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> > > >
> > > > Any ideas?
> > > >
> > > > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> > > >
> > >
> >
>
10
I learned this week that Epicor found the problem with the BAM Auto Printing in 9.05.

The report type in the RDD defaults to "Base". E9 knows to print with Crystal when printing from a menu, but when printing from a BAM is gets confused. The workaround is to change the report type on the RDD to Crystal. I did a test and it seems to work. Also, they moved the BAM fix to release 607.

--- In vantage@yahoogroups.com, "bobschnable" <bschnable@...> wrote:
>
> I wouldn't mind seeing some sample code on this as well, Dan.
>
> Thanks
>
>
> --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> >
> >
> >
> > I'm told it will be fixed in 9.05.609.
> > I worked around it with a screen customization to submit the print job to the task agent. Let me know if you want sample code.
> >
> > Dan
> >
> > --- In vantage@yahoogroups.com, "Robert" <robert.nupp@> wrote:
> > >
> > > Has this issue been resolved? We are on Epicor 905.603 and we are seeing the exact same issue with auto printing through BAM's and support is telling us they can't replicate it on their system.
> > >
> > > Did you get a work around or a one-off fix for this?
> > >
> > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > >
> > > >
> > > >
> > > > Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
> > > >
> > > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > > >
> > > > > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> > > > >
> > > > > Any ideas?
> > > > >
> > > > > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> > > > >
> > > >
> > >
> >
>
11
I was actually looking for the code for other reasons than as a workaround to the BAM issue. We currently have several different methods we use to auto-print things, and I wanted to see your method to see if it possibly has benefits our other ones do not currently have.

Thanks
--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
> I learned this week that Epicor found the problem with the BAM Auto Printing in 9.05.
>
> The report type in the RDD defaults to "Base". E9 knows to print with Crystal when printing from a menu, but when printing from a BAM is gets confused. The workaround is to change the report type on the RDD to Crystal. I did a test and it seems to work. Also, they moved the BAM fix to release 607.
>
> --- In vantage@yahoogroups.com, "bobschnable" <bschnable@> wrote:
> >
> > I wouldn't mind seeing some sample code on this as well, Dan.
> >
> > Thanks
> >
> >
> > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > >
> > >
> > >
> > > I'm told it will be fixed in 9.05.609.
> > > I worked around it with a screen customization to submit the print job to the task agent. Let me know if you want sample code.
> > >
> > > Dan
> > >
> > > --- In vantage@yahoogroups.com, "Robert" <robert.nupp@> wrote:
> > > >
> > > > Has this issue been resolved? We are on Epicor 905.603 and we are seeing the exact same issue with auto printing through BAM's and support is telling us they can't replicate it on their system.
> > > >
> > > > Did you get a work around or a one-off fix for this?
> > > >
> > > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > > >
> > > > >
> > > > >
> > > > > Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
> > > > >
> > > > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > > > >
> > > > > > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> > > > > >
> > > > >
> > > >
> > >
> >
>
12
Does anyone have any more recent information on this? I tried this work
around but this was still a no go for working.


--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
> >
> > I learned this week that Epicor found the problem with the BAM Auto
> Printing in 9.05.
> >
> > The report type in the RDD defaults to "Base". E9 knows to print with
> Crystal when printing from a menu, but when printing from a BAM is gets
> confused. The workaround is to change the report type on the RDD to
> Crystal. I did a test and it seems to work. Also, they moved the BAM fix
> to release 607.
> >
> > --- In vantage@yahoogroups.com, "bobschnable" <bschnable@> wrote:
> > >
> > > I wouldn't mind seeing some sample code on this as well, Dan.
> > >
> > > Thanks
> > >
> > >
> > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > >
> > > >
> > > >
> > > > I'm told it will be fixed in 9.05.609.
> > > > I worked around it with a screen customization to submit the print
> job to the task agent. Let me know if you want sample code.
> > > >
> > > > Dan
> > > >
> > > > --- In vantage@yahoogroups.com, "Robert" <robert.nupp@> wrote:
> > > > >
> > > > > Has this issue been resolved? We are on Epicor 905.603 and we are
> seeing the exact same issue with auto printing through BAM's and support is
> telling us they can't replicate it on their system.
> > > > >
> > > > > Did you get a work around or a one-off fix for this?
> > > > >
> > > > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Support agrees there are autoprinting problems with 9.05.602A,
> Crystal Reports XML files are properly created, but the System Monitor can
> not print them. I'm just posting to let people know to be carefull
> upgrading to 9.05.602A if you autoprint.
> > > > > >
> > > > > > --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> > > > > > >
> > > > > > > Has anyone been successful with BAM Auto Printing? in 9.05.602A
> we are getting in the System Monitor Reports Tab "System error has
> occured...", when we Print Preview to see the error we get an Unhandled
> exception "Invalid Report Type or Print Driver specified". I get this for
> both Sales Order PickList and Sales Order Acknowledgement. When I reported
> this, I was told someone else reported the same error with AR Invoices but
> no response back from developement yet.
> > > > > > >
> > > > > > > Any ideas?
> > > > > > >
> > > > > > > I'm trying to figure out if the problem is with my setup or its
> truely a bug that I have to work around.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
>
>
>


[Non-text portions of this message have been removed]
13
I am just testing some BAMs and was getting this error. I believe what I did to correct the problem was simple. On the Report Style, Styles, Style Detail sheet there is a Report Type. This needs to be set to Crystal. On the Report Data Definition, Detail sheet, there is also a Report Type field. I believe this needs to be set to Crystal as well.

I am working on version 9.05.606, but if you haven't fixed it yet, try the above.

Paula

--- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@...> wrote:
>
>
>
> Support agrees there are autoprinting problems with 9.05.602A, Crystal Reports XML files are properly created, but the System Monitor can not print them. I'm just posting to let people know to be carefull upgrading to 9.05.602A if you autoprint.
>
> --- In vantage@yahoogroups.com, "Dan Sirow" <dansirow@> wrote:
> >
> > Has anyone been successful with BAM Auto Printing? in 9.05.602A we are getting in the System Monitor Reports Tab "System error has occured...", when we Print Preview to see the error we get an Unhandled exception "Invalid Report Type or Print Driver specified". I get this for both Sales Order PickList and Sales Order Acknowledgement. When I reported this, I was told someone else reported the same error with AR Invoices but no response back from developement yet.
> >
> > Any ideas?
> >
> > I'm trying to figure out if the problem is with my setup or its truely a bug that I have to work around.
> >
>