[EnablingSolutions]

For the past couple of weeks the following code has been working:

${item.item.itemid}
${item.description}

Giving us the Item’s Name/Number in bold and dark grey, and the Item’s Description on the line below as normal text.

However, something has happened over the past couple of days…instead of:

Widget X

The best widget in the world.

We are now getting:

S-DE

The best widget in the world.

For some reason, the item.item.itemid is now pulling through the Tax Item’s ItemID field!??!

What’s odd is item.item.internalid is giving us the inventory item’s internal ID, and not the Tax Item’s Internal ID!

Anyone got any idea what’s going on?

NetSuite – could you shed some light on it?
This is a cached copy. Click here to see the original post.

[tgrimm]

What record are you working from here? Do you have an issue with Name vs Display Name? What prints out if you use simply item.item?

[michoel]

Advanced HTML/PDF Templates do not properly support accessing linked records like item.item.itemid. Even if it did work, it would probably only give you the correct itemid for the first item, and then just repeat that for the following items.

I would recommend creating a custom Transaction Column Field to source the values you need in the transaction. Make sure ‘Store Value’ is unchecked, and that when you customize the form, the field is checked to be displayed but remove all text from the label to hide it in the UI.

---

EnablingSolutions replied on 07/25/2016, 12:35 PM: Hi Michoel. We ended up doing this, along with a few other fields on the item as we didn’t want this to happen again in the future!

[Marty Zigman]

We solve all these problems with our Content Renderer Engine (CRE). No need to copy data around to overcome NetSuite weaknesses. If you can search it, we can report it. See this article with many linked article references: http://blog.prolecto.com/2015/12/19/…nderer-engine/

---

EnablingSolutions replied on 07/25/2016, 12:38 PM: Hi Marty. Big fan of your blog – always an interesting read!

You and I are going to have to talk in the immediate future about something totally unrelated, but nonetheless NetSuite.

Thanks for your reply, we did get it fixed in the end, but yes, the CRE would have been a much better solution – and certainly not full of SuiteSurprises!

[Author]

Posts