This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
I have encountered an contradictory issue wherein two schemas which are topologically identical are treated differently; one works fine and the other throws a circular reference error.
I have distilled the issue into a very simple example base. Here...
I have a column of linked records. I would like to make a second column that filters those linked records based on a condition.
Example:
Table 1 Column A is a checkboxTable 2 Column A links to records of People that are associated with the BusinessT...
This is a great solution to the OP’s problem! Any progress towards new integrated functions that would simplify things?
Specifically it would be nice to be able to differentiate beyond the MAX and MIN records. For my work I need to be able to index...
Bumping this issue as it seems to be an inconsistency in the product design and should be addressed one way or another.
Here’s a look at the schema for the two scenarios.
Using two tables, the schema does not cause a circular reference
However, I ca...
Hi Kuovonne, thanks for the answer. Rather than doing a rollup, I was trying to maintain a link from the second table to a subset of the records from the first. After further thought I realize that this doesn’t quite make sense in the existing para...
