Ah yes, always forget that! Works fine now - thanks!

I've been trying this, and despite following this and other SuiteAnswer examples, I keep getting the following error when the PDF is validated. " The reference to entity "c" must end with the ';' delimiter." This relates to the &c=AccountID element in the URL Has anyone come across this?

You don't mention how you're printing the picking tickets - from the Sales Order, in bulk, or from the Item Fulfilment - however you should find that using ${item.inventorydetail} will show you the Bin number and the qty available in that bin.

You shouldn't need to do that, adding the global permission to the employee record is supposed to allow access.

Despite adding the "Mobile Device Access" global permission, I'm still getting a permission error when trying to use my admin role. Other roles seem to work OK.

The update is also dated 21 Dec 2011!

Same here - I've not actually used the app for years, due to it being so bad - but it pretty much looks the same to me

There's no new version in the App Store, just the same Dec 2011 v1.5

A new iPhone app only took 4 years, don't hold your breath! :)

Using 'Event Type = Print' should help you do this. Trigger Type = Before Record Load On Create = FALSE On Update = TRUE Event Type = Print

Yes, I found another thread which covered the same issue. {id} is the formula required - I'd tried {internalid} but I forgot how NS likes to use different values for every transaction type! :)

Damn :( Just checked 2013.1 and it's not there either. Ah well, back to the drawing board.

Now there's a thought :)

Thanks, that worked! Wish all the various "which codes work where" were documented somewhere! :(

Thanks! I'd totally missed the "Current Record" option inside the Transaction field. Also, needed to change workflow action to After Submit to ensure the transaction number was known. Thanks for your help.

Apologies, should has mentioned in the original message - this is a Workflow question. I've just completed doing it by using a new Action for each country, but still wondering if there's a more efficient way to do it.

Just trying to join two parameters into a single formula. As Net Amount is also not available in a Workflow Visual Builder, I'm having to build it within a custom formula. Any idea why this doesn't seem to work? {shipcountry}='AU' and {netamount}>=750.00 Looking to trigger on any order shipping to Australia for more than…

Doh! Thanks Evan!

Thanks anyway. Ended up getting our Netsuite partner to build a script to handle all this. We're now able to set the value of any custom field based upon the Shipping Country. Makes life a lot easier! :)

I did try using it in a formula, but the workflow didn't seem to trigger. I'll make a simpler workflow to test it again.

Tried this with a very simple {shipcountry} = 'Australia' The workflow itself triggered, but not the action.

Is there a way to view the progress with defects?

Bingo! Turned on Firebug, and here it is! freeitemkeys is undefined for (i = 0; i < freeitemkeys.length; i++) Just need to persuade Support that it's a defect! :)

Could I have an update on this please. Will this defect fix be in 2011.1 as promised??

OK - it took several hours, but I've finally tracked it down! Here's how to cause it. [1] Have a WorkFlow which sets the "Ship Via" field [2] Have items entered in the "Free Shipping Items" tab on the DEFAULT shipping method. That's it! If you now try to add items to ANY transaction which has a WorkFlow attached to it…

Evan, thanks very much for this. Yes, we utilise WorkFlows to look after the various types of transactions that we are creating (Loan stock, Transfers, Exchanges, Staff Sale, etc) - these are all done manually, and these workflows ensure consistency. I should have perhaps described them as extensive usage, as though we…

This defect actually causes multiple other issues with the shipping too. If you set the ship via method via a WorkFlow, then it will not work as expected at all. It looks as if it's actually not setting all the required data fields correctly when it's done this way - so NetSuite then pulls this data from the Default…

Finally, fixed this morning! Thank you!

The status will be updated when the fix is ready for internal testing. You can see this in your support center login if you've been attached to the defect. The fix for this issue has been coded but is not ready for internal testing. The fix will be released in 2011.1. Thanks, -e Just tested this in 2011.1 beta - and the…

Is there any update on this defect?