When trying to reference the customer journey in a workflow this way, it seems to not get any values despite being triggered from a customer journey using the 'Launch Workflow' option. Is there a solution to this issue?
Related
I'm having a problem in outlook that whenever anyone at the company tries to create a zoom meeting in outlook it also adds a Microsoft Teams meeting link as well. I did research to try and turn off the setting at the Organization level and I found the following PowerShell script : Set-OrganizationConfig -OnlineMeetingsByDefaultEnabled $false. Does anyone know if this will fix the automatic Teams invite?
I've been tasked with coming up with a way to insert a link into all of our meeting invites in Office 365.
This link will be different based on the location of the meeting.
At a high level, how can I use something like an Azure function to run some code and act on every meeting object when they are created?
Directly through Azure Function, I don't think it's possible unless you keep querying the office 365 api in order to get the meetings (and compare with previous state to get the new ones).
What you can do is combine Microsoft Flow and office 365, and from the flow, call your azure function.
https://powerusers.microsoft.com/t5/General-Power-Automate/Easiuest-way-to-get-calendar-id-for-the-Office-365-Calendar/td-p/6279
We have an automation in place to move information from BUG to a customized ticket template (Infra Requests.xml) in case of infrastructural issues. Currently an AD account is being used to create tickets. I want to use the CreatedBy field from Bug to create Infra Requests. I know we have way to check-in behalf and queued-build behalf, wondering if we have similar for create-workitem.
You can create a work item and update the CreatedBy field with the bypassRules option. The same question was here: How to change the Created By field on a Work Item in TFS?
Link to rest api: Work Items - Create
I'm using the SharePoint Three-State workflow for a complete and then validate scenario on an InfoPath form. A web service creates the instance of the InfoPath form in the library. The idea is that the workflow will get a particular user to complete the form and then gets a manager to approve it. Simple stuff really.
The workflow fails to start unfortunately. The log shows an argument exception when it tries to start the workflow. Strangely it runs fine when manually started so that rules out the association data being incorrect. I've also tried this with other OOTB workflows such as Approval. I've thought it might also be the creation of the item through the web service but then it all works in my development environment.
I'm hoping someone might be able to contribute what I'm forgetting to check.
What identity is your workflow attempting to start under? If it is the SharePoint System Account, that account cannot start declarative workflows, as documented in this SharePoint Designer Blog post on MSDN.
This same problem impacted one of our workflows, where a web part programmatically created a list item and our workflow was set to trigger on item create and update actions. Manually creating items or manually running the workflow worked because it happened under our personal credentials.
Our solution was to simply create a service account in AD that the web part could impersonate. Once the list items were no longer being created under the System Account, the workflow worked as expected.
If you are receiving an argument error, I would check that the workflow is not referencing a field that would not be populated at the time of creating the list/library item. If you reference something like the ID field or a calculated column this field would not be available.
I have a code activity that sends an email in a VS workflow. It simply sets the 'To' property to the name of a SharePoint group in the site collection. However, only the 1st person in the group gets emailed.
Any ideas why this is happening?
thanks
Does your group contain anything other than just users (ex: distribution lists, ad groups)?
If this is still a problem and you need to be able to send to a SharePoint group, I would recommend writing a custom workflow Action that would gather the emails of all the users in a specified group (you can find many tutorials online on how to make a custom action).
Turned out it was not even emailing the first user. I decided to extract the user emails programatically instead. Works fine.