Hello @Chris_DeAngelis,
Although I agree with @Pablo_DV that sometimes we need to struggle a bit to learn, I think that’s not the case here. Your use case isn’t the default behavior, and it requires some workarounds to make it function properly.
I haven’t tested your specific use case, and I don’t have much time to create a doc, so it’s always easier to help if you share a dummy doc that demonstrates the behavior along with an explanation of what you’re trying to achieve.
Here are a few points regarding your use case:
-
Are you trying to have a calculated column that updates as soon as you select the project field in a form?
-
Is your selection column a list of texts? For example, in the options formula, are you using something like:
PROJECTDB.ForEach(Concatenate(currentValue.Name, " - ", currentValue.Desc))
-
Are you using the native form or a published/embedded form? If you’re using a published/embedded form (accessible via a public URL), access to the doc’s data may be restricted. Try adding the same form inside the doc (using
/form
on any page) and see if the issue persists.
Possible Causes and Solutions
- If it works in an in-doc form: The problem likely lies in how the data is being accessed. My initial thought is that the form table is not linked to the PROJECTDB table through a relation column, or you haven’t activated the “Include reference tables” option in the form settings.
- If it doesn’t work in an in-doc form: Then the issue is likely with a formula or filter in your setup.
Additional Resources
Check out my two posts about forms; they include some useful tricks:
- Tips when using forms: Validation - Showcase / Tips and Hacks - Coda Maker Community
- Tips when using forms: Style and Filtering - Showcase - Coda Maker Community
Let me know if this helps!
Best regards
Arnhold