I am having trouble displaying choices of List Field in Parent table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2024 04:35 PM - edited 05-10-2024 09:07 PM
I have a table that extends another table. On the extended table, I have a list field called Relationship, whose choices appear as below.
On the parent table, it appears like this:
Is there any easy fix to get these choices to show up in the parent table? Thanks.
Additional Information about setup:
I did not create Relationship on the parent table. I'm not supposed to create new fields on the parent table. There is a one to one relationship between the tables and I was able to have the relationship field appear on the parent table through form layout.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2024 01:10 PM
Hi @AM24,
Can you share a screenshot of how the dictionary/field is configured with the choices?
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2024 02:04 PM
Hey James, thanks for the response. So this is how the field is set up. It is set up in the child table Table2.
I've tried setting up the choices like this:
I've also tried setting it like this:
u_table2_ref is the reference field on the parent table (Table1) to Table2 (the child table). There is a one to one relationship between the tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2024 02:38 PM
Hi @AM24,
Okay, I am now a bit confused, maybe I misunderstood your question.
I thought Table 2 extended Table 1 and the relationship field was created on Table 1.
But from your screenshot, it appears that it's created on Table 2 instead.
Does that mean the relationship field on Table 1 is actually dot-walked? i.e. u_table2_ref.u_relationship
Can you please elaborate on what you are trying to do here? What is the goal/purpose of this requirement?
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2024 05:44 PM
Yeah I probably did a poor job of explaining it.
Yes you are correct. The relationship field on Table 1 is dot-walked. Our company wants to avoid creating fields on Table 1, because of certain issues. That's why almost all new fields, including this one, are created on Table 2. However, Table 1 is still being used for the display. I am able to get the choices to show up on Table 2, but cannot get it to show up on Table 1. I was trying to figure out if there was a way to achieve this. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2024 06:27 PM
If Table 2 is extended from Table 1, so you can add fields to Table 2 and not Table 1, it will include Table1's fields. But you need to view Table 2 to see the choice field on that table as it doesn't exist on Table 1. Your design seems off if users won't view Table 2. Adding a referenced field on Table 1 to Table2 will allow dot-walking when viewing Table 1. But you don't want to add a field to Table 1. Maybe James has a solution.