Was hoping someone would be able to help me. Basically I have a sharepoint and planner. Tasks get added to the sharepoint and I already have a flow that then creates an equivalent task on planner, which also adds the planner ID to a column on the sharepoint item for easier reference later.
What I now want to do is have a second flow that will update the sharepoint item with information from the planner task whenever the corresponding task changes assignee or bucket. the buckets represent the stages each task goes through and has an equivalent column on the sharepoint item, ditto for the assginee.
I know there isn't a trigger for this, so thus far have been using a reccurring flow that looks up the planner task ID in the sharepoint list. It just ends up devolving into a massive for each loop mess!
Any help would be much appreciated!
Thanks,
Simon
Related
I would like to premise that I am not a coder, and have limited SharePoint experience. Nonetheless, I have a task at work to create a new tool for a group at work. This tool will allow them to track things through its life-cycle. The old tool will stop being used once they hit the 49,999th record. At that point we will transition to SharePoint. The prior numbers will live with those records and we will be unable to start back at the number 1.
My goal is to have an ID field for each record that incrementally grows starting from the number 50,000.
I tried creating a new calculated formula field that does 50,000 plus the ID but it does not work effectively. There tends to be a lag. The lag can be anywhere from 5 minutes to a day or two. In turn, I need an alternative option.
With a friends coaching, I am messing with SharePoint designer to automatically create a record once one is deleted and delete one every time one is created. However, this times out occasionally. Even more so, it is extremely slow. It will take me a week or so to get to 50,000. Does anyone have any experience or expertise to assist me? It is very appreciated.
The way I did it was to create another field and used that in all my views. Update it through a SharePoint Designer workflow on create - set the field to ID+50000, for example, or whatever you need. Maybe give it a bit of a buffer and set it to ID+51000. By the time the workflow is running the ID has been created and you can use it in a workflow.
If you are going to be moving your old records to the list, you can change the workflow to only update the new field if it's blank. That way you can save the original ids.
I'm looking to get some guidance with Sharepoint 2010. I am working on a project which requires a system that would inform concerned users of an outages with their applciation and provide regular updates via email (worflow).
I can accomplish most of the tasks with a simple custom list and workflow. Users would be able to input their start/end time of the outage, description and their update. With a workflow an email would be sent to the concerned users with all the details.
Where the problem starts is that, we have to provide hourly updates on an outage. So I would need to be able to add new update fields dynamically for every new updates and then be able to send all the updates via an email workflow.
At the moment I am just trying to figure out the best way to go about this. I tought that a simple custom list would be sufficient but looks like ill need to create a more complex system. Perhaps ill need to create 3 custom lists, 1 master list that would gather the details from list 1 (cotnains the description, start/end time) and the list 2 (contains updates) and some how link the together.
Would anyone have any advice about this?
I would create 2 lists: 1 main with all details and another one with updates and added multi lookup field to the first list.
OR even better -
added lookup field to the second list and when item is created - set lookup to the item in the list 1. Then you would be able to get all items from the list 2 (updates) by the item in the list 1.
Hope it makes sense.
Regards,
Andrey.
I would consider having following 4 fields apart from whatever you need right now.
1. Update
2. Outage (choice yes/no)
3. Previous updates (hide it on Edit form)
4. latest update hidden (hide this on edit form)
I would use one list. Let the workflow run whenever a new item is created or an existing item is updated.
For new Outage items send the outage email.
For updates:
Every hour check for update on the item
If there is any update then copy the value to latest update and previous updates. Clear the value of update column.
Send email with latest update value.
Once outage is over user updates the update field and makes outage over to yes.
At this point of time the workflow is complete.
(As far as I know) SharePoint list alerts only fire off due to a change. If I want an email to go out daily even if there were no changes, I figured I could create a calculated field that does today's date minus the "Start Date". It will increment by 1 every day. Will this cause a daily change email to go out? If not, does anyone have a trick for emailing out a list daily even when there are no changes? Thanks!
This will not cause the alert to go out. Calculated fields are only calculated when the list is accessed. The only way I see to do this is to create a site level workflow with a tool like Nintex or create a timer job that can generate the email you want. Nintex Workflows can be scheduled to run on a regular basis. Workflows created with SharePoint Designer cannot be scheduled out of the box.
I was hoping you could help me. I have a calendar in SharePoint 2010 that I want to run a Nintex Workflow when the following conditions are true:
A new item is created
The "Type of Leave" field equals "Vacation". This field I created as just a category for the types of requests.
The date that the item was created for already has an entry with the "Type of Leave" field equaling "Vacation."
The use of this will be that the first person to enter vacation on a day will be automatically granted. But if more than one person enters vacation on the day that another vacation day is on, it will go through an approval process through their manager.
Here's what I've tried/reviewed:
- Using a Condition within a workflow. I can't find an option that would complete this.
- I did try looking on line searching for different solutions. I've watched some tutorials but nothing with this kind of solution was present.
- One thought I did have was to have an additional calculated column that counted how many entries for the same day with "Vacation" and then use that in a condition if the column was greater than 1 but I couldn't figure out the syntax.
This is on SharePoint 2010.
Thank you!
have you considered using the rest interface to query the list from nintex:
http://msdn.microsoft.com/en-us/library/office/ff521587(v=office.14).aspx
You can call this service from nintext using the call web service action.
Apply the filters on the url as per documentation above and count the records returned you can then include that in the nintext condition.
I am not sure if Nintext supports calls to Restfull services (from memory i think it does).
If not, you can use the Soap web service, same principle as above just the parameters to call it are slightly more complicated:
http://msdn.microsoft.com/en-us/library/lists.lists.getlistitems(v=office.12).aspx
I don't think there's an need for REST. Once your workflow starts, query the list for items matching the current item booking date and put the result in a collection. You can query the collection length, and if it's >0 you can use that condition to steer the logic of your workflow.
I'm new to MOSS 2007. I need to create a workflow that looks at a document's review date (a select list predefined to values of 3 , 6 or 12 months) then send an email if the review date has passed.
So the workflow needs to get the documents review date then convert this to date time add to the created date if greater than current date send an email.
Can anyone tell me if this is possible to do using SP designer to create the workflow? I'dd be grateful for any pointers.
Many Thanks,
Nav
SharePoint Designer makes it very simple to create these kind of workflows. Have a look at this article.
Date manipulation can be a bit of a pain so if you need a little bit more flexibility and have the skills to write a little bit of C# or VB code (Visual Studio not required) then have a look at the Workflow Power Pack. There are plenty of examples on the associated blog.
Disclaimer, I worked on the WPP so consider me biased (It works great though :-)
You can do this with secondary workflows, that starts, update dates and finish.