This topic contains 3 replies, has 0 voices, and was last updated by michoel 9 years, 1 month ago.
-
AuthorPosts
-
October 11, 2015 at 5:39 pm #2110
sneyCan anyone advise how to get an item record’s Display Name to show in an item list on an Advanced PDF/HTML layout?
${item.item} shows the regular item Name, but we sometimes use a different Display Name that is printed on estimates and invoices to customers. Using the older HTML or PDF layouts the Display Name is always shown (if that field is populated on the item record).
While on this subject, I assume we’ll run into the same issue when we customise the Purchase Order template – we will need to reference the Vendor Name as we sometimes use different names for raising POs to vendors to what we use internally.
This is in a list ( ). I’m guessing I can’t reference the item’s Display Name using ${item.displayname} because the Display Name is not actually stored on the form – so I have also tried ${item[n].displayname} and {record.item[n].displayname} with no luck – I either get an error when saving or nothing in the output.
Any help appreciated!
Cheers
This is a cached copy. Click here to see the original post. -
October 11, 2015 at 10:49 pm #2111
michoelAdd the the field to the form as a Custom ‘Transaction Column Field’ (make sure ‘Store Value’ is unchecked, and in the Sourcing & Filtering tab, source from the Item record).
If you don’t want the field to show in the UI, I saw a great tip on the forums recently – you can hide the field by removing a label on the form (under Customize Form -> Screen Fields -> Columns), though make sure that the ‘Show’ checkbox is left enabled.
-
October 11, 2015 at 11:03 pm #2112
sneyThat did it! Genius
So what I gather from this is that although we can source fields from related records linked in BODY fields, in a SUBLIST you can only refer to fields on the form?
Also wondering why in this instance not storing the value in the field is important?
I did know about the trick to hide a field by removing it’s label but leaving ‘Show’ checked – figured that out the hard way when we wanted a lot of custom fields to be scriptable but invisible to the user.
Thanks again! I am creating very complex forms and seem to keep running into odd things like this – will surely post more questions
-
October 11, 2015 at 11:19 pm #2113
michoelI believe that for sublists you have to have the fields on the form. If you try the syntax {item.item.displayname} you will probably see that it will source the first line in the sublist each time.
It should still work if you store the value but this will take up space in your database for no reason, and also if the display name on the item record changes it will not update on the transaction records.
-
AuthorPosts
You must be logged in to reply to this topic.