Thank you for the latest additional information and rephrasing the requirement. I think I have understood your new requirement.
Bricks_n_Mortar_Cons:
The reason for trying to set source to parent slice rather table is that when I add a new transaction and want to add a new project from the transactions form view I want it to take me to the slice view of Project table (Has filtered columns that i need) rather than the original table.
I believe you can still achieve the intended behavior by having the following setting. Well, additional requirement / constraint means additional logic.
Suvrutt_Gurjar:
Please ensure that your Ref column in the child table is on Parent table only and not on Parent Slice.
Yes, please continue to have your reference column setting on parent table and not on parent table slice. In addition to the 4 steps described above, in the reference column in the child table that references the parent Projects table, please have a valid_if constraint such as below
IF(CONTEXT(“View”)=“Transactions Slice_Form”, SELECT(Projects[Projects Table Key], [Project Status]=“Active”),SELECT(Projects[Projects Table Key], TRUE))
This expression ensures that when you navigate to the Transactions ( Slice) form, only Projects with “Active Status” are available in drop down while selecting project ID ( or name) in your reference column in Transactions (Slice) form.
The relevant images from the test app with similar test setup below,
Interactive Dashboard view. On the left Orders view. It is parent table slice with with open orders. On the right, order details slice view. On the right, only shortlisted child records are there for the selected parent record. Please pay attention to the right hand top corner encircled in red to expand the child slice view.
Expand the child slice view. The following view will appear. Please pay attention to encircled add icon at right hand bottom side.
Click on Add sign. New child table form appears. Please pay attention to encircled Order ID reference column.
Please expand the Order ID column. All tghose order IDs in the drop down are for “Open Orders” only ( Equivalent to “Active” projects in your case)
Basically, while going to parent table from the child table , you will necessarily need to select an existing parent record. The above mentioned addition in logic ensures that when you navigate to select parent record from the child record slice, it restricts the user to only parent record IDs with "Active " status.
Hope this helps.