Hi Team (Alex),
I'm hoping your can work your magic for me again. My form is working great, but Management has asked for a new feature, the ability to cancel an entry.
I can pull all the information back into the form using a Primary Key, but when I try to pull the value of the Smart Dropdown back into the field it won't show the data.
This is what I'm using: Seat1=[entry.PrimaryKeyReference.Seat1.Seat] Where Seat1 is the Smart Dropdown field on the form, and Seat is the column in the referenced form.
For all the other fields this works as expected: Date1=[entry.PrimaryKeyReference.Date1] for example pulls the original date submitted for the selected PrimaryKeyReference.
As always, any guidance is appreciated.
With or without the ".Seat" the field doesn't populate.
The part of the form I'm working with is a seat booking form.
People can select the Date, Location, and Pod, and based on those selections the Smart Dropdown filters to a reduced list for the requester to select a seat.
Once that is done, Management has asked that there be functionality to cancel the entries.
So using the reference number generated on creation, the requester can pull their record up and select to cancel it.
The form is fine pulling up the record details for the Date, Location, and Pod, but it can't seem to pull back the Seat selected.
Hope that helps you understand my question.
Thank you for your attempt explaining!
What I am after is to understand what is "PrimaryKeyReference" and what is "PrimaryKeyReference.Seat1" and what is "Seat1"
This is what I mean saying about data model... Knowing something about " Date, Location, and Pod" is not really relevant here, as these are missing in the expression you have and add more noise than help...
Okay, PrimaryKeyReference is a smart dropdown referencing the Autonumber that is generated with each request on the form. So if I submit a seat booking I get a confirmation number VRTO-#. I can then use that number to look up my request and cancel it if necessary.
Seat1 references the seat I have selected when booking. Seat1 is the field name for the smart dropdown that references a secondary form that lists all the available seats.
Hope that helps, and thank you for all your help.
So, in the form that is referenced through the "PrimaryKeyReference" field you dont have a "Seat1" field?
It is even more complicated now...
Let's start from the initial question - you are using Seat1=[entry.PrimaryKeyReference.Seat1.Seat]
which means you want to get a "Seat1" through the field "PrimaryKeyReference". Navigating to it through this field to the source form (configured for your smart field). Which means you assume you have a field "Seat1" in that form... do you?
Yes, the main form (that PrimaryKeyReference is referencing) has the field Seat1. That field is a smart dropdown field that is referencing the field "Seat" in the secondary form.
When a user first goes to the main form, Seat1 is chosen from the values in the secondary form as listed in the field Seat.
When a user needs to cancel an entry in the main form I need Seat1 to pull the value from the referenced entry in the main form, but (and this is the tricky part), Seat1 still needs to be connected to the secondary form so it can update that form with the cancellation (as you showed me how to do in another question - Thank you again for that).
I know, so confusing. Feel free to tell me it can't be done.
Oh, could you provide some visuals?
Is it so that "PrimaryKeyReference" field references the SAME form (I mean "linked to itself")? This is confusing - I just dont get where you have Seat1 and Seat and how this things are connected together.
Is it so that PrimaryKeyReference and Seat1 are connected to the same form?
Do you have 3 forms or 2? Could you tell or show what fields and their types has each form?
Hopefully this looks the same on your side as mine.
Picture One: Form One where users book or cancel their seats.
Picture Two: Form One in Edit mode
The red column is the Seat column with fields Seat1 through Seat5. These fields are smart dropdowns that reference the second form.
Picture Three: Form Two Smart Dropdown Database:
When users select the Date, Location, and Pod in the first form it filters the list of available seats in this form/database (field Seat). When they hit submit in the first form it updates this form to show the seat is booked and generates an email with the auto number generated reference number.
For the Cancellation piece, I want to use the the reference number from Form One to pull up the information booked (Date, Location, Pod, and Seat (field Seat1)), so the user can choose to cancel their booking.
Right now though, the rule to pull back the information from the saved data in Form One isn't pulling back the corresponding seat.
Hope that helps clear things up.
Happy New Year, everybody! What better way to kick off 2022 than with a new Marketplace Partner Spotlight ✨ This month, we're getting to know Daniel Franz, co-founder of Fine Software. Fine Software ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events