Write to New Screen and Different SQL Table

[TesDA]

I'm looking for resources or sites that could walk me through how to handle the situation I'll describe below. My searches came up without anything which is probably due to the wrong terminology.  My SQL tables are already setup to write correctly from the app

I have two screens:

Screen 1 - Writes to SQL Table General_Requests, primary key ID (auto increment)

Screen 2 - Writes to SQL Table Employee_Requests, primary key ID_Emp (also has ID to join back to General_Requests)

The requester fills out screen 1 about the request and then screen 2, to specifiy which employees they would like on their project.

When the requester moves from screen 1 to screen 2 - screen 2 should write the ID from screen 1 into the Employee_Requests table.

[RandyHayes · Accepted solution]

@TesDA 

Can you supply a bit more information about your application (galleries, forms, controls, formulas, etc) that might be helpful?

In general, if you are using a Form on screen 1 (let's call it Form1) and then need information from that form, you can use the LastSubmit property of the form.  More info on that can be found in the documentation.

So, on screen 2, you can use the Form1.LastSubmit.yourIdField to get that information.  Obviously, replace yourIdField with the name of your Id field you want to use.

I hope this is helpful for you.

[TesDA]

@RandyHayes 

Let me know if you need anything else...

I'm working on a canvas app that uses forms, so far on Screen 1 I have:

ICWO_Entry_Form -> Form

3 DropDowns - Most using a selection from another table in SQL Server

I've attached a snapshot

[RandyHayes]

@TesDA 

That is all fine, and the suggestion remains as before - you can get to the ID of the form submitted in Screen 1 by referencing the ICWO_Entry_Form.LastSubmitted.ID value.

But, I dont' believe that Screen1 is your issue - you had said you needed this information on the screen2.?

[TesDA]

Yes, so Screen 2 would just be information about the employees the requester would like to request for their project (Employee ID, etc). This would write to a different table then Screen 1 (the employee request table). The foreign key of ID would still need to be the same as the primary key on Screen 1 so that the two can be joined (general information to foreign key). I havent started this screen yet.

[RandyHayes]

@TesDA 

Okay, so if you are making screen 2 as an EditForm, then for the datacard that needs the ID of the first table, you can set its default to ICWO_Entry_Form.LastSubmitted.ID

You'll need to flush out the logic for that screen first to determine when and if you want that value to be included.

Considerations like : If the form will be used for View as well as Edit (exisitng records), then you'll need to account for using the previous form value or the stored value.