I'm not sure what exactly you were asking, and no one else seems around to answer, so here's an answer to a commonly asked question:
If you get only one .Gotvalue event block per FireBaseDB component, how do you
decide what the data is and how to deal with it?
The answer (just tested by me) is to make extra copies of your
FireBaseDB component with the same attributes, but different
component names to remind you which piece(s) of data and which contexts they handle.
In the attached example, I used separate components for customer email and customer
phone requests (a very small grained choice, I admit) with extended tags built up with JOINs
to keep the data separate in the database.
Notice how I request both email and phone in the last button, and
their arriving values magically are handled separately by different event blocks.
If I were working with only one FireBaseDB component, I would have had to add
extra blocks in the .GotData event to examine the incoming tag and route the value
to the proper GUI .Text field.
Another note about tag design:
Using '/' in a tag breaks the tag list off at the first / level.
So keep your customer list separately, and don't
expect to gather it from a taglist.
Other designs might change the bucket on the fly, but I am not experienced in that.
Does this answer your question?
ABG