Forum Discussion

KatherineOakey's avatar
KatherineOakey
Qrew Member
5 years ago

Updating a field in a child record based on selecting parent summary value

Not a very good title. Event (parent to Registration) Registration (parent to Ticket) EOTI registers for a specific Event date and creates a Ticket record (working as desired :) ) Now I would...
relationship
DonLarson's avatar
DonLarson
Qrew Elite
5 years ago

Katherine,

Would you draw a picture of the relationships?  I am not following the architecture of the application.



------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------
KatherineOakey's avatar
KatherineOakey
Qrew Member
5 years ago

Event - has unique date/time and associated marketing data.

Registration - one record for every participant in an event including the date/time selected from Event- child of the Event>Registration relationship

Ticket - one record for every participant in an event and includes problem statement.

I've left out a Client table in the initial description.  A Client may have many Tickets, A Client may register for multiple events so actually:

Events -> Clients

Events -> Registrations

Clients -> Registrations

Clients -> Tickets

Registrations -> Tickets

parent -> child (for above reference)

Registrations are driven by an EOTI form that gets the Ticket added and, if needed, a new Client record added.

I would like to allow internal user to select the day of the event (I may be able to use use Today, have to think about that), display a list of all the Tickets specific to this Event (I can do that via a field in Tickets), view the associated problem and, optionally, update that specific Ticket record's solution field.



------------------------------
Katherine Oakey
------------------------------
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    5 years ago

    Do you have these two relationships

    Events -> Registrations

    Registrations -> Tickets

    There for you can lookup the value for the Record ID# of the Event [Related Event] from the Registrations down to Tickets.

    Then create a Report Link field for Tickets on the Event  Table by matching Record ID# on the right with the lookup of [Related Event] (which I suggest called [Record ID# of Event].  That way the Tickets for the Event will be on the Event Record itself.



    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    mark.shnier@gmail.com
    ------------------------------
    • KatherineOakey's avatar
      KatherineOakey
      Qrew Member
      5 years ago

      Yes, I do have those two relationships.

      Thank you!  I'll fuss around with this to make sure I understand it :)

      Also had another thought this morning that I may give a try.



      ------------------------------
      Katherine Oakey
      ------------------------------
      • DonLarson's avatar
        DonLarson
        Qrew Elite
        5 years ago

        Katherine,

        Thanks for the structure, you are in good hands with Mark's advice.



        ------------------------------
        Don Larson
        Paasporter
        Westlake OH
        ------------------------------
    • KatherineOakey's avatar
      KatherineOakey
      Qrew Member
      5 years ago
      What am I missing?

      In the Event table I have added a Report Link to a report in the Ticket table that displays the ticket problem and solution (starting fairly simple).

      In the Registration table I added a field Event Record ID# which is a lookup from Event to Registration (the Reference Field is the Related Event in the Registration table), the Value field is the Record ID from the Events table.

      When I click on the Events table, I see a single row for each event (which I want) plus fields I don't wish to display (and not sure where they are coming from as they aren't in the List All for Events).  I do have a column for Tickets for Specific Events which is the Report Link field.

      When I click on the Report Link column value, I believe I am seeing a report from Registration (which is good because I see the client name) but I don't see the actual report from the Ticket table.

      Still suffering from not completely understanding all the basics :(

      TIA

      ------------------------------
      Katherine Oakey
      ------------------------------
      • KatherineOakey's avatar
        KatherineOakey
        Qrew Member
        5 years ago
        I have had somewhat of an 'a-ha' moment which helps and further confuses :)

        It appears the Report Link points to a table that has fields that may or may not be 'Reportable'.

        When I look at the fields in both Registration and Tickets, there are many default fields that I can't mark as non-Reportable (so I can pare down what columns are seen in both the Registration and Tickets tables when I click on an individual Report Link field from the Events table.  What I see when I am looking at the list of Events is, expected, the RecordID of the Event.

        When I click  on the Tickets for Specific Events value (which is the Report Link field; Record ID# from Events on the left; Event Record ID from Registration on the right), I get the list of registrations for that date (yay!) but more fields than I want to see from both Registration and Ticket tables, but again, more columns than I want to display to the user (and missing the Solution field) and most of these fields are default so I can't make them non-Reportable.

        ------------------------------
        Katherine Oakey
        ------------------------------