I am trying to perform a simple task for Azure Devops work item type Release. All we need to know is how many days between State - Testing to State - Documentation for these items. If this was historical data in some SQL table, it's no question for me what to do but it seems there isn't any simple way to report on this within Azure Devops. I would like to be able to do this all within Devops itself without having to use excel, some external app. just simply be able to see it right in devops.
Generally this is accomplished by adding an extra field to store the state transition time and adding a rule that populates that field when the work item is put into that state. Then you can simply query these two dates and diff them.
Related
Elaborating the title further, the current ADF I am working on has a lot of legacy code, i.e. multiple datasets, linked services. Unfortunately no naming convention or system of creating new items were defined.
I have tried to list down all the pipelines, the associated datasets (linked services as well), but this seems a lengthy approach and we have around 100 odd pipelines.
I tried by exporting the complete data factory as an ARM template and tried to create a parser which would automatically create the above list, but it seems that ARM templates are more interlinked than I had thought, I dropped this plan.
Is their a better approach for solving this problem?
You can pull the pipelines/dataflows that uses the particular dataset. this details will be available in the properties tab -> Related tab.
enter image description here
Also you get the list of datasets that uses a particular linked service by going to manage tab ->Linkedservice -> Related
enter image description here
Since you haven't mentioned data factory version (v1 or v2) and mentioned it has lot of legacy code, I am making an assumption that it could be a v1 factory. In that case, you can check the ADF v1 to ADF v2 migration tool which helps with basic migration tasks (listing resources, doing simple migration steps etc.)
I'm using PowerApps to build a project management reporting interface, and I'd like to indicate on the main list of tasks whether something is a main task with subtasks or a subtask. We are syncing a microsoft project file with a sharepoint task list, and the mobile interface provided by sharepoint is bad. I can't find a task item property that is accessible within a powerapps query that will indicate this
I've iterated through all of the task item properties that are apparently exposed to the list connector, and none of them seem to indicate when something is a subtask. isFolder always returns false, even on top level tasks, so it seems like that property isn't being used to track this.
I expect to be able to build a conditional so that when my gallery is populated I can indicate if something has subordinate subtasks, how many there are, and allow people to browse to them. No matter what I've tried so far the list appears to populate unsorted and without any distinction between master tasks and subtasks
Had a similar problem; the current connector to Project Online is very rudimentary. However, if you have access to Power BI you can use the ProjectData REST api to send an OData query to get everything you are looking for. Power BI is much better for reporting/browsing data, and if you need to edit the SharePoint list you can embed PowerApps within a Power BI report.
Have also looked at using PowerApps to edit MS Project tasks, but as you noticed the connector is not fully functional. I think this may be by design; even the REST APIs do not allow for setting baselines, you have to open the file in MS Project Pro to have full access.
I have been trying to find a standard way to include databases schema patches into my Azure continuous deployment flow.
So the problem I am looking for a solution to, is that as an application evolves, so does the database. Ever so often there are changes to the database to support new functionality etc.
In earlier work situations I have used proprietary solutions that hold changes to the database in a linked list in an Xml document. The database then knows the latest patch it applied, and if any new patches are present it will apply them. That way it is easy to keep all environments synchronised, and the changes follow the code.
While these proprietary solutions have worked great, I was thinking that before I implement yet another tool to do this, I would see if there was a standard solution provided by SQL Azure to solve this problem. But I haven't been able to find one.
Is there one or do I need to create a tool myself?
Visual Studio Database Projects support deploying to Azure SQL Database so this is a good way to incorporate it into a CI workflow. If you are used to traditional deployment methods it is a bit of a mindset change; these projects work out at deploy-time what to deploy. For example, if you want to create a table, add a Table to the project and fill out the columns. Then, say months later, you want to add a column, simply add the column to the CREATE TABLE script. When you deploy, it will work out that the only schema change is a new column and it will add it.
This is a nice little series on that topic:
https://channel9.msdn.com/Blogs/Have-you-tried-turning-it-off-and-on-again/Creating-a-Database-Project-for-Artificial-Intelligence
As the title says...
I've successfully got workflows working that create project tasks, so I have some idea how the workflow customization tools work. But I'm struggling to see how I can (or even if I can) use a workflow to auto-magically add resources to the project (and then assign them to the project tasks I dynamically create.
Regarding which users/employees to add as resources, I imagine sorting out an appropriate clause shouldn't be too hard.
If I recall correctly, Resouces on a Project record are sublists. If I am correct, then it is not possible via workflows. There is a limitation with Workflows that they cannot work on record sublists.
You will have to do this via SuiteScript.
In my solution I have a workflow where one step contains a reference to Queue. After importing this solution on another CRM instance this workflow could not be activated because it contains an invalid reference - Queue can not be resolved. Queue with same name is created on new CRM but resolving is probably based on record Guid.
Now, I'm wondering, is there a way to edit workflow steps using CRM SDK? Whole process of CRM solution deployment is automated. And I want to remove all manual work. Some example would be great :)
Thanx in advance!
There are 2 things you can do if you are having issues with the Guids not matching in a workflow lookup when deploying from one environment to another.
Use the API to create those records referenced in the WF. When you create a record you can actually specify the Guid that it uses as the id. So write a tool or see if one exists already that will create some default data for your environment.
Use a configuration entity with references to all the EntityRefrences needed in your WFs. Then you can create a custom workflow activity to retrieve the configuration entity record (there should only ever really be one) that contains all the references in that environment.