Unanswered

Saving two records at once via Patch

(0) Share

Report

Posted on by PA-Unicorn

Hello!

I need some direction please? I have a Patch function that is saving a record to a SQL table successfully. I have been asked to create two records at once for employees who will be swapping job positions. So, one employee who was working as a teacher with a similar job description will be trading places with another. I need to save employee ID, F,M,L name, Location, etc. This will be two brand new records that I am capturing the data for through LookUps across multiple screens. What would be the best approach to accomplish this? Bonus points for working examples. 🙂

Set(VarReturn, Patch(
DataSource,
Defaults(DataSource),
{
TransEmpID: dcEmpID_1.Text,
Location: lblddlLocationFilterSelection.Text,
LocationNumber: lblEmpLocationCode.Text,
TransEmpFName: dcFName_2.Text,
TransEmpMName: dcMInitial_2.Text,
TransEmpLName: dcLName_1.Text,
TransEmpEmail: dcEmail_1.Text,
EmpBargUnit: txtBU_1.Text,
EffectiveDate: dcEffDate_4.SelectedDate,
TransToPosNum: Proper(ddlJobDesc_2.Selected.pmpc_position),
TransToJobDesc: Proper(ddlJobDesc_2.Selected.prjb_long),
PASubmittedForReplacedEmp: rdoPAAlreadySubmitted.Selected.Value,
ReasonForChange: ddlPAReason_1.Selected.Value,
PANotes: dcNotes_4.Text,
ManagerEmail: lblHMEmail.Text,
ApprovalStatus: lblApproval_Status_1.Text,
TransFullName: txtfullname_1.Text,
TransEmpMstrCurrentJobNo: lblCurrentPosNum.Text,
TransEmpMstrCurrentJob: txtEmpMstrJob_1.Text,
PATimeStamp: Now()
}
) );

VarReturn.ID; <--Using to upload files to SharePoint with employee Metadata in next screen.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

StalinPonnusamy Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @PA-Unicorn

In this case, we have 2 options

1. Create another record once the current record is saved using PowerApps
2. Have Power Automate to create another record based on this record creation

#1. Save 2 records one after other
Set(VarReturn, Patch( DataSource, Defaults(DataSource), { TransEmpID: dcEmpID_1.Text, Location: lblddlLocationFilterSelection.Text, LocationNumber: lblEmpLocationCode.Text, TransEmpFName: dcFName_2.Text, TransEmpMName: dcMInitial_2.Text, TransEmpLName: dcLName_1.Text, TransEmpEmail: dcEmail_1.Text, EmpBargUnit: txtBU_1.Text, EffectiveDate: dcEffDate_4.SelectedDate, TransToPosNum: Proper(ddlJobDesc_2.Selected.pmpc_position), TransToJobDesc: Proper(ddlJobDesc_2.Selected.prjb_long), PASubmittedForReplacedEmp: rdoPAAlreadySubmitted.Selected.Value, ReasonForChange: ddlPAReason_1.Selected.Value, PANotes: dcNotes_4.Text, ManagerEmail: lblHMEmail.Text, ApprovalStatus: lblApproval_Status_1.Text, TransFullName: txtfullname_1.Text, TransEmpMstrCurrentJobNo: lblCurrentPosNum.Text, TransEmpMstrCurrentJob: txtEmpMstrJob_1.Text, PATimeStamp: Now() } ) ); //Patch or Create Another record Patch( DataSource2, Defaults(DataSource2), { } )

#2
Create Power Automate to create another record.
Type: Automated Cloud Flow
Trigger: When an item is created

Thanks,
Stalin - Learn To Illuminate

Was this reply helpful? Yes No
PA-Unicorn 8 on at

Like
a
(0)

Report
Copy link

Link copied!

I am just starting to learn PowerAutomate. I will play around with option one as the learning curve shouldn’t prove as steep for me.

Just so I am clear, excluding employee specific metadata, the job description values for employee one will become the values for employee two and vise versa.

I am currently retrieving via lookup the job info for employee two and saving these values for employee one in my patch function. These save to a different table then where the data is being read from. I will now need to perform a lookup up on employee one so I can save those data for employee two since employee one is swapping jobs with employee two.

Was this reply helpful? Yes No