Hello Community Leaders!!
Are there any rules to follow while selecting the display value of a table to show up in reference and list fields?
I'm asking this because, we have a table with a string field as it's display value. Sometime later, the client decided its length of that field needs to be 1000 instead of the default 40. But we never changed the display value of the table and it never caused problems until now. There's one record with that field's value length of 135. Now, we've observed that when that record is selected in a list field, it's working fine. But if we create a template from it, the reference to that record is being removed while the other references stay.
I was able to reproduce this in my personal instance as well. But I couldn't find any documentation or any existing problem related to this, nor did I find any similar issues reported in community.
I was hoping I might get an answer here. Now, I've suggested to the client that we make another field of shorter length as the display value, which works in this case, and also generally in a user experience point of view. But I can't help but wonder why this should even occur.
Please see below screenshots of my personal instance replicating the issue.
Thanks for the reply ctomasi! The length of the list field is 4000. And it worked fine when the display field was of length 40.
And using long fields is recommended? But that is exactly what's causing the problem. Multiple references to records with shorter display value were captured fine, it's only the ones that have lengthy display value that are being removed from the template - like shown in the pictured above.
I tested again referencing multiple records and created a template and it worked fine. Please see screenshots below.
