Updating Netsuite Price
I am pulling data from a saved search that is calculating what our new base price should be. I would like to push that new price back into Netsuite. I have the data mapping correct to push the new price back in (I am using "Celigoprice : USD : Base Price : Tier 0 Amount").
I would like to avoid updating any prices that do not need to be changed. I figured I could do that in the "How can we find existing records" step. I am currently matching ["internalid","is","{{{id}}}"] to match the record in the saved search to the Netsuite item internal ID.
I would like to add a filter to that to exclude items where the "New Base Price" from the saved search equals the "Base Price". Is that possible? I can't find that field in the filter drop down, and not sure what the field ID would be to put it into a formula.
Thanks!
-
Hi Geoff,
Are you calculating your new base price within your saved search? If so, you could just add a criteria to check if your calculation is different from the base price. Here is an example, with the red lines indicating where your formula would be.
1 -
Thanks for the reply!
Unfortunately the way we are calculating it adds some complexity. We have another dataflow that updates the "surplus classification" (as we call it) to an A, B, C, D, etc based on how overstocked we are. The saved search that the dataflow in question is doing is taking that letter value in a case statement and discounting it by varying percentages.
Only way I can see omitting items that haven't changed within the saved search itself would be to duplicate the case statement to the criteria into a formula and modify it to compare the potential new prices to the existing prices within each case argument.
0 -
Although counter-intuitive, I would always update the price, even if it is the same as the previous one.
There is no performance-gain to be had by doing an extra database query to look up the current value before an update, and NetSuite doesnt register a change if you set a field to the same value it already has. (it doesnt go in the log or call fieldValueChanged methods etc..)
1 -
Ahhh I never even thought of it that way, but yeah it would be the same expense either way. So I either restrict the initial data set from Netsuite that needs to be acted on, or I just update everything.
0 -
I think you would just have to copy your formula into that criteria clause like this. But like Bas van Ditzhuijzen stated, even having the lookup part would utilize your NetSuite concurrency. If that's what you're trying to limit, then you would have to filter the search on the front end like I suggested. You could also add an output filter on your NetSuite export.
1 -
Perfect, thanks Tyler and Bas
0 -
Here is an example of an output filter:
1 -
The output filter worked perfectly. Thank!
1
Please sign in to leave a comment.
Comments
8 comments