picklist options as source for subquery field issue

  • 1
  • Problem
  • Updated 3 years ago
  • Acknowledged
Photo of mB Pat Vachon

mB Pat Vachon, Champion

  • 42,714 Points 20k badge 2x thumb

Posted 4 years ago

  • 1
Photo of Greg Jarrett

Greg Jarrett

  • 3,496 Points 3k badge 2x thumb
Hey Pat, I'm not getting any audio on the video either in Youtube or embedded in the skuid community here. I can definitely get audio on your other videos and my PC isn't muted (checked that twice!). Is there definitely audio on this video?
Photo of Pablo Martinez

Pablo Martinez

  • 2,468 Points 2k badge 2x thumb
no audio for me either 
Photo of mB Pat Vachon

mB Pat Vachon, Champion

  • 42,714 Points 20k badge 2x thumb
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
Pat.  You are correct,  you cannot use field metadata to derive your filter source if your working with a subquery condition.  I will take your note as an Idea and put it in our backlog. 

However you can make your filter source be the rows of another model,  which aggregates the rows of the child object, grouping by the picklist.   This is the model described in use case 7 of this document
Photo of mB Pat Vachon

mB Pat Vachon, Champion

  • 42,714 Points 20k badge 2x thumb
Hi Rob,

I'm not able to this in my case. The values required in the filter are the values from the picklist. Each of these values need to be present in at least one record for it to show in the model. It's unlikely to happen, but it could and then the filter list values would be incomplete.

So, instead of this, I've created a manual source list that is full proof so long as the picklist values are in sync with the manual source values.

Pat
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
Yup.  That's the solution at this point.