conditional dropdown
Hi, I'm trying to utilize conditional dropdowns and running into an issue that I can't figure out. Here's the relationships: Project Management App has Projects. Each Project has many Sign Typ...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendIs that field in your screen shot for Record D#2 visible on the form? Is there a value in it?
When you have a CDD the field on which the drop down is conditioned must be on the form, even if hidden by a form rule. But while you are on debug mode, make it visible and see what's in that field.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
When you have a CDD the field on which the drop down is conditioned must be on the form, even if hidden by a form rule. But while you are on debug mode, make it visible and see what's in that field.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Blank. I thought about it more, and the problem is that when the Production Task is created, there are no "Related" PT Chains created, even though Grid Edit is allowing me to enter some. It's a chicken-egg thing.
Unless I'm overthinking this?
If I could use Dynamic Form Rules to populate something on PT Chains (displayed via Grid Edit), that would work. I don't think you can, though.
I created an Automation that when a Prod Task is created, it created 10 blank PT Chains. This works. There's then 10 entries where someone can associate a PT to a ST. It's messy but I cannot think of any other way. A nightly Cron can clean up the "blank" entries to limit the junk.
It makes sense but I wish QB would allow for a non-IOL solution here. I couldn't think how to do this with Pipelines, either.
Unless there is some way to use a multi-select here? I tried that before but that didn't work. I was trying to do a summary combined text into one using some Formulas, but its not limited to the scope of the specific project, so all Sign Types were showing.
Any other ideas?
------------------------------
Andrew Ryder
------------------------------
Unless I'm overthinking this?
If I could use Dynamic Form Rules to populate something on PT Chains (displayed via Grid Edit), that would work. I don't think you can, though.
I created an Automation that when a Prod Task is created, it created 10 blank PT Chains. This works. There's then 10 entries where someone can associate a PT to a ST. It's messy but I cannot think of any other way. A nightly Cron can clean up the "blank" entries to limit the junk.
It makes sense but I wish QB would allow for a non-IOL solution here. I couldn't think how to do this with Pipelines, either.
Unless there is some way to use a multi-select here? I tried that before but that didn't work. I was trying to do a summary combined text into one using some Formulas, but its not limited to the scope of the specific project, so all Sign Types were showing.
Any other ideas?
------------------------------
Andrew Ryder
------------------------------