remove past mistakes

[PALE]

hello to all,

One of you can describe to me how to delete the spots that have encountered a failure in my flow because they keep re-engaging THX 

PHIl

[BCLS776]

That flow run history you see cannot be altered; however, after 28 days those flow runs disappear from the listing.

I'm curious though - why would you want to delete the flow run history? I find it very useful for debugging and spotting issues with flows.

Bryan

[PALE]

Hello Bryan  @BCLS776  

thank you Bryan for your feedback.

to explain to you, I am a user with little experience in the POWERAPP field ... and unfortunately I do not master English too much, it is very difficult to find advice in my French language ...

In fact I created a sharepoint list for my colleagues, in this list they fill in data which is then processed by other operators.

So in my list I placed two flows
the first changes a choice (Invoices aviable / Not aviable) in the case of the presence of an attachment or not.

The segond retrieves the attachment = creation of a folder in a library and creates a folder with the attachment.

unfortunately this flow generates an infinite loop,
I therefore tell you that the flow is triggered only on the condition that there is an attachment, and that once this attachment recovers the flow is locked

but it seems to be complex despite everything ....

Thanks to you
phil

[BCLS776]

Yes, I see your flow is running repeatedly over a short time interval. It sounds like this is happening because the flow is triggered by some sort of automatic criteria, such as whenever a SharePoint item is edited.

One way to make sure a flow runs once and only once for a particular item is to implement this practice:

1. Add a yes/no column to your list that will be a toggle to indicate if this item should or should not be subject to future flow runs
2. Add a trigger condition to your flow so that it only runs if the yes/no toggle you created in 1 meets the proper criteria - see this link
3. Change your flow(s) so that they update the value of the yes/no toggle upon successful completion of the first run of the flow on that item

This will set up your flow to run once (and only once) for each SharePoint list item unless the value of the toggle gets changed.

Je parle un peu français, alors n'hésitez pas à me répondre et je ferai de mon mieux pour vous répondre en français

Regards,

Bryan

[PALE]

Hello Bryan,
I hadn't seen any notifications for your reply 😉
I read your instructions, I'll try that and get back to you.
thank you very much
Philip

[PALE]

Hello @BCLS776  Bryan 

J'ai effectué les opérations que tu recommandes .

Comme j'ai dans ma liste champs avec un choix  '' INVOCE AVAILABLE'' or  ''NOT INVOCE AVAILABLE ''j'ai utilisé celui ci à la place de  Complete, j'ai donc ajouté dans le paramètres de mon déclencheur  @equals(triggerBody()?['{INVOCE AVAILABLE}'],true)  si je ne met pas @ devant il indique une erreur ?? 

seulement je ne suis pas certains de la bonne hiérarchie dans mon flux ?

car ensuite j'ai ajouter la conditions , mais il me demande ensuite de lui indiquer si OUI ou SI NON ?

I did the operations you recommend.

As I have in my fields list with a choice '' INVOCE AVAILABLE '' or '' NOT INVOCE AVAILABLE '' I used this one instead of Complete, so I added in the parameters of my trigger @equals (triggerBody()?['{INVOCE AVAILABLE}'],true) if I don't put @ in front it shows an error??

Merci Bryan 

only I'm not sure of the right hierarchy in my flow?

because then I added the conditions, but then he asks me to tell him if YES or IF NO?
and the i'm afraid this is not a good build

[BCLS776]

It is a bit tough to read the jpg you included, so please try to capture smaller pieces of the operations in several images. However, I can see that you have no blocks in the Si Oui or Si Non sides of the condition. You will need to drag your code blocks into the appropriate side so that they only execute when the condition is satisfied.

As for the trigger condition, the format is different when you use a SharePoint choice column. Try this example, which will allow the flow to operate when "Invoce Available" is the choice for the record:

@equals(triggerOutputs()?['body/Invoice/Value'], 'Invoce Available')

Bryan

[PALE]

Thanks for your help Bryan @BCLS776 
I now have a big problem😥

I had carried out a first test with the addition of a column in my sharepoint list, I deleted, and it no longer appears in my list.
But in the fields when you encode new data!? and the form refuses to register and yet does not indicate an error!!
It's very annoying for my colleagues
do you have any idea of the origin of this problem?

Phil 

[BCLS776]

I'm not sure I understand your problem correctly, but it sounds like you are experiencing an issue after deleting a column from the SharePoint list. This is a very different question than your previous one, so I encourage you to start a new thread so we don't confuse other readers.

However, I will offer one thing I have learned: if you delete a column and then later change names or add a column with the same name to the list, the column name will be different. See this blog for more info.

Bryan

[PALE]

Brian, it's ok

I was able to modify and delete it here! and it works now, even if the window no longer closes automatically...