I have a workflow that runs upon the change of status of an entity (Opportunity "Won"), in which I am creating another entity.
I want to copy all the notes from the Opportunity to the new entity, but I cannot see how to do it.
Is this possible without coding (or in fact, with coding!)
Chris
Its not possible without coding. With coding (custom workflow activity and the ICrmService) you can read and creates notes (Entity: annotation).
I agree with benjynito answer. You need to hook a custom workflow activity in order to get the notes object.
Here is the link to setup a basic custom workflow activity : http://www.stunnware.com/crm2/topic.aspx?id=CustomWorkflowActivity
An example of some custom activities on CodePlex: http://crm4activities.codeplex.com/
Custom workflow activity documentation on MSDN: http://msdn.microsoft.com/en-us/library/cc151142.aspx
It is possible to do this using the clone children action in "Dynamics 365 Workflow Tools". I used this library to copy the notes from a lead to an account when the lead is qualified. For exact steps see the documentation of clone children or my blog post Copying Notes from a Lead to an Account that shows you how I did it for notes.
Related
I am currently using devops (cloud) services. I have created a custom Work Item Type (WIT) within an inherited process from Agile. I would like to configure it to behave like exactly like Agile's User Story WIT. By this I mean:
The WIT should be addable in the taskboard view of the Sprints (see first pic, WorkItemTaskBoard).
One should be able to add tasks to the item just like User Story's.
The WIT should rank below features in the WIT hierarchy. This way when it is added as a child of a feature it will be visible in the Backlogs view (see second pic, BacklogChildMissing)
According to my reading I need to export my inherited process as an XML, edit said XML then import the modified XML. I have two issues with this.
A. I have not found any reliable documentation how to perform the above.
B. Although I am using cloud based Devops (dev.azure.com) and am the organization owner I do not appear to have rights to import a process (see third pic, ImportProcessMissing)
Can anyone confirm that I need to perform the export, edit, import the XML as specified above in order to achieve 1, 2 and 3? If so, I would need help in figuring out how to import the process.
WorkItemTaskBoard
BacklogChildMissing - The WIT is not displayed despite being a child of Test Feature.
ImportProcessMissing - Import button is missing.
You can follow the steps like as below image shows to configure the customer WIT in the inherited Agile process.
Create the custom WIT.
Set the custom WIT as the Stories backlog level.
After above settings, in the project which is using the inherited Agile process, you can manage the custom WIT like as User Story.
See below example:
I have inherited an Azure Data Factory solution in my new job. It has been worked on by at least 6 different BI developers. I'm currently busy with cleaning up my Azure Data Factory, fixing version control, and making sure that all my three environments are the same.
Some objects seem obsolete to me. To check if it is obsolete, I go over to the portal, and check the objects Properties if it is related to another object.
If not, it is a confirmation for me that the object is not (yet) used and I can safely remove it from the solution.
Is there an easier way than checking each object?
I figured it out and wanted to share it here. It is possible to check the "orphaned" objects in an ADF instance, however not directly from the UI. Paul Andrew has an excellent blogpost about his script that is able to check your ADF code against his best practices. The relevant checks for me are:
Pipeline(s) without any triggers attached. Directly or indirectly.
Dataset(s) not used by any other resource.
Trigger(s) not used by any other resource.
Linked Service(s) not used by any other resource.
The last check can also be done via UI, see #AbhishekKhandave-MT answer.
Step 1: Export ARM template to a local folder, and unzip it
Step 2: Download Paul Andrews PowerShell script from here
Step 3: Open the script and replace the $ARMTemplateFilePath variable with the path to your ADF ARM template. If you want to check out the details, change the $VerboseOutput variable to $true
Step 4: Run the script and check the results.
Here are my results, so 58 datasets are not used by any other resource.
Unfortunately, there is no other way to find whether object is used(yet) or not.
But you can check number of datasets linked with a single linked service as shown in below screenshot.
Manage > Linked Services
Click on number in Related column.
We are using Azure Devops Server. When a bug is created, I would like to create a child task automatically. The task does not need to have any particular properties, it just need to be created with default values and have a default name like "Placeholder" or something like that.
I have already encountered some different ways of doing it, but neither of them seems to be well suited for me:
The extension 1-click-child-links could be used to create a child task by clicking a button in the context menu after creating the bug. This will of course work, but it would be even better if it could be done in the background ensuring the task to be created even if the user forgets to click the button.
As I understand it, using the Microsoft Flow software tasks can be created in the background when creating a bug which would be exactly what I'm looking for, but it would be nice to find a simpler way of doing it without installing a complete software tool.
I've learned that it is possible to hook into different events by using service hooks (https://learn.microsoft.com/en-us/azure/devops/service-hooks/events?view=azure-devops). There are a couple of standard integrations, but neither of them can be used to solve my case. So using this method, I guess I need to develop a custom service creating the task?
Is there a simpler solution to achieve my gool or do I need to stick with one of the solutions above?
As a workaround , we can set Azure Logic App, select When a work item is created"as trigger, and then select Create a work item as action.
Make sure to set the Link URL to the “When a work item is created” URL and set the Link Type to Hierarchy-reverse to create the Task as a child of the Bug item. Please refer to the settings below:
Save the Logic Apps Designer, and then when the bug item is created, the child task named Placeholder will be automatically created.
I have a User Story against which there is an impediment faced in current sprint. Due to this impediment, we are not able to complete the US in this sprint. However we cannot also close it or mark it resolved. Since its open without any action, its also interfering with the burndown charts.
Can I get an advice on how we can handle impediments in Azure DevOps and thereby set that work has been halted/suspended on a particular user story? I was reading the related article here: https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/manage-issues-impediments?view=azure-devops.
Thanks and Regards,
Satheesh Vijayan
As stated in the documentation:
You use issues or impediments to track items that may block work from
getting done. In general, you link these items to user stories or
other work items using a Related link type.
So as a workaround ,you can try customizing impediments tracking ,through this you can customize the item state,add a special state to impediment item . For details, see Customize an inheritance process.
Organization Settings -> Process -> Inheritance process -> Impediment ->State -> New state
Note: only inheritance process can be customized.
In Azure DevOps Boards, if you open a work item and reference another in the discussion field by using #ID for the work item you want to discuss, ADB automatically relates those two items.
More recently, the dev team has determined that the code review tool they are using is tying reviews to multiple work items because of this related field.
Other than telling the team to avoid using the #ID feature or manually removing related work items from each story and task, is there a way to prevent #ID from relating work items, but still allowing the live link in the discussion thread?
The #ID control quickly links objects to work items. With this control, you can specify or select a work item ID and it's automatically linked to the object.
Use the #ID control within the following areas:
A work item discussion or any rich-text field
A pull request discussion
Commit comments
Changeset or shelveset comments
Wiki page
Is there a way to prevent #ID from relating work items, but still
allowing the live link in the discussion thread?
Sorry it's not able to do this. This is by designed, it will automatically link to the object in Azure DevOps.
If you really do not want this, you may have to avoid to use #ID or manually remove the link relationship.
More details about link work item you could also kindly refer this official tutorial.
for Azure DevOps 2019/2020
You could enable or disable commit mention work item resolution , for details you could visit : https://learn.microsoft.com/en-us/azure/devops/repos/git/resolution-mentions?view=azure-devops
I've test 2019 and 2020 version , it works fine for me.