i have an invoice advanced PDF and in the list of ...
# advancedpdf
a
i have an invoice advanced PDF and in the list of items, i'm joining to a custom field on the item record using "item.item.custitem_customfield". this seems to work to source it in... but for some reason it's printing the value from the first item in the list for every item, even though other items have a different value. has anyone seen this before/know if there's a fix for it? i don't think that my list is broken as other values are accurate for each line, not sure if it's just a limitation of joining to the item record or something?
m
I came here to ask the same thing
I feel like this used to work for me but maybe I'm imagining
nvm confirmed limitation
workaround is to create a custom transaction line field yuck
3 custom fields later and I'm back in business 🤣
r
Hi Amy/Merik, i'm having the same issue. Is the creation of a custom transaction line field the only solution/workaround for this problem?
@Merik Ducker where or how did you create the custom transaction line?
m
Hey Robert - assuming you need to join to Item fields for more than just the first line, then yes, you'll need the custom fields. You can make em from Customization > Lists, Records, & Fields, Transaction Column Fields > New. On the Sourcing & Filtering subtab, use Item as your Source List, then select whichever field you'll need in the Source From. You can also make the fields Hidden on the Display subtab using the Display Type field
a
thanks for confirming, @Merik Ducker! i was also able to apply this to existing invoices by using store value = false, which is usually my hesitation to add a new sourced field since it won't populate on existing records. i'm still gonna meet w/ NS support and see if they'll log a defect because it would be nice to be able to do the join, but this works for now.
âž• 1
r
@amy i added the transactioin fields but am seeing that for existing records it comes back null. your statement above if i understand it correctly is that for existing records it doesn't populate them? is there a way around that if that is true?
a
yeah, i had to set store value = false on the custom field in order for it to populate on existing records. setting store value = false also has other implications though (isn't always accessible in reports; will auto-update anytime the source data updates) so YMMV as to whether that works for your needs.
r
Thank you both! I'm set with this setup.