I’ve done this successfully before but can’t seem to get it to work now. I have a parent table, called Events, and a child table, called EventOverrides. EventOverrides has a column, eventID, which is a ref to the Events table. “Is a part of” is checked.
I made a slice for EventOverrides, called EventOverrides_1. It allows adds/deletes/updates. No row filter condition. (The purpose of this slice is solely to display an inline table without a specific column…it’s to get around the quirk where a showif condition on a column doesn’t hide the column in table view but only the data in it. Anyway…) I added a list column in the parent table, called “Form Overrides”, that mirrors the system-created “Related EventOverrides” column, with the only difference being it points to the slice rather than to the main table. (Formula: REF_ROWS(“EventOverrides”, “eventID”), “Show?” box is checked.) Lastly, I created a ref table view for the slice and added the “Form Overrides” column to the form view for the parent table.
According to my research these are all the steps required to get this to work- and I know I’ve done this successfully in the past- and yet the list doesn’t appear in the form (It should be appearing with a “New” button given that it’s a blank list to start). Anyone know what I’m missing?
Andrew2 is seeking help with an issue where a slice-based list is not appearing in a form view. They have a parent table, Events, and a related child table, EventOverrides. To control the columns displayed in an inline view, they created a slice of the child table called EventOverrides_1. A virtual column was added to the parent table using a REF_ROWS formula pointing to this slice. Despite believing they have followed all the necessary steps, which have worked for them in the past, the inline list with its “New” button fails to appear in the parent table’s form. They are looking for assistance to identify the missing step or potential error in their setup.
The slice must allow adds.
The REF_ROWS() column must be included in the form view.
Post screenshots of the slice configuration, the REF_ROWS() expression, the configuration of its column, and the form view configuration.
However for some reason, the screenshot below shows the REF_ROWS() expression with just EventOverrides and not EventOverrides_1 as highlighted in red in image below.
Also the reference table in the same image is pointing to a different slice ( EO_No Inline Actions) and not the EventsOverrides_1 slice. Please ensure that is correct in overall configuration.
In the working example from a sample app, please see that the reverse reference column expression as well as reference table setting refer to the same slice “'Complete Order Details”
My apologies, the slice is as named in the screenshots. I also updated the REFROWS formula to include the slice name instead of the main table name, as you suggested (see below). However, the issue persists- the “Form Overrides” list still does not appear in the parent table’s form view.
Thank you. You seem to have created a form on the events table “Events Form” as against the system generated forms. Could you confirm the add/ edit actions are navigating to this manually created “Events Form” and not the system generated forms of the Event table where the actions could be navigating?
Confirmed. I removed two columns from the Event Form view, refreshed the app, and saw that they were missing when I click the add button. So yes, the add action is going to the Event Form view as expected, not the system one.
Thank you. Could you confirm you are seeing this “Event Form” name at the " View: " caption as shown below after navigating to the form view in the app editor?
Sorry for reverting late as I was doing some relevant testing. But I could not so far come up with a conclusive root cause analysis.
The IsPartOf option seems to gravitate to the table based system generated reverse reference column rather than a manually created reverse reference column based on a slice. In a way, it appears logical because a slice on a child table may have lesser rows than those associated with its parent, depending on slice expression. Any deletion of parent can leave the related child rows outside the slice orphan.
However there is one sample app where the IsPartOf relationship is working on the slice. Please take a look at the following sample app
Thank you @Suvrutt_Gurjar . I didn’t notice anything different in my setup vs in the app you shared…save for one thing: I noticed that in the app you shared that there were system-generated views for the slice “Open Orders”. I do not have system-generated views for my slice. I didn’t even know the system generates views for slices. I’m also not sure if this is even related to my issue, but I did some research and learned that the system generates a form view when updates are allowed. However, as shown in one of the first screenshots I shared in this thread, my slice does allow updates, yet there is no system view. Again, I’m not sure if this is related to my issue, but it is odd.
