I see there are 5 checkoff fields in QuoteHed. I would like to utilize one or more of those fields. We do not have CRM, so I am attempting to replicate one of the base features of being able to mark a quote as “won”. Using Checkoff1, I want to be able to check the box. However, a basic UBAQ is not enough as we have the logging turned on which forces a reason when updating a quoted quote. I see that the EQSyst table contains the label for the Checkoff fields. How do I update that table without running a custom UBAQ? Is there a form to define the checkoff label names for Quoting, the same way there is for Jobs? Also is there a way to set a checkoff field to true and submit a reason without using a BPM?
Thanks!
Nate
1 Like
I can’t find a way to do this at all so far. I think I am going to have to use a UBAQ with a custom BPM to submit the data. Does anyone know what method needs the “Change Description Required for Log”?
I ran a trace, but I can’t find anything about a reason. I am guessing it is stored in some kind of log file, but it must be done via a method, right?
Looking at Ice.ChgLog and ChgLogTB, I think this might be the right area. We don’t have any changes logged on QuoteHed yet. When I can find the method that updates the change log when I want to change QuoteHed.Checkoff1, I will post back with the process.
I feel like I’m missing something here. When you talk about setting those fields what did you have in mind if not something programmatic? Could you not examine the methods available in Quote method directives or BL Tester to find something? I think I may be misunderstanding your question, but I get triggered by QuoteHed questions.
And just to beat @Mark_Wonsil to it…
I don’t see any of the checkoff fields in the native Quote forms. Perhaps they are reserved for the CRM module? If I could just check a box and trace the method I would be in business. Instead I am trying to find that method without being able to check the box. When I run a UBAQ to update Checkoff1 to true, I get an error that a reason is required for the log. I know this is because we have the log turned on for the quote changes. I don’t want to turn that off. But I do want to find the method that allows me to both update the value in the checkoff fields, and supply the necessary reason description for the log.
I haven’t really done anything with BL tester. I looked through the various quote methods and I don’t see anything that stands out.
Ah ok, sure enough ours is custom (Classic UX) and we do have CRM.
Edit: just noticed that actual checkbox isn’t a custom field, the one aboven it is the one I was looking at
I can run a trace though
Strangely (to my mind anyways) it just runs GetQuotedInfo which sounds like it’s reading not writing, but the dataset has “Quoted” = true. This is the first packet after the tracing packets.
Then it runs Update with “Quoted” = true.
In case I got this wrong, I opened an existing quote that wasn’t quoted, enabled tracing, marked it quoted, disabled tracing, in that order.
In SQL not quoted:
Pulled up quote in BL Tester using GetByID
Set Quoted flag to true by ticking it and selected GetQuotedInfo
After invoking GetQuotedInfo:
Selected update and invoked
in SQL Quoted is now true
I also got a couple of errors that I think are customer-related, so your mileage could vary. But it did update Quoted to true, so it seems GetQuotedInfo edits the dataset prior to saving via Update.
I am not sure where you are going with this. Does this help me supply the reason for the log?
This is what I was thinking about
Sorry, I just realized you’re talking about the method that updates the change log, not the quote. 
Nate,
We’ve got CRM, and when quotes are won or lost, the reason code is set to WON or LOST. This automatically checks the Quoted box for us. Not sure if it helps, but it’s all I can think of for ‘reasons’… I wouldn’t be surprised if there were skeletons that Epicor expects to be processed with CRM. You might have to go down the Task rabbit hole if Epicor wants that. Feed the beast!
QuoteHed.Quoted field help:
Indicates if the quote has been quoted. That is, the details have been entered, prices have been determined and is ready to be sent to the customer. The quoter considers this quote complete. Toggling this field also sets the DateQuoted equal to the current system date.
I think without CRM I can’t do anything with Tasks. I think I can replicate what I want using a custom field instead of this checkoff field. Thanks guys for your great feedback!