Ayuda con solicitud de aprobación en una lista de Sharepoint

Hi @MARTIN VALERO Carlota - Contractor,

Another way is to set Condition for judgment after the flow is triggered. If the column is empty, no approval will be performed. The flaw of this method is that flow will be triggered twice

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards

Cheng Feng

I have tried to put a condition before initiating and wait for the approval it says;

Current value is equal to null

If not ..... Initialize and wait for an approval.

But I keep getting an infinite loop where I get a lot of requests per minute,

What should I do to solve the problem?

Thank you very much

Hi @MARTIN VALERO Carlota - Contractor

If you want to prevent flow execution before the flow is triggered, I think you should choose the method above, Trigger Condition, to avoid secondary execution by setting conditions.

But I have provided the complete method, but you still say it cannot take effect, which makes me feel very strange. Normally, just control flow triggering by setting trigger conditions. It is recommended that you refer to the documentation I provided to help you better use trigger condtion.

What if I want it to be activated when an element has been created or modified in the Value column?

What expression should I put

because if this does not happen, I do not want it to be activated at all.

Thank you very much

Hi

If you want me to help you write the formula for triggering the condition,I hope you can provide me with the formula for the column you need to determine whether it is empty (you also need to tell me the type of this column: is it text, number or date... )

This way I can better help you write triggers

If you need to get the formula, you can use Compose to display it like this, and then place the mouse on it and you can see the complete formula.

Then you can select it just like copying text, and then Ctrl +c to copy it, but the copied consensus will be wrapped by @{}

Like this:

@{triggerOutputs()?['body/Mouth']}

We need to remove the corresponding @{} to get the real formula

triggerOutputs()?['body/Mouth']

equals:

equals(triggerOutputs()?['body/Mouth'],null)

not:

not(equals(triggerOutputs()?['body/Mouth'],null))

Finally copy it, add an @ in front, and put it into Trigger condition

@not(equals(triggerOutputs()?['body/Mouth']))

I hope these detailed steps for writing public announcements using power automate can help you!

I use the following formula in the configuration when creating or modifying an element:

@not(equals(triggerOutputs()?['body/ValorActual'],null))

but it keeps thinking and the flow is never executed.

The type of this column is it number.

*It should be noted that I have the previous versions activated, so that another flow functions in the sharepoint list.

Hi ,

From a testing perspective, you should do this:

First create a record, fill in the value of this column, and then approve it. After approval is rejected.

Let's observe whether Run history is triggered a second time.

When we set the trigger condition, we hope that after approval, if the Update item changes the column to empty, it will not be triggered a second time, or an infinite loop will occur.

Hi ,

We need to simulate a complete test environment,

What you need to do is:

1. Start testing
2. Create a new record (ValorActual must fill in the value, otherwise it will not be triggered, because your judgment is based on whether the column is empty)
3. Reject in the approval email
4. Check Run history to see if there are new Flow running records.

(Another way to judge is whether you receive multiple emails!)

look, every minute it sends me two requests for two different values for two different months, when what I want is to send me the current modified one.

I don’t understand what you mean. Do you mean a record of creating a record and rejection?

It is a rejection record, when I enter a new number in the Value column, but instead of just one request, they start sending several every minute and it never ends.

In flow check it puts a warning in update element: The actions of this flow can cause an infinite trigger loop. Be sure to add appropriate conditional checks to prevent this flow from triggering itself.

I don't know how to solve it

Thank you very much

I understand what you mean, this is just a reminder. I provided two methods for you:

Scenes:

After creating a record, the approval was rejected.

Method 1: Set the trigger condition in the trigger setting: This method only triggers Flow once.

Method 2: Add Condition after the trigger to determine whether the value of the Valoractual column is empty: This method will trigger twice, the first time is executed, and the second time will determine whether the value of the value is empty, the empty is empty Do not perform any operation.

You cannot superimpart the two methods, even if you superimposed, you will only execute the first one.

And you seem to create multiple records at the same time. If so, you can click on the Run History to view how the four are executed.

Could you tell me what I should put to have an activation condition in the configuration, because if I put the condition of Valoractual is equal to null, I still get a lot of requests.

I don't create several records at the same time, but I create the flow of several records

Can you provide screenshot of the [update item], I need to see how you update it into empty。

As you can see, I have sent you a picture of the execution history (which are a few per minute) and my email where the requests arrive, but I only added a new value to the Value column where you see the number, the rest I have not modified anything, nor have I added several values at once or anything.

Hi

Setting:

Trigger condition:

@not(equals(triggerOutputs()?['body/ValorActual'],null))

Let’s simplify the steps. We only need to know whether this Update item will cause the flow loop to trigger.

Here is test :

We wait a few minutes,Observe Run History

There have been no new triggered since 5:55

yes, but what I want is that when someone adds a new number to the CurrentValue column that an approval request is created and if it is rejected, that item is deleted.

The problem is that the flow is triggered by sending multiple of approval requests.

I understand what you mean, your overall process should be:

1. Trigger Flow when the user adds value to the CurrentValue column
2. Send an approval email to inform the approval person

3.1 If you refuse to approve, update the value added by the user to the empty, and the email will be sent to the notification

3.2 If you approve , end Flow

But the key to your problem is that once the approval is rejected, it will be updated item. This update item will be considered by [when an item is created or model] that the ITEM is modified, so the flow triggered Flow has always email you, not ?

So the essential problem is to want to turn the CurrentValue column into an empty value when the Update item becomes an empty value. That's why I set the trigger condition to determine whether the value in it is empty. If it is empty, let Flow False, so that Flow will not start

the problem is that I use the condition you put and it keeps loading for a long time, but it never does anything.

10 minutes later it continues like this and when the time is up it says: time out.

Hi,

Do you mean that after you start the flow and then enter a value in the CurrentValue column, the flow does not start?

Exactly, it keeps thinking and never gets started.

Have you tried using [When an item is created or modified] and [Update item] separately to test like I did.

In my scenario, I followed the information you provided to simulate the environment to test, and it worked perfectly.

If your steps are exactly correct, there should be no problems.

Can you provide me with the steps so I can help you determine where your problem is?

If it still doesn't work, in order to ensure the progress of your project, I will consider using Condition to judge after [When an item is created or modified].

Although this method will be executed twice, it will also avoid triggering the loop.

Good morning

I have tried the flow as you put it and it works.

But what I want is that before updating item an approval is created and if it is rejected, the number added in the Current Value column is removed.

The problem is that if with: when an element is created or modified; and with update element; the approval request enters in the infinite loop.

is what I want to avoid, because otherwise they are sending me requests every minute without stopping, and the activation condition that you provide, I never get to load the flow, it stays thinking and never ends.

Hi @MARTIN VALERO Carlota - Contractor,

Good morning！

You said that trying my method is effective. Are you referring to setting the trigger condition in the setting of [When an item is created or modified]?

If the test demo I asked you to create by [When an item is created or modified] and [Update item] is valid, you can develop on this basis. Because sometimes there will be some unexpected errors, causing the flow you created before to be unable to effectively implement the trigger conditions (the cause of this problem cannot be traced, the best way is to re-create a flow to test)

Or should we add a [Condition] after [When an item is created or modified] to determine whether it is valid?

If this is valid, it will inevitably be executed twice.

You want to create approval before updating. There is also a trigger called [For a selected item], which requires the user to click on this operation to execute it.

Flow name :Test

Because the essence of this flow is that the user first starts the flow, then inputs a data, and then sends it to the approval. If the approval is passed, it will be updated. If the approval is not passed, an email notification will be sent.

But in fact, I think this may have a slightly worse user experience (but it is more logical), but this is approved before filling in. It will be updated only if the approval is passed. If it is not qualified, it will not be filled in.

Here is test：

Approve：

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards

Cheng Feng

If my answer is helpful to you, click "Accept Answer" and please vote up

Doing as you do from:

1. When you create or modify an element.

1.1 Configuration: @not(equals(triggerOutputs()?['body/ValorActual'],null))

2. Initiate and wait for an approval
3. Condition: Outcome is equal Approve
4. In negative case: Update element

It works for me if the request for the element I create or modify in the Current Value column is rejected, but when I approve the request, the infinite loop starts again; because "in positive case" I have nothing set.

I would like to know if I should put some condition in the configuration of when an element is created or do something so that it does not enter the loop and send me numerous requests when I approve the request.

I want to know why you update the column after approval?

What are the next steps? (Can you provide all screenshots of the flow?)

The basis for setting the trigger condition is that the column will not trigger if it is updated to be empty.

If you update other columns after approval, the flow loop will still be triggered. Because essentially we only set trigger conditions for the ValorActual column to be empty, and we did not set conditions for other columns, so after your approval, if you update other columns, you will still enter the loop hell.

Logically speaking, the only trigger conditions for flow are creation and modification. If you do not take any action to update or create a new item after the approval is passed, theoretically there will be no loop.

I update the column after approval because what I want is that if when a new data is added to the Current Value column, the request is rejected, this value is deleted and what I do is to put in update element, in the Current Value column: null; so that if this value is rejected, this added element is deleted.

So, what I want is that if a number is entered in the Current Value column and then the request is approved, then that number stays in the column

and with this flow in negative case, it works well because it sends me only one request for approval and if I reject, the number is deleted; but in affirmative case, when I accept the request, it keeps sending me numerous requests every minute and I don't know how I can avoid this.

Logically speaking, after approval, you do not perform any operations, and this value is the value filled in by the user. That is to say, this record has not been modified and should not be executed.

Do you have other flows that create or modify records?

If this is the case, it may be caused by other flows. Because judging from the information you provided, this problem should not exist. In my environment, after agreeing to stop, there will be no loop.

So, shouldn't I use the update another item?

because I don't understand what you mean.

Anyway, can you think of any other way to be able to do this, or how to correct in positive case?

Thank you very much

Do you mean that you actually have other flows that are triggered and then update other columns of this record? You can consider adding some other trigger conditions in the setting.

For example, whether other columns are empty or have values, this approval flow will not be triggered.

You can tell me the column name and column type, and we will write the trigger conditions to limit

the column name is: Current Value and the column type is numeric

You may not understand what I mean.

my question is:

1. Do you have other flows that update and create records?
2. If yes, please provide the column updated by that flow
3. If you have no other flows associated with this list, but you still have this problem. Then the problem is beyond my scope.

Because in the test in my scenario, whether it is approval or rejection, it will not cause the problem of circular approval emails.

sorry, I misunderstood

You have other flows in which the Current Value column of this list is updated in another list.

HI ,

Sorry, I don't speak Spanish, so the text in the screenshot you provided is unfamiliar.

I used screenshots to translate and roughly understood the situation.

Does this mean that this list update will trigger this flow and then update the records in another list?

In fact, it won't affect the current list.

I tested it in my environment without any problems. But you said that it will be triggered cyclically when approved. This doesn't make sense.

My test scenario:

1. User fills in the value
2. The flow is started and then sent for approval

If approve,

No action is performed.

If reject, use the update method to clear the value filled in by the user.

Send emails to inform users concurrently'

Since no operations are performed after approval, it should not cause loop problems!

Hi @MARTIN VALERO Carlota - Contractor

If the answer is helpful, please click "Accept Answer" and kindly upvote it.

Thank you for your efforts

In effect, I do what you have described and get it to update the current value to null and I'm done.

I used the expression: @not(equals(triggerOutputs()?['body/ValorActual'],null))

and it works for me; but I have the problem if the request is accepted, there the infinite loop starts again and sends me several requests per minute.

It has occurred to me that in the configuration of when an element is created or modified, to put an expression equal to the one put previously, so that if the request of the introduced value is accepted, it stops the cycle. But I do not know what expression I could put.

Could you help me in this?

Thank you very much and sorry for the inconvenience caused.

The flow I use translated into English is:

1. When an item is created or modified 

2. Settings "When an item is created or modified"

      2.1 Trigger conditions: @not(equals(triggerOutputs()?['body/ValorActual'],null))

3. Start and wait for an approval of text

4. Condition: Outcome equals Approve
     4.1 If no: 
           4.1.1 Update element: Current Value: null
           4.1.2 Send an email

I think there is a very important point.

You need to figure out why the flow is triggered again after approval.

Please check the run history. Why is the flow triggered after the review [approval] is recorded?

puts a warning as to why the stream is triggered: Actions in this stream may cause an infinite trigger loop. Be sure to add appropriate conditional checks to prevent this flow from triggering itself.

And I wouldn't know what conditional checks to put in to prevent this.

and could you tell me how I could do that with examples?

It is recommended to fill in ID, Created, or more fields. This will be displayed in the approval email

but aren't you setting some condition or something here, so that if the application is approved, I don't do anything else.

I don't know if you are understanding what I mean.

I'm still trying to troubleshoot the reasons why the loop triggers the flow.

You need to know which record caused your flow to be triggered after Approve.

Then we can know which record caused it through the second approval email.

In the solution I gave you, there should be no problem of loop triggering after Approve.

I think it is because in the expression put in the configuration of when an item is created or modified, as it says that if it is empty stop the flow, I think that as when it is approved, the Current Value column has a number, since it is not null, it constantly sends the request, as it forms an infinite loop. Then I do not know if I could put a condition that if the request is approved, do nothing and stop the flow.

When you modify the Current Value column from empty to having a value.

Then the process begins. Before starting, the column is checked to see if it is empty.

If not empty, the flow begins.

Then approve and the flow ends.

Because before this flow starts, the value has changed from empty to valuable, which then leads to the start.

The problem is that if I approve the value, since there is already a value, the flow continues constantly; on the other hand, if I reject the value, since there is no value, the flow stops.

That is why I was asking if it is possible to put some condition or something so that if the value is approved, the flow stops, because what it detects is that as it is not empty it continues to run infinitely.

Hi@MARTIN VALERO Carlota - Contractor

No, the reason why the flow starts is: you modified the value (or created a record). You only modified it once. Then the flow will be started once due to your modification.

My formula in Setting is to avoid the second modification caused by your use of [Update item], which then triggers the start of this flow.

What confuses me is that you do not have an Update item after Approve, so it should not cause the flow to start again due to modifications.

So I suspect you may have another flow to update or create this list. This will cause this flow to start again

And how could I make the flow you are telling me about?

so that this does not happen

Indeed I have a flow with the same problem, I have put the same expression in the other flow: @not(empty(string(triggerOutputs()?[' body/ValueActual']))) to see if it solves the problem.
The other flow consists of making a column named Trend: 
1. When an item is created or modified

Settings "When an item is created or modified" 2.1 Trigger conditions: 1.

          2.1 Trigger conditions: @not(empty(string(triggerOutputs()?[' body/ValueActual']))))

3. Get item: IDENTIFIER: add(triggerOutputs()?['body/ID'],-1)

4. Update item

So I hope that in this case, putting also this condition, the problem will be solved.

I still have the same problem, even if I also modify the other element

Hi @MARTIN VALERO Carlota - Contractor

Can you tell me that these two flows are actually executed on the same list?

If they are for the same list, the updated items in the two processes will affect each other.

I roughly know how your two flows affect each other.

Scenes:

Here is a list A with two columns DE

D E

1 10

10 20

20

Consists of two flows: flowA flowB

When the user will modify the value in column E of the third row:

D E

1 10

10 20

20 40

Then flow A and flow B will start at the same time

flowA:

Determine whether column E is empty before starting, if not, start

start Approval

if approve

Finish

At the same time, flowB starts and determines that column E is not empty, so the column is updated: then flow A and FlowB are triggered to start.

IF reject

The update column is empty: because flowA has set a trigger condition, it will not start again. But flowB will start again.

So there will be repeated flow starts.

So I suggest you pause these two flows first. Otherwise, there will be a terrible continuous notification.

Then you need to rebuild the flow. Merge the two flows together.

You need to provide the execution ideas of the two flows, thank you.

This way I can better help you solve this problem

and how could I merge the two streams?

If I merge them, do you think this problem would not occur?

so that you understand me:

1. The approval flow I did as you put me in previous messages.
2. The Trend flow I did as it says here: https://learn.microsoft.com/en-us/answers/questions/1371486/calcular-una-columna-a-partir-de-los-valores-previ

Thank you very much

Hi @MARTIN VALERO Carlota - Contractor

I can't guarantee that the problem will be solved.

Because I'm not an expert in power automate.

This forum is actually more focused on sharepoint issues.

So this needs to be tested to know whether it is feasible.

If not merged, I suggest that the approval flow add an trigger condition in Setting to intercept updates to column D.

It will not start regardless of whether column D is empty or not. Let this flow not pay attention to the update of column D

Regarding this flow: https://learn.microsoft.com/en-us/answers/questions/1371486/calcular-una-columna-a-partir-de-los-valores-previ, you also need to set conditions for Trigger to avoid problems caused by updates.

and what condition do you advise me to put in both flows?

I've also asked in the Power Automate community, but they never answer me...

it takes 10 minutes and it never runs, I don't know why.

And half an hour later this message appears: The flow execution has timed out because the initial action has not been performed. Please try again

Hi @MARTIN VALERO Carlota - Contractor

Good afternoon！

Can you share the trigger conditions you set with me?

When an item is created of modified:

Start and wait for an approval

Condition: Outcome is equal Approve

If yes: Get Item -------> Update item

If no: Update item

I have not put anything in Trend, because I have it in the list of Microsoft lists, as a column of type calculated with the expression: =IF(AND(Valor2>Valor1,Valor1>[Valor Actual]),"Descendente",IF(AND(Valor2<Valor1,Valor1<[Valor Actual]),"Ascendente",IF(AND(Valor2=Valor1,Valor1=[Valor Actual]),"Igual","")))

Y aunque no ponga nada, en la columna Título tengo puesto:- (que ese no es el problema)

add(triggerOutputs()?['body/ID'],-1)

Hi@MARTIN VALERO Carlota - Contractor

Thank you for your detailed information

How did you modify the record to trigger the flow?

If you set these two conditions:

Then when you test, you need to

1. Make sure the value exists in the Valor Actual column

2.The value of Valor1 column must be empty

Because your Valor1 and Tendencia will be updated after Approve, and this update will cause the flow to start again, so I added another condition to limit it.

@not(empty(string(triggerOutputs()?['body/Valor'])))

@empty(string(triggerOutputs()?['body/Valor1']))

@empty(string(triggerOutputs()?['body/Tendencia']))

There are three restrictions on flow startup. Valor cannot be empty, Valor1 must be empty, and Tendencia must also be empty.

Ok, the flow works, but I don't know if the condition is set correctly, because if I approve the request, it sends me another request a minute later.

Is there any way to modify the expression or something?Ok, the flow works, but I don't know if the condition is set correctly, because if I approve the request, it sends me another request a minute later.

Is there any way to modify the expression or something?

Hi@MARTIN VALERO Carlota - Contractor

Can you compare the contents of the two approval emails? (Is it about the same record?)

Because the approval process sometimes involves sending two emails at once, this is sometimes unavoidable.