How is it that you can’t select a Gig? Watch the video again from about 8 minutes or so. I show exactly how to get a Thing from the RG (in the video it is of type “Favorite Thing”, but for YOU, that’s your “Gig”) and operate on it in a popup. (And then I go on to show some fancier stuff.)
[Aside: Is your RG… perhaps… NOT full of Gigs? Is it… perhaps… full of UNIQUE ID’s OF GIGS? That’s where you are going wrong. An RG is an element for displaying Things. They can be used to display primitives, but this is not something that one will regularly do. You send the RG a list of THINGS. Not a Thing’s something (like, say, Thing’s unique ID). You send it the Thing itself. And then, the elements WITHIN the cell of the RG are used to show various aspects (properties) of the Thing.
If you do not start with an RG that contains Things, what I show in the video WILL NEVER WORK. This is supposed to be obvious from my video and I do not dwell on this point, but one reason I made this video and start from scratch is that it’s easier [and probably nicer] to simply show how its done and let people come to their own “oh, I’m a goofball” moments, as opposed to me screaming at the viewer. ]
Now, my example popup is going to delete the Favorite Thing. But for you, the user is going to make an Offer on the Gig. Same damn thing. These scenarios are only different in terms of what you do after the user clicks “OK” (for you, “Make Offer”).
Your button says “MAKE OFFER”. And, in fact, that’s EXACTLY what your workflow is going to do: You are going to Make (Create) a New Offer! It’s that simple.
So do that. Caveat:
Now, there IS a huge – HUGE – UUUUUUGE – problem with your Offer data type. (Which I hope you have now already realized.)
I see that it thinks that a Gig is a text. That is NOT CORRECT. A Gig is a Gig. The Gig field on your Offer should be of type Gig.
When you create this new offer, DO NOT try to populate the Gig field with a text. (I know what you’re thinking: “I need to store the Gig’s unique ID.” WRONG. You need to store the Gig itself. So do that.)
Secondarily, there’s another problem: It seems to me that your data model is Gig-centric and that, in fact, an Offer doesn’t need a Gig field. A Gig needs an field that should contain a LIST of Offers. Instead of populating a Gig field on Offer, you should consider creating an Offer and then (step 2 in your workflow) attach that Offer to the Gig’s list of Offers.
In this case, Gigs should have a field of type OfferS (note plural). That field should be of type Offer, but it should ALSO be a list (check the list box).
So after creating the Offer, you Make Changes to the Gig (what Gig? this popup’s Gig). The field you change would be “Offers”. That field is a LIST, so you ADD the Offer to the list of Offers. (You’ll see this in the Make Changes dialog.) The Offer you will add is “Results of Step 1”, which will be the Offer object your workflow just created.