Currently when you create a new custom object, you need to give a single line text name which you then have to include in the association table view card, however what is populated in this field is often meaningless for us as we are essentially associating two objects and adding additional information - so the suggestion is to create a new association object that links two existing objects together and doesn’t have a completely separate naming convention presented to our users (I understand there would still need to be a table name behind the scenes). These linking tables would not be available in the main navigation, but could be accessed from either of the associated records.
For example if we have a company involved in the deal we might want to add in fields related to that companies involvement in the particular deal - what % of the deal they are involved in, the date they became involved, comments about their role in the deal etc.
So on the deal card we want a table with the company name and the additional fields from the new association object that we have populated - ideally the company name would let us click through to the relevant company record
Another example would be if you are on the company page we want to create an association between the company and each product we have and then add additional information about the products fit for that particular company, the date when it would be good to discuss the product with them again etc. In this case we would want an association record between Product and Company, and the Product name would be the key piece of information we would want to display on the association card on the company screen + the additional fields
At the moment I am finding I have to work around this with workflows to add names to new records created so that the display name is then meaningful for our users