Power Platform Community Forum Thread Details

Hello -

I am building a multi-screen form in PowerApps. The form has 9 screens, but the user will never visit all 9 screens - the screens they are directed to are based on a form response on the 2nd screen. Here is a listing of the screens:

Screenshot of InterviewRequestInfo Screen:

Here is a listing of possible user experience paths:

1) HomeScreen>InterviewRequestInfo (Who will be scheduling the interviews? Item "I need Recruiter/TAA assistance" selected)>ScreenScheduleRecTAAAsst>LIFEValuesPanel (Submitting form updates to Sharepoint occurs here)>Thank you Rec TAA Int Sched

2) HomeScreen>InterviewRequestInfo (Who will be scheduling the interviews? Item "My Admin or Team Member will assist" selected)>ScreenScheduleAdminTeamMember1>LIFEValuesPanel (Submitting form updates to Sharepoint occurs here>Thank you Rec TAA Int Sched

3) HomeScreen>InterviewRequestInfo (Who will be scheduling the interviews? Item "I will be scheduling the interview(s)" selected)>I will schedule on own (Submitting form updates to Sharepoint occurs here)>Thank you already scheduled

4) HomeScreen>InterviewRequestInfo (Who will be scheduling the interviews? Item "I have already scheduled the interview(s)" selected)>Already Scheduled Screen (Submitting form updates to Sharepoint occurs here)>Thank you already scheduled

I duplicated the ScreenScheduleRecTAAAsst to create the ScreenScheduleAdminTeamMember1 screen.

Screenshot of ScreenScheduleRecTAAAsst:

Screenshot of ScreenScheduleAdminTeamMember1:

The issue is coming with the upload of form responses to Sharepoint...User Experience 1 is working fine, but User Experience 2 is missing the following fields:

1. Who Manages your Schedule?

2. Scheduling Callouts

3. Email of Admin/Team Member

Screenshots are below for reference (see the yellow highlighted areas, sorry it is so small...):

Finally, a list of properties for each, which I've double checked against each other to see if I could spot the difference:

ScreenScheduleRecTAAAsst (this is working):

Tree Diagram

Screen Properties:

OnVisible:

UpdateContext({varSelectedLoc:Blank(),VarSelectedPerson2:Blank()});ResetForm(ScheduleTAAAsstForm)

Form Properties:

Name of Admin and/or Team Member Data Card Properties:

Name of Admin and/or Team Member Gallery (SchedMgrGal) Properties:

Name of Admin and/or Team Member Data Card Value Properties:

Email of Admin/Team Member Data Card Properties:

Email of Admin/Team Member Data Card Value Properties:

Scheduling Callouts DataCard Properties:

Scheduling Callouts Value properties:

Advance Button Properties:

ScreenScheduleAdminTeamMember1 (this is not working):

Tree Diagram:

Screen Properties:

OnVisible:

UpdateContext({varSelectedLoc:Blank(),VarSelectedPerson3:Blank()});ResetForm(ScheduleAdminTeamMemberForm)

ScheduleAdminTeamMemberForm Form Properties:

Name of Admin and/or Team Member...Data Card Properties:

SchedMgrGal_2 Properties:

Name of Admin or Team Member Data Card Value Properties:

Email of Admin/Team Member Data Card Properties:

Email of Admin/Team Member Data Card Value Properties:

Scheduling Callouts Data Card Properties:

Scheduling Callouts DataCardValue Properties:

Advance to Next Screen Button Properties:

And Finally - the Submit Interview Sched Info_1 on the LIFEValuesPanel Screen:

Tree Diagram:

Submit Interview Sched Info_1 Button Properties:

OnSelect:

Patch('Diversity Panel Reporting List for Power Apps',Defaults('Diversity Panel Reporting List for Power Apps'),LIFEValuesForm.Updates,'JobReqID Form'.Updates,InterviewReqInfoForm.Updates,ScheduleAdminTeamMemberForm.Updates,ScheduleTAAAsstForm.Updates);

Clear(colLIFEValData);

NewForm('JobReqID Form');

NewForm(InterviewReqInfoForm);

NewForm(ScheduleTAAAsstForm);

NewForm(ScheduleAdminTeamMemberForm);

NewForm(LIFEValuesForm);

Notify("Form Submitted",NotificationType.Success);Navigate('Thank you Rec TAA Int Sched')

Thank you for reading through this incredibly long message, and please let me know if you can help me troubleshoot (or need any more information for troubleshooting). Thank you!