@faithdwn I think I understood, but I didn't want to assume.
Here is the formula what we are working with from your posting:
If(DataCardValue64.Selected.Value="Completed",
Remove(ClosedPIVTickets,
First(
Filter(ClosedPIVTickets,SERIAL_x0020_NUMBER_x0020_CONFIR=SelectedTicket.Column_x0020_Number_x002f_Locati)
)
)
);
Navigate([@ConfirmSubmitScreen],ScreenTransition.None)
But, in your picture it is quite something different:
SubmitForm(EditTicketForm);
Set(RunFlow,true);
AddColumns(PIVRequests, "Barcode_x0020_Title", DataCard2.Default);
Navigate([@ConfirmSubmitScreen],None) …(cuts off from there)
So which is it? Let's at least get to where the trouble is you're having in a formula.
But, baring that, I'm going to take a step back and look at your theory.
I have already updated the edit form with the lookup function. Now, in order to have that value carry into the datasource, what formula would I need to use on the Submit OnSelect property?-View picture below to see what I currently have.
If you're dealing with an EditForm, your submit action should be SubmitForm(myEditForm). You've already established a datasource for the Form and given it an Item to work with, so it has all it needs.
Furthermore, I would like that form to submit to two different sources under a specific condition.
I have two SPLists: PIVRequests and ClosedPIVTickets. The form submits to PIVRequests. I would like for that same form to submit to ClosedPIVTickets with the same exact columns as PIVRequests only if one of my datacard values dropdown is selected. Therefore i only want ClosedPIVTickets SPList to display all Complete requests while PIVRequests SPList submits all open requests.
This is not going to happen with the SubmitForm. Even if the fields/columns of one DataSource are exactly like another, you can't just switch the sources around on the forms.
You have two choices:
1) In your submit action, you can patch/update the other list with the long list of fields and a bunch of thisField=thisField statements. That will absolutely work, but is lengthy to do and - if you change the list in any way, you'll have to maintain that formula and all it's changes.
2) (I like this one) Create another screen. On it, put a Form for the second list (FormClosed). Connect its datasource to ClosedPIVTickets. Change the "logic" of the form that instead of showing values from the datasource, it shows values from your first form. That way, when you change values in a control in FormRequests (the PIVRequests form), you have the values of the FormClosed's controls set to the values of the FormRequests' controls (for the fields you want duplicated).
Then in your Submit for the first form you would simply do SubmitForm(FormRequests); SubmitForm(FormClosed).
You'll never have function in your App to navigate to that screen, so users will not see it, but you can use it to diagnose issues and to "maintain" your field-to-field copy...in a visual way without putting in all the plumbing yourself.
Why is this a good idea? Again, this makes the experience more visual and understandable for you and anyone maintaining in the future.
You will need to deal with the NewForm logic and if you should submit both or not.
Something like: DataCardValue64's OnChange action: NewForm(FormClosed)
Then in your submit for FormRequests:
SubmitForm(FormRequests); If(DataCardValue64.Selected.Value="Completed", SubmitForm(FormClosed))
So, it's a little hard to completely know your solution needs, but based on what I am reading, this would certainly work well.
BTW - don't be shy about putting "hidden" screens in your app with troubleshooting controls and "common" logic. This will save you lots of headache in maintaining in the future when you've long forgotten what you did to begin with.
Hope this gives fuel for thought.
