New answers tagged

0

You should use Return as email id semicolon delimited That way there would be no lookup id.


0

Basically, workflows and the built-in Sharepoint Draft/Published feature don't play together. As you have discovered, as soon as you set an item to "Published" and the workflow responds by updating the item, the system considers that an edit and puts the item back to "Draft"... Ideally workflows should have the capability to update items with the option of ...


0

Are you sure that you have set both variables to return data in the correct format? Using a workflow variable of the type Date, this is your available options. (Site is for 2010 but it's the same for 2013 workflows.) As String: 8/2/2010 12:00:00 AM ISO Formatted: 2010-08-02T06:00:00Z (Zulu – GMT) Long Date: Monday, August 02, 2010 Long Time: ...


0

OK, so I never found out why the REST API call wasn't working on the Survey List (I'm guessing it's some kind of limitation for that list type). BUT I did come up with a solution to my problem & business case... In order to accomplish the task of emailing the # of responses from a survey every week, I realized I couldn't build the workflow on the Survey ...


0

Let consider Folder name TestDoc and here i am coping a file from source folder FolderA(or from any where in the TestDoc library) to destination folder FolderB see code below. public override void ItemUpdated(SPItemEventProperties properties) { string strItemProperty = properties.ListTitle.ToString(); if (strItemProperty == "TestDoc") { ...


0

You can do this using default workflow actions. It's a bit tricky though. First you have to have an extra column in your document type. I've added "Resource Identifier" to my default document type. Then as part of the workflow action you set the resource identifier column to a specific value, say 'XX' Then you copy the document to the other library. ...


0

We ended up using a reusable workflow wich SPD was able to create the XSN form.


0

If you only saved the workflow in SPD then your change won't automatically be reflected. You need to republish your workflow.


0

It was my own mistake, I had the status of approved on each approval task process. I later changed it to Pending and this resolved my issue.


0

Glad you offered a long post - helps me narrow down on what I think is the answer for you! That "/?$select=ItemCount" at the end of your URL is superfluous. If you just query http://[mydomain]/resource/025/_api/web/lists/getbytitle('[list display name]') with the REST API call it will return a dictionary of metadata about the list. Then your Get ...


0

SharePoint Designer workflows won't trigger when you're logged in as farm account / system account. Make sure you're logged in as a different user for testing / triggering workflows.


3

You can develop custom action in Visual Studio. I have article regarding that. Workflow (SharePoint 2013, 2010, SharePoint Online) custom action using Sandboxed Solution The example I gave in my article will not meet your requirement though you will get basic steps of creating a Custom Action. Areas to Change declare two parameter in Element.xml. Fist ...


0

I am able to resolve the issue using below steps: Check whether the workflow files like *.xoml, *.wfconfig, *.rules etc, are in check out state. a. Open site in the SharePoint designer b. Click All files and open the Workflow folder. c. Navigate to your SPD workflow and you can see the below files. d. If the above are in “checked-out” state, try to ...


1

With workflows 2013 you can get the version column, split the version to get the "." (example: 2.5) and you get de version. But you dont need do this. You can create a workflow, this workflow will fired when document is edited, you check if version is your X version, if true: send your e-mail.


0

Not sure if it will work but you can try the Is current version. Make a if statement on the current item, look for: field is current version which is boolean and set it to True, in the if you can set your values: If Current Item:Is Current Version equals value { Set Variable: currentValue to Current Item:Field }


0

I have found the answer for this question. The Url I was calling is wrong. There is a REST API for publishing a page. So you need to create a Web Service Call on the Workflow, make a POST without any request parameters, even without the __metadata property that usually is used. But with the request headers filled in as: Accept: ...


0

Could you please goto the workflow and write in logs for each workflow variable created by you.This would help you in know as to which workflow variable has been set null and that would help in resolving the issue. Thanks Bhism


0

When I see things like this, in our environment, it us usually a timeout issue. Too many workflows kicked off at once, or too many open workflow causing a step to take longer than expected so the value hasn't arrived before it is requested. If this could be the case, comment here and we can look at some options.


0

If you have some custom SPD-workflow activity in that workflow and the programmer that created or recently modified that custom activity used this (http://blog.symprogress.com/2011/01/spd-2010-custom-workflow-activity/) tutorial to do that... then you should revise any usage of that custom activity in failing workflows - third argument could be not set


0

I had the same problem and older advices did not work... after some hours of brainsqueezing I found the cause (in my case at least): in my library I had check-out required!!! As I turned it off, all workflow started working well


0

Did you also check the Item specific settings? You can add a workflow to a specific List content type, which as well has an option to trigger a workflow automatically. It can be found via Settings -> Content Types -> Item -> Workflow settings


0

Are you trying to send email from your workflow? If this is what you are doing, then I faced similar issue. Here is how I resolved it- Note the user to whom workflow is sending email. Go to Central Administrator. Under User Profile Synchronization Service search for the user you noted in step 1. Look for its email attribute. If it is empty, then this is ...


0

If you want to copy an item from one list to another on the same site the option in SPD 2010 is to Copy Item but the option in SPD 2013 is to Create List Item. This function you will need to Map each field you want from the 1 list to the other but I found it very easy to complete.


1

It is probably because of a permission problem. Workflow runs under an App identity. That App identity has only access to the current sub-site. Your search request probably returns 4 results when considering all your sites and if you have access to all results... However, when called from a WF, it gets only result the WF has access to, so only results ...


0

A detailed solution on how to solve this problem using only a single SharePoint 2013 workflow can be found in this post: How to Create a Folder in a SharePoint 2013 List using a SharePoint Designer 2013 Workflow The proposed solution works both for SharePoint 2013 On-Premises and Online (Office 365) and uses only SharePoint Designer 2013 built-in actions. ...



Top 50 recent answers are included