[jatm@cm]

Hi,

We have swapped over to the advanced printing for the packing slip.

However by default the tracking number(s) are accessed from the salesorder, ${salesorder.linkedtrackingnumbers} , in the case where a shipment has multiple fulfilments this means the packing slip ends up with all the tracking numbers rather than the one for the particular fulfilment from which the packing slip is being created.

I have tried ${record.trackingnumbers} but this does not work, given that the packages is a sublist is there something like record.packages[0].trackingnumber ?

On a general note is there either a full schema list for the advanced printing templates (other than the add fields button in WYSIWYG which seems to have lots of values not applicable to the specific record you are on) or anyway to print all the information in an object, eg equivalent of console.log record ?
This is a cached copy. Click here to see the original post.

[sterlingr]

I would like to know too… We have the same issue and it actually affects our email template for fulfillment as well. I fooled around with it a whole lot and haven’t found the solution yet. :-/

[michoel]

On a general note is there either a full schema list for the advanced printing templates (other than the add fields button in WYSIWYG which seems to have lots of values not applicable to the specific record you are on) or anyway to print all the information in an object, eg equivalent of console.log record ?

Try opening a developer console window in your browser and running nlapiLoadRecord(‘salesorder’, xxx)

[jatm@cm]

Originally posted by sterlingr

View Post

I would like to know too… We have the same issue and it actually affects our email template for fulfillment as well. I fooled around with it a whole lot and haven’t found the solution yet. :-/

Quickly tested this for printing the tracking number:

${package.packagetrackingnumberups}

note that the above will only work for UPS, if not using ups you need to put an if statement for record.package (not sure if fedex has a different package type)

and

in answer to my own question adding

&xml=t to the end of the url makes finding the fields names alot easier

[sterlingr]

Thanks, I think that’s great. It didn’t occur to me to try to list the packages.

This was my previous workaround which did work okay but it would list all tracking numbers even previous shipments on the same order.

<#assign trackinglist1 = transaction.createdfrom.trackingnumbers?replace("
“, ” “)>
${tracking}

I’m now inserting your list solution and I just put in two lines one each for USPS or UPS. I didn’t use the If because if there’s nothing it won’t list anyways.

${package.packagetrackingnumberusps}
${packageups.packagetrackingnumberups}

[torin@aminian.com]

This is a late response but Suite Answer 46503 offers a great solution. You can use a custom body field to source in the tracking numbers from that fulfillment using a saved search. You can then use this field id on your template.

[Author]

Posts