Solved: Is it possible for the '' SAVE '' button to save t...

Anonymous · ‎02-19-2020

Hi,

I have 2 Buttons, Submit, which sends the form and SAVE. But Save is not working. Can someone tell me if this buttom it possible to Frizee the information in the form, and if the user enters the same ''ITEM'', the information will it appear?

The previous code "ON SELECT" in SAVE is not working.

Thanks !!

365CornerDawid · ‎02-20-2020

@Anonymous apologize my mistake... the formula should be:

Patch(Custom,Form1.LastSubmit,{StatusChoice:{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
   Id:0,
  Value:varMode}})

As you can see the mistake was with ID=Form.LastSubmit if you will use just Form.LastSubmit it will knows that it is correct record.

Ok now second part with the flow:

make sure that you are using trigger for create and modified

Assign the site and list name.

Not it is starting to be a little bit complicated but you can try follow the YT: https://www.youtube.com/watch?time_continue=561&v=j-gP-E6CCE4&feature=emb_logo

But the steps are:
Add the Compose action (you can remove it later on)
Create following function (replace StatusChoice with your field)

equals(triggerBody()?['StatusChoice']?['Value'],'Submit')

Next take the function and click three dots on your trigger and select Settings

find the Trigger condition settings add @ to your function:

@equals(triggerBody()?['StatusChoice']?['Value'],'Submit')

Save and test your solution - remember that there is delay due to the Flow timer job.

If this resolve your problem please mark answer as Solution.

View solution in original post

Anonymous · ‎02-25-2020

Hi,

Sorry for not answering quickly, The solution was as follows:

1. In ''On success'' fuction of the form :

Refresh('yourBackEndListName');

Patch(yourBackEndListName, FormName.LastSubmit.ID, {Status:{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:0,
Value:varMode}})

2. Save Buttom:

SubmitForm(FormName);UpdateContext({varMode:"Draft"})

3. Submit Buttom:

SubmitForm(FormName);UpdateContext({varMode:"Submit"});

In the Flow:

When the form is in `` SUBMIT '' state, make the next action, if not, keep asking until it is not in `` DRAFT '' state

Thank you very much for the help.!!

View solution in original post

eka24 · ‎02-19-2020

Just to clarify, do you want to prevent someone from entering the same item. What field name is this item you want to prevent. You said the save button is not working but I see it is creating a collection.

Anonymous · ‎02-19-2020

Hi,

Thanks for the prompt response. 🙂

The only thing that the user wants is that, if in any case he still does not have all information needed, can save and exit without sending the information until he clicks on Submit, since clicking on submit a workflow begins to run. The collection is created, but when I enter to the ITEM, the information on the form is empty, it means that it is not being stored in any collection.

The collection is created but is not sending the data, I suppose. Is there something wrong with the code?

eka24 · ‎02-19-2020

Did you enter data into the fields.

365CornerDawid · ‎02-19-2020

@Anonymous
You know that Collect will create collection in the current session?
Do you want to provide the functionality to save the data "permanently" = when the User will next time open the app the item will be possible to edit with previously entered that?
Let me know if yes as now you are storing data only in memory not in your back end (SharePoint?)

Anonymous · ‎02-19-2020

Hi,

That is exactly what I want the app to do. When the user re-enter to the form, will be dirty with the information the user entered.

Thanks form the help !

365CornerDawid · ‎02-19-2020

Ok,
Im making assumption that you are using SharePoint as back-end - please confirm:)
Second is question: is it Canvas / stand alone application with two screens one with list of items and second with the Form where you have challenge?
Or it is Customized Form and User is selecting SharePoint item?
In my answer assuming that you are using Canvas app.

To SAVE data you need to create them in the back-end. You have at least two options will describe easier one.
- secondary list with draft items
- DRAFT status in the main list (you can hide or create specific view for DRAFT items)

Easier is to add STATUS column to your SP / Back-end and in the Form
In the App change the formula of the SAVE button to:
SubmitForm(FormName);
UpdateContext({varMode:"Draft"})
Then OnSuccess of the Form
Add
If(varMode="Draft",Patch(yourBackEndListName, ID=FormName.LastSubmit.ID, {Status:"Draft"}),Patch(yourBackEndListName, ID=FormName.LastSubmit.ID, {Status:"Submit"}))

For your Submit button/action
SubmitForm(FormName);
UpdateContext({varMode:"Submit"})|
Dont need to change OnSuccess

Q: do you have the Power Automate workflow assigned in the application to Run OnSelect ? or when item is created?
If you have RUN OnSelect of the Submit you dont need to do anything else.
If you have the Power Automate on the item creation you need to add the condition to it to start only for "Submit" items.
You will find the condition section if you will open settings of your trigger - that is suggested method than adding condition action in the workflow as it will run extra empty executions...

Hope it all make sense - let me know and accept the solution if it is correct 🙂

Anonymous · ‎02-19-2020

It is a custom form and the user selects the data from a sharepoint list. The application is married to the list. The workflow is assigned in the application when a new ITEM is created.

Anonymous · ‎02-19-2020

Is there something wrong with my code? Should I add the ID field somewhere?

365CornerDawid · ‎02-19-2020

@Anonymous Did you added the Status field to your list? If the Status is not added you will see error.
Next if you created Status as the choice and not text you should Patch your item Status in following fashion:

{StatusChoice:{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
   Id:0,
  Value:"Submit"}}

Change Value to Draft or Submit or any other value.
Also in your case you could try following simplification if always one of two actions will happen: Draft or Submit.

Patch(yourBackEndListName, ID=FormName.LastSubmit.ID, {Status:{'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
   Id:0,
  Value:varMode}})

Change made here will just assign value of the Status to one of the two values of varMode variable.

Sorry that did not came up with this quicker.