If you configured Workflow Manager for your farm, you can use "Call HTTP web service" action to call users REST API, then add/remove a user from a group.
Users REST API
Workflow – Useful REST calls – Add user to group
In addition to Ganesh Sanap’s Solution 1, here’s a sample flow for your reference.
There is one dynamic content called PersonGroupCol Email, which you can directly use to update the Email column. (Where PersonGroupCol is internal name of person or group field.)
Not as good as the Solution 2 but it is doable.
It seems the path of "Get item from dictionary" is wrong.
Please refer below article to work with dictionaries in SharePoint 2013:
Here are some similar issues for your reference:
Sharepoint 2013 Designer workflow ...
You can create a workflow or Microsoft flow/power automate to update the Email address field based on the Person or Group field.
If you are not going to use those email address values later (you don't need to save emails in column) and you just want to show the email in SharePoint list view then you can also achieve it using JSON ...
I assume this is the SharePoint online version. In SharePoint online, to enable the form web part in the ribbon, we need to enable the custom scripting in the SharePoint admin center. To do that we need to follow the below steps:
Go to the TenantSettings.aspx page from your environment like below:
You can install the custom workflow action solution from this link. However, if you have third-party workflow tool like Nintex, you can easily find this action.
The Solutions includes the following SharePoint Designer Workflow Actions:
Create Site Action
Create Group Action
Add Users to Group Action
Here is the answer of your each questions :
Q: How can I tell what version of SharePoint my "personal site" is running? I suspect "SharePoint 2016", On-premises. How can I tell?
Answer: To get SharePoint on-premise version type the below URL in the browser.
To check the version of SharePoint Online, use below ...
Get Items action have a filed called Filter Query which allows you to filter all the list items you need and get them. Mostly the follow will be like Recurrence->Get Items->Apply to each including send emails. Here are some articles talking about using filter query. Have a look at them try with your list.
SharePoint Workflow has no Out of box approach to get previous value of fields. After you change the item, trigger the workflow, we can only get the edited value. Rest api is an option to get version history.
However, have you tried the alert? It will send you an email displaying the edited fields, previous value and edited value like the samples below:
If you just want to collect multiple actions in a step and use this step in the same stage, you can insert a step named "Get Manager Approval" as below:
If you want to pre-define a step and reuse this step in a stage, it's not possible. we can only set a new stage and use this stage in "Transition this stage" section.
You can only transition to a single stage, but if your example is correct you should be able to solve this by moving the condition to the end of the Get Manager Approval stage ?
Stage: Manager Approval
if (CurrentItem:Amount) >= 100) then
Get Finance Approval
Contacted Microsoft support and eventually they located 1800 orphaned workflows and deleted them. I asked them if I had the access to do this in future but they said no and provided the following response:
"These orphaned workflows are not within SharePoint side. It’s orphaned within backend instance. It’s non customer facing part.
It’s related to the ...
You could do this by creating a custom form in PowerApps. When you change the branch it will filter the list based on that value and set the default value for 'Balance':
How i did this
Start by creating a new form. From the top menu, select "PowerApps" and "Customize Forms"
Remove any fields you do not want to display. Simply select the section and press ...
You can as long as you have Version History turned on for the list.
While it is not a built-in function, you can use the Send HTTP Request to SharePoint action in Power Automate to call the Versions REST API and restore the previous version.
Start by using the Send HTTP Request to SharePoint action to call /_api/Web/Lists/getbytitle('NameOfTriggeredLibrary')...
Technically once you commit the changes in SharePoint we can't rollback it directly but through some work around we can do it.
Create another as example temp column, update this with the original column value through the workflow, so here original column value will be retained.. now when approver reject the request update the original column value through ...
Please give us more information on what the workflow is doing. Offer the workflow steps.
Republish the workflow and compare the results.
To narrow down the issue:
please create a new workflow with just log to history action, check whether the issue exists.
Try to start the workflow with other user, compare the results.
There is no such thing in SharePoint as "versioning for the delete process". When an item is deleted, the item and it's entire version history move to the recycle bin, and eventually disappear into oblivion.
You cannot hook an approval process to the delete process, and there wouldn't be any history to that either. If you trigger your Flow on item deleted,...
You may try running the workflow with elevated permission by using the App step action which is available in SharePoint 2013 workflow template.
The App step action will not be available by default, in order to get this action available, we need to activate the
Workflows can use app permissions site feature.
Navigate to Site settings->Manage site features ...
I found the problem, the create item is in the "Apply to each 2", when I removed it it worked fine. I guess the reason was copying it from the update item. Because when I created the "update item", flow puts it in "apply to each", so when I copied it to "yes", "Apply to each" was also copied, while it should not be. However, I am sure I will be corrected if ...
I got the issue.
Solution - Create only one workflow which will contain all conditions and actions.
Issue - Your second workflows is running twice, once when someone changes the item and then when the workflow first workflow get completed, this triggers second workflow to run again.
You can verify this issue form item level workflow history.
You can develop a workflow on the library which should trigger on item creation and create item action and in the configuration of create item select the custom list and map all document library columns (document properties) with the custom list column (the custom list should have the needed mapping columns). That's it - on item creation on document ...
To test if it's the issue about workflow manager, try to use SharePoint 2010 workflow platform and "Impersonation Step" in SharePoint Designer to copy document to another document library, and check if the issue exists.
What's the permission of normal users in the source document library?
Try to add "log to history list" action before each action in the ...
I dint believe it would be this simple. I just had to update the ExtendedProperties column.
listitem["ExtendedProperties"] = Convert.ToString(listitem["ExtendedProperties"]) + " ows_FieldName_Comments='" + "Test comment'";
Follow below steps:
Create a new workflow variable (say indexloop).
Set its value to 0.
Add loop until the indexloop is less than the number of results returned from REST API.
Check below link for detailed explanation and images:
SharePoint Designer 2013 Workflows and GET REST API
Working with Web Services in SharePoint Workflows using ...
It is by design that Workflow local variables for Date/Time store value doesn’t go with the site regional settings and it cannot be changed for the time being.
In my test environment, the variable is using the time zone UTC +0. If I change the time zone under site regional settings to UTC, I will find these two values equal.
Here are steps for your reference:
Step1: Format the excel file as table refer to this article, the result looks like this:
Step2:Create a flow to list rows present in a table, apply to each to cycle the table and create new item in different lists using differnent column name.
Try following approach to replace item permissions:
Set a STRING variable to the multiple selection people picker field, returning the field as a STRING.
In an Impersonation Step, add the action to Add/replace item permissions and use the string variable you just created in above step.
This could also be happened, if the workflow could find the user. In our case, we get the user from another list based on custom field entry (Project Online). And the entry has space in front of it, so the workflow couldn't get the data and it failed with that error message.
For SharePoint Designer it may be needed to do everything by hand with hard coding. A more OOB way will be using InfoPath, you can display a view that is based on a user role.
Or you will need to create a data connection to receive the user information and add rules for switching views. Similar thread here:Change view on Infopath form depending on user ...
In my case (SP Workflow 2013 engine), the lookup column provided only the option for comparing "equal to" and "not equal to", so there was no "is empty".
What I did was simply assign the lookup value to a workflow string variable and then check the workflow value for empty. There, the option was available.