Jim,
This was exactly the problem. To give kudos to Epicor Tech Support, I called them with this problem at the same time I posted it here. Normally, I find this venue to often be quicker and sometimes more accurate, but I got the same answer from them in a quick manner. I figure for as much as we badmouth their group, I need to "good-mouth" them when they are helpful. From now on, when I call tech support with Service Connect problems, I'm asking for Ahmed, he hit a home run with this one.
It appears to me that part of the Service Connect functionality (map only those fields you need, and if it gets a field not set, it doesn't change it) hurt in this area. It appears that my "blanking out the field" was treated as if I didn't set it, and it therefore didn't update it. Passing [Clear=BreakListCode,PriceListCodeDesc] through my XSLT map to the ROWMOD did the trick.
I've got a quick followup question: Currently, I pass the OrderNum and OrderLine through to the workflow for the one I want to update. However, when I do the "SalesOrder.GetByID", it returns all OrderDtl records with that order. In order to get the only one I need, I used the OrderDtlSearch service to get just the Order Line needed, but when I pass through and call SalesOrder.Update, it returns back all order lines. Then, as I continue in my workflow, when I continue to map (and, for example, map a new UnitPrice in), it tries to affect all OrderDtl rows, not just the one I want. How do you go about in the conversion mapping from one response to a new request and passing only the OrderDtl row you are dealing with, not all of them?
Thanks.
Kevin
This was exactly the problem. To give kudos to Epicor Tech Support, I called them with this problem at the same time I posted it here. Normally, I find this venue to often be quicker and sometimes more accurate, but I got the same answer from them in a quick manner. I figure for as much as we badmouth their group, I need to "good-mouth" them when they are helpful. From now on, when I call tech support with Service Connect problems, I'm asking for Ahmed, he hit a home run with this one.
It appears to me that part of the Service Connect functionality (map only those fields you need, and if it gets a field not set, it doesn't change it) hurt in this area. It appears that my "blanking out the field" was treated as if I didn't set it, and it therefore didn't update it. Passing [Clear=BreakListCode,PriceListCodeDesc] through my XSLT map to the ROWMOD did the trick.
I've got a quick followup question: Currently, I pass the OrderNum and OrderLine through to the workflow for the one I want to update. However, when I do the "SalesOrder.GetByID", it returns all OrderDtl records with that order. In order to get the only one I need, I used the OrderDtlSearch service to get just the Order Line needed, but when I pass through and call SalesOrder.Update, it returns back all order lines. Then, as I continue in my workflow, when I continue to map (and, for example, map a new UnitPrice in), it tries to affect all OrderDtl rows, not just the one I want. How do you go about in the conversion mapping from one response to a new request and passing only the OrderDtl row you are dealing with, not all of them?
Thanks.
Kevin
--- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@...> wrote:
>
> Kevin,
>
> There is some Vantage functionality that may be coming into play relative to order pricing that might be controlling the process, however, generically the way to clear a feild with Service Connect is to put a string as follows into the RowMod field in your xslt map.
>
> [Clear=ShortChar02]
>
> You can also specify multiple fields this way:
>
> [Clear=ShortChar02, ShortChar03]
>
> The field name must be exactly as it is shown in the xslt map.
>
> Then, when the incoming data is blank, Service Connect will force the field to be cleared. If Vantage business logic is controlling the behavior of the field, you'll have to look to BPM's to have any effect.
>
> Hope this helps.
>
> Jim Pratt
>
> Vantage 8.03.404B
>
> --- In vantage@yahoogroups.com, "alfe_ksimon" <alfe_ksimon@> wrote:
> >
> >
> > I'm hoping that someone has a handy trick in their back pocket. I've got a Service Connect workflow that is designed to take a sales order, override the price list, blank out the price list (make it null), and change the unit price. The problem I am having is on "blanking out" the price list. No matter what I do, it is not removing the price list.
> >
> > I've tried setting the price list code to a value of a single space (" "), tried setting the literal value and "force empty node", tried moving a value from another field (ShortChar10) that I know is also blank, etc. Doesn't matter, after the update, the sales order maintains the price list that it had to start.
> >
> > To try to narrow down the problem in the workflow, I set another unrelated field to a value of "abcd" (so I know the update is working as I see that update working), and I've tried changing the price list to a value of "NONE" (which gives an error on the update, as NONE is not a valid price list). When I set up a price list of NONE, the update works. However, setting up a dummy price list is not something I want to do.
> >
> > I want to be able to remove the price list via Service Connect the same way I can open sales order entry and remove it there. Has anyone run into this type of issue with Service Connect, and have you figured out a trick around it?
> >
> > Thanks.
> > Kevin Simon
> >
>