Update Item Field based on WFproperty

Hi!

Can you clarify your issue a bit? Do I understand you correctly, that you want to subtract number of available day per user, once his request for a specific absence type is approved?

In such case - just use the "Update List Item" action to set the new value. You are right - you cannot do it dynamically, ex. in a single action get current value, subtract it and update.

You first need to get the current value, using a "set variable" or any other action, where you can set a variables value using "advanced lookup". Then subtract it and finally using the "Update List Item" action set the new value.

Regards,

Tomasz

Hold your horses

Right, so once again the scenario:

1. You have two lists - users' leave requests (A) and users' leave quotas (B).
2. User places new leave request on a list A
3. The request gets approved
4. Now you need to subtract the approved amount, for the approved leave request type, for a specific user, from the list B.

I see two options. Ok, three to achieve what you need:

1. The "Update List Item" action allows you to provide just a single "filter" rule. So you can select an item to be updated using ex. the user as a comparison. To overcome it, you can query all the quotas, that belongs to the requester, then subtract the one, that got approved, and then using the action update all quotas, having in mind, that in the end only one will be changed.
2. OR you can do, as you wrote - create a switch action, and in each branch of that switch do an update of a specific quota.
3. OR you can use the "Office 365 Update Items" action (be aware, it requires much more time for completion, as it is executed outside of your tenant) and in the "Fields to update" dynamically pass the field name you want to update. This approach is far more the most flexible, so in case you add a new absence type, you won't need to update the whole workflow
   

Please, let me know if the information I provided helped you.

Regards,

Tomasz

Be sure the field, on the list B ist the "Number" type. Maybe you have used a different type. Also - check if the display name is equal to internal name of the column you want to update. You should provide there the internal name, but... maybe try also with the display name

That may be the reason... If you pass column name as a variable it doesn't work. But still, this is weird. It should have!

Are you sure your variable contains a correctly typed value, correct size of cases, no white spaces?

If still no luck, then the last possible solution is to use the "Call HTTP Web Service" action, knowing the ID of the item, from the list B you want to update:

The "var_Headers_Dict":

The "var_Body_Metadata_Dict":

The "var_Body_Dict" (your <qouta-field> along with the value should be set dynamically):

Check it out. That solution should do the trick. Also, get more familiar with the SharePoint REST Endpoints documentation here: Lists and list items REST API reference .

Regards,

Tomasz

Err... Right. My fault. You cannot set it there dynamically.

So the only approach left is the "Web Request" action, where you build headers and URL request strings dynamically. You have to build the whole request body yourself.

The only thing, to keep in mind - Nintex Workflow has problems with string variables starting and ending on brackets { and }).

To achieve that, simply create a string, having ex. ### in the beginning and @@@ in ending, and then replace them using "regex" action with { and }.

Regards,

Tomasz

Uh.. This is really hard to debug it that way  Make sure the account you are using has sufficient permissions (right, you surely use the account having sufficient permissions ).

Maybe try removing login and password from your action. Or try to put the action inside the "Action Set" with elevated permissions. 

You can as well try to execute the action using ex. Postman to check, if that really works for you.

THE LAST option is to obtain rtFA and fedAuth cookies and use them as the header parameters (Working with security credentials (RequestDigest, FedAuth, rtFa)).

Regards,

Tomasz

Regarding the cookie - are you using the "modern site" or the old one?

Sorry, that has nothing in common. Try my answer from the blog post - have you tried simulating this requests with Postman app for example?

Regarding 255 limit - no. The only way is to send yourself an email with the data

Regards,

Tomasz

Still getting an 403 Forbidden response when using FedAuth and rtFa.

With PostMan or with the WebRequest, bot are responding with the 403.

Any sugestion? (Executed WF as SiteCollectionAdmin, with granted permissions, and tried it inside an Action Set)

Regards,