Pipelines | unique | list
Hello,
I have a parent table and a child table I am working with.
The parent table has a field called [CList Master (Pipeline generated)]
The child table has a field called [Clist current page...
Forum Discussion
I just tested the summary combined text relationship field called [Combined Text Clist current page] (viewable in screenshot above). I assumed it had a max amount of 20 for some reason, but after testing it doesn't seem to have a limit? If this is accurate, maybe it would be easier to create a formula field and have it list out all unique values from this [Combined Text Clist current page] on the parent table? Just a thought
------------------------------
Shane Miller
------------------------------
Are you just trying to combine the list of clist entries into a combined string? Or do you need to parse out uniqueness within it as well. The summary combined text list field is not capped at 20 - I believe it does cap out somewhere over 100 but I forget the exact limit. If you have concerns with that cap, you can use formula queries instead which do not have a the same limitation and will typically show all entries without any cap.
------------------------------
Chayce Duncan
------------------------------
Hey Chayce,
Thank you for responding. The child records may go over 100, so I was trying to create a "fool proof" system using pipelines. Essentially, I am trying to create a clist for an embedded report so that the embedded report only shows columns which have data in the child records. Formula queries may work at first, but I expect hundreds of thousands of records on the child table, so I don't think it will be efficient long term.
Does that make sense?
As an example:
child record ID 1 may say: [Clist current page] = 1.5.17.34child record ID 2 may say: [Clist current page] = 5.18.34
I would need a field on the parent table to then show the values: 1.5.17.18.34Samuel Trachy gave me the idea during one of the office hours. He helped me get the embedded report working with a clist, and then recommended making a dynamic field which houses the unique clist on the parent table
------------------------------
Shane Miller
------------------------------- MarkShnier__You
Qrew Legend
The limit is 150 unique children rolled up to a combined text field.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------ If it were me - I would make a Pipeline that instead of trying to combine the clists into the parent record via PIpeline, I would instead make a Pipeline or webhook that would break the clist in your child into a different child table to break out each field into it's components. So if you child record has a Clist of 1.5.17.34 - I would make a child table under it and create 4 records with a single field of FID and each record having the value:
Record 1: FID 1
Record 2: FID 5
Record 3: FID 17
Record 4: FID 34
Your other option could be instead of entering the clist as a string - just enter the clist into a grid edit and enter each field as it's own row.
The reason I say that - is you can then relate these records directly back to the original parent and use the summary combined text to summarize all of those FID records.
------------------------------
Chayce Duncan
------------------------------That's an interesting thought. Makes sense since the summary field wouldn't duplicate values on the parent table. My brain is having a hard time figuring out how it would take the [Clist current page] and parse out the values to capture 1.5.17.34 on all separate records. Or would this have to be jinja2 saying if this field is not null, then FieldID
------------------------------
Shane Miller
------------------------------
