Forum Discussion
JohnnyLundgren
Qrew Member
Hi Paul,
1) If the automation or pipeline is creating the child record, you can add into the automation/pipeline to enter the parent field value in the child field. This way there will be no difference between the two fields as it is copying the value entered in the parent field.
2) If the automation or pipeline doesn't create the child record, check for errors or run conditions that are preventing it from creating the record.
3) You can create a summary field via the relationship back to the parent record. If there is no child record or the values don't match, you can see that on the parent record.
Hope that helps!
------------------------------
Johnny Lundgren
------------------------------
1) If the automation or pipeline is creating the child record, you can add into the automation/pipeline to enter the parent field value in the child field. This way there will be no difference between the two fields as it is copying the value entered in the parent field.
2) If the automation or pipeline doesn't create the child record, check for errors or run conditions that are preventing it from creating the record.
3) You can create a summary field via the relationship back to the parent record. If there is no child record or the values don't match, you can see that on the parent record.
Hope that helps!
------------------------------
Johnny Lundgren
------------------------------
PaulPeterson1
4 years agoQrew Assistant Captain
Johnny,
your logic works fine for the instances where the verification team is able to locate the auto generated ticket. However, that is not the issue. The issue involves orders that the verification team cannot find the auto generated ticket (mainly due to missing data in the order). In those cases there a manual ticket is created and there is no connection to the order, therefore the summary field will not return any results.
------------------------------
Paul Peterson
------------------------------
- JohnnyLundgren4 years agoQrew MemberHi Paul,
the GetFieldValues() function might work for this use case. They are a bit tricky to set up, and I don't have a ton of experience with it yet. Here is the QB documentation https://help.quickbase.com/user-assistance/formula_queries.html
Their samples only use the record id as the query but we have been able to use other unique fields as well.
------------------------------
Johnny Lundgren
------------------------------