This topic contains 14 replies, has 0 voices, and was last updated by mmarchant77 7 years, 10 months ago.

  • Author
    Posts
  • #2186

    Robbie

    I’m having a hard time customizing the Statement printout. Basically my problem is that I don’t know what fields are available, since the Statement isn’t actually a record type. Is there anywhere that shows what fields are available for a Statement?

    The two specific ones I’m wondering about are simply the Customer Name and the Ship Address.

    Thanks!
    This is a cached copy. Click here to see the original post.

  • #2187

    corey

    Just print one out with a regular print layout and append the url with &xml=t, that’ll give you all the fields available to you. There’s no real documentation on available fields, it’s more of a trial and error thing.

    Strike that. Won’t work.

  • #2188

    corey

    Ok, if you look at your statement form record and flip it to advanced printing the default layout that comes up is listed as type invoice. So, I would bet you could just make an invoice use the xml hack and have all the same fields there as would be on a statement.

  • #2189

    Robbie

    Lol I tried the xml=T thing but yea it didn’t work. As for doing it like an invoice, I feel like I’ve tried all the normal customer type field IDs: entity, entityid, companyname, customer. Nothing I’ve tried has worked. It seems pretty silly that there wouldn’t be a customer name field on a statement though :-


    corey replied on 02/23/2015, 10:06 AM: No, you gotta do the xml thing on an invoice. That’ll give you what you want.

  • #2190

    Infinet Cloud Solutions

    Have you looked at the 2015.1 Release Preview? there are quite a few improvements in the Advanced Templates functionality one of which is the ability to select from a dropdown fields to insert into the template, you can then review the source to find the fieldname.

  • #2191

    dmatyas

    Currently no customer information is available on the Statement. There is issue filed already and I took extra note of it as well. Customer information should be available in couple of weeks. Once it’s done even the Help will be updated with list of fields available for Satement.

  • #2192

    Robbie

    Dmatyas – Great, thank you. Could you share the number for that issue? I’d like to keep an eye one it.

    ICS – Yes, I checked that out, but it looks like you can only use dropdowns for email templates, not for the advanced print templates. Plus I get an unexpected error every time I try to save the advanced template in Release Preview

    Thanks for the help!

    Robbie


    corey replied on 03/04/2015, 03:25 PM: ‘swhy I use an external editor and paste and save. Still.

  • #2193

    rnedelkow

    I think this is being tracked in Defect 301810: Advanced Printing > Customize the Standard Statement PDF/HTML Template > Add Standard Fields such as Subsidiary, Customer, Overdue balance> Print > The fields values are empty. You can attach your case in order to receive status updates.

  • #2194

    rnedelkow

    Possible alternate solution to include Customer Name and Partner Name on the Advanced PDF layout:

    1. Create custom fields.

    a. Customization>Lists, Records & Fields>Entity Fields>New.

    b. Type = Free-Form Text.

    c. On Display tab, make sure to set the SUBTAB to Main.

    d. Make sure to check the following box

    1. Store Value (Main header)

    2. Customer (Applies to tab)

    e. On the Label, put Customer Name then Save.

    f. On the second custom body field that you will create, Label should be Partner Name. Follow steps a to c.

    g. Once the two custom fields are saved, edit both and make sure to click Apply to Forms. Choose a custom customer form that you will use.

    2. Open a customer record where you have associated a partner record. Manually encode the customer name and partner name. Take note of the internal id of the custom fields that you have created earlier as we will use it later.

    3. Customization>Forms>Advanced PDF /HTML templates. Click Customize for Standard PDF/HTML Template.

    4. Type the following on your advanced pdf/html template:

    ${record.custentity8@label}

    ${record.custentity8}

    Where the custentity section is the internal id of your custom field.

    5. Save the custom PDF layout with your preferred name.

    6. Then go to Customization>Forms>Transaction Forms. Look for Standard Statement and click Customize.

    7. On Advanced PDF/HTML Template, set your custom advanced PDF/HTML layout.

    8. Save the Transaction form. Now open a customer record. Under Actions>Generate Statements. Under Form, choose the custom transaction form saved from step 7 and then click Print.

    Notes:

    You have to update the customer to supply the values on the custom fields that you will create.


    Robbie replied on 03/06/2015, 01:47 PM: Awesome, thanks for the workaround!

  • #2195

    billing@merchantsinfo.com

    I know this is a year old, but I’m still a bit of a novice in some of these matters and encountering the same issues, but not quite understanding where to go to find the answers. I’m specifically trying to add the check number for a payment onto a customer statement (PDF).

    The syntax for the header is

    ${line.description@label}

    and

    ${line.description}

    for the detail, but I’m not sure what to replace “line.description@label” or “line.description” with.

  • #2196

    Nelliott

    Neither, unless you no longer need the description field?

    If you want to display the checknumber you will need the NetSuite internal id of that field

    You probably need to use the records browser to identify the field or you could try loading the record and using the &xml=T “trick” mentioned in previous posts.

    Once you know the internal id you should be good to add it in.

    By the way, using @label pulls in the label for a field without it you’re bringing in the value held in the field.

  • #2197

    billing@merchantsinfo.com

    My apologies – I just copied the line.description lines as examples. The Description field is still there, this is just the next line down now. So far as I can tell, the syntax should be customerpayment.checknum (see below for how I have it now), but all I get is a number of “Expression customerpayment is undefined on line 218, column 42 in template.” errors.

    Column Header

    Check Number

    Detail

    ${customerpayment.checknum}

    FYI: I used the &xml=t trick on a payment to determine what the record type for a payment is (customerpayment>), and “checknum” is the internal ID for that field. Not sure what I’m missing.

  • #2198

    Nelliott

    Your problem is that the either customerpayment record is not “exposed” or, if it’s the record you are working on and in scope, you probably need to use “transaction.” or “record.”

    It’s worth noting that there’s a limited amount of detail available beyond the root record when working on Adv Print. and often you need to create custom fields that source form the record you’re interested in so they are available to the advanced print code.

    There’s an example of the kind of thing I’m talking about posted by rnedelkow earlier in the posts.

  • #2199

    billing@merchantsinfo.com

    Thanks for your help. Seems like this is more work than it’s worth, if it’s even possible. Can’t exactly create check number custom fields for every payment on the customer record. It’s just bonkers to me that putting something like a check number of a payment on a statement is so difficult. Thanks again.

  • #2200

    mmarchant77

    Does anyone know if it’s possible to get the customer name on the statement lines? We need this because we’re using consolidated statements and we would like to know what is the child customer on each line. I tried finding the field id by adding it in the Advanced Pdf wysiwyg tool and it’s not possible to select line fields so this didn’t work. Thanks!


    mmarchant77 replied on 01/19/2017, 02:41 PM: NS support answered and provided this for the line subcustomer id: ${line.subname}

You must be logged in to reply to this topic.