My Stuff
Comments
-
Yes most of our order are to wholesalers so we want to send complete lines not complete orders. So if we mark the order ship complete then the whole order is frozen until every item is in stock.
-
It would also be good to be able to set the COMMIT preference by customer to override the global settings.
-
I found the problem you need to use "Advanced Partner Role' But unfortunately you need a full licence for that. From what I can see you either use the Partner Role no licence required. Which gives 3 pre-determined reports. Or you have the Advanced Partner Role but that requires a full licence because it is just like a full…
-
That is exactly what I have done. I just thought it would have been a neat trick to give them a live KPI, but in this instance it is not worth paying for at all. A daily report is all they wanted anyway. in different circumstances then the Advance Partner Role could be useful and good value for money. In the UK we can't…
-
I am talking about the UI in the Forum not Netsuite.
-
What about a better app for the iPad and iPad mini? I think there would be more demand for thatthan the iPhone App. I would love my reps to be able to have a 3G enabled iPad with the ability to raise quotations etc.
-
Yes but having done the iPhone app it can't be a big task to re-format it for the iPads compared to developing an iPhone app from scratch.
-
LPAD won't work because the mpn from one supplier is a 13 digit number and 5 or 6 from others and some are alpha. What I need is to pick up the full text of the originating field.
-
Sorry not to misslead you but the actual expression I am trying to use is:- CONCAT({mpn},' ',{custitemb1})
-
Yes that worked.
-
Also how do I get it to produce 00033 instead of just 33
-
It is a customer error. Supplier part number was set to 00033 and MPN was set to 33. I have changed it and it is all working now. Thanks so much for you prompt help. Paul
-
I thought you might be on to something but: CONCAT({mpn,' ',{field1}) produces : ERROR: Invalid Expression
-
Thanks Evan that's very helpful.
-
Oh one other oddity is that when saving the above script to workflow it reports that it is 42 characters too long. But it does save the whole script and as far as I can see it is working perfectly well.
-
I get the same error, but I think your code is more elegant. Interestingly every time I hit "edit" the code strips out all the + signs and replaces them with a blank. I don't understand what the problem is.
-
I had to change the field name to reduce its length but this version of the script works in "MASS UPDATE" CASE WHEN {custitemlm} <=136 THEN ROUND({custitemlm}/9.1,0) WHEN {custitemlm} BETWEEN 137 AND 249 THEN ROUND(({custitemlm}+33.5)/11.3,0) WHEN {custitemlm} BETWEEN 250 AND 470 THEN ROUND(({custitemlm}+118.5)/14.7,0)…
-
I just did an experiment and put the code into a test "Mass Update" and it works perfectly. It seems a shame to have to put this code into a Cron that will run every night rather than using a workflow so it only runs when something changes. It is an utter waste of system resources and slows the system for everyone. This…
-
I have found the problem with the help of support. the working script is as follows:- CASE WHEN {custitemlm} BETWEEN 0 AND 136 THEN ROUND({custitemlm}/9.1,0) WHEN {custitemlm} BETWEEN 137 AND 249 THEN ROUND(({custitemlm}+33.5)/11.3,0) WHEN {custitemlm} BETWEEN 250 AND 470 THEN ROUND(({custitemlm}+118.5)/14.7,0) WHEN…
-
I'd look at a data type mismatch. The case statement is calculating a numeric value. The error occurs on setting that numeric value into your other custom field: custitemcustitemcustitemhalogenrepl Is that field defined as a numeric? Both custitemtestlumens and custitemcustitemcustitemhalogenrepl are set as "Decimal Number"
-
Will this work? Its the same statement but about 175 characters shorter I did the following; reversed the order of the conditions to eliminate the And in statement decrease each condition by 1 to eliminate the = from each wrapped the entire statement in a single round to get rid on the round on each one (not if this one…
-
I have changed the code thus:- Replacement (W)=CASE WHEN {custitemtestlumens} <=136 THEN ROUND({custitemtestlumens}/9.1,0) WHEN {custitemtestlumens} BETWEEN 137 AND 249 THEN ROUND(({custitemtestlumens}+33.5)/11.3,0) WHEN {custitemtestlumens} BETWEEN 250 AND 470 THEN ROUND(({custitemtestlumens}+118.5)/14.7,0) WHEN…
-
Sorry Voltron I am not sure what you are suggesting. Are you saying that I am wrong to use the Transaction for the wWORKFLOW and that is should be on the customer record?
-
Oh dear it looks that even if I could send an email to a custom email address on the customers record. There is no way t attach the relevant document. If I have got this assumption wrong please let me know. Thanks.
-
Got it thanks. Now I need to find out how to trigger it to send a copy of the document.
-
1. No I have set the workflow on the transaction record, is that wrong? It is the creation of a sales order or fulfilment that will trigger the order confirmation/fulfilment notification to the buyer not the creation of the customer. 2. Yes the custom field does have the value stored. 3. Most of our customers are…
-
No I am still hoping that this feature will become a standard option in the future. At the NS conference in SF this problem was raised at the breakout sessions and they asked how many people had problem with the inability to designate different email addresses to different documents and just about everyone in the room…