we have a project using Microsoft Team Foundation libraries connected to TFS 2010.
Our TFS projects was based on Agile 5.0 template. So there are many transitions in projects.
My question is can we do transition validation on state change before saving work items?
I have errors when I try to validate state change without saving.
For example, in transition you allow:
"" to "Active"
"Active" to "Closed"
Then you do following:
1. You create a new bug work item.
2. Change state to "Active".
3. Do validation but don't save. --> OK
4. Change state to "Closed".
5. Do validation. --> Failed.
This means you have to save before do further validation. But I don't want to save anything until I'm sure all the state change is OK.
Thanks in advance.
Since a TFS Work Item has a number of triggers (both on the client and on the server) that trigger on field changes and state transitions it is important to save when one of these important fields change. The Status and Reason field is one of these important fields, especially since it normally drives the state machine that is behind these work items.
So unfortunately, there is some validation before save (mostly on input formats), but there needs to be some on the server as well. From the UI there is no way to trigger the serverside validation through another means than by saving. And there certainly isn't a way to have it execute the rules and transtions without saving the workitem to the server.
If this is important to you I suggest you file a request on the Visual Studio User Voice.
Related
I'm working with Quick Create Forms in Microsoft Dynamics CRM. Everything is working as expected. We have a sub-grid of one entity visible in it's related entity. When the User clicks on the + sign of that sub-grid, the Quick Create From appears exactly as it should.
The issue at hand though, is the physical form label of the Quick Create Form. For some reason the system keeps insisting on adding the words Quick Create: on the top of the form before the name of the entity (see image below).
Does anyone know how to prevent this from happening? This is a on-premise Dynamics CRM 365 environment.
Unfortunately this is not customizable.
Maybe you can do some unsupported customizations like overwriting DOM objects, etc. But it’s not recommended.
It appears to have something to do with a CRM Patch that we had installed to fix a Chrome CSS issue. That seems to have added something outside of our control. I'm not a fan of hacks/unsupported fixes, so I think we may have to talk to Microsoft about this one directly.
My partner and I created a custom task form to be used in Outlook using the developer mode to do that, and we published it to the Organization Forms Library for anyone to open. We're running into issues that I personally can't seem to find on how to resolve:
Custom forms aren't syncing correctly.
When I complete out the custom form, and I assign it to someone else they might be missing details like the dates I picked from the date picker, and text within the text box are gone too. It's very odd that sometimes some would get all the details that an end-user would input but that's like a 1/8 chance. I feel like there's a disconnect where it just won't behave like any other task. Cache mode or no cache mode doesn't matter it seems. When the person assigns it back with changes made on their end, those changes aren't seen on my side. I just have the same original details that I made when I first made it. We're on Exchange Server 2010.
Looks like a custom form was not published correctly to others in the organization. Try to create a new Outlook item on other machines with your custom forms to make sure they were deployed correctly.
Note, message forms default to separate layouts for composing and reading. Many people find their first message form doesn't look right when they receive an item created with it. That's simply because they forgot to click the Edit Read Page button and customize the Read layout!
You may find the Customizing Outlook Message Forms article helpful.
In CRM Online 2015 Update 1 instances I experience charts on forms not showing the correct data until they are manually refreshed.
Charts in general show all data from the underlying view when the form is loaded. Only after manually refreshing a certain chart does it show "Only Related Records".
As an example, I have added a chart to the Account entity as seen below. Both the chart and the shown subgrid are using the same view. Even though there is only 1 related record the chart shows all data from "My Open Opportunities" after form load:
After refreshing the chart by clicking the small recycle-icon the correct data related to the current record (in this case 1) is shown:
I have tested this in 3 different CRM Online 2015 Update 1 instances which all exhibit the same behavior. Additionally, this is seen for both system and custom entities.
A similar chart setup in CRM Online 2015 without Update 1 works as expected.
I've got the same problem.
Microsoft has changed how they load forms. For now, you can switch back to the old way by going to Settings -> Administration -> System Settings -> General tab, and selecting Yes for “Use legacy form rendering”
This is only a temporary measure as that option is likely to be removed, but maybe Microsoft will support charts in forms or whatever the issue is by then.
PS:
Drawback is that the new way of loading forms is much faster, so you'll lose som e time if you switch back.
I Haven't tested this yet, but maybe you could add some javascript on the onLoad event to automatically select the view, like your users have to do now manually:
Xrm.Page.getControl(subgridname).getViewSelector().setCurrentView(viewname);
but this isn't pretty either
This issue is supposed to be fixed in Service Update 1 for Microsoft Dynamics CRM Online 7.1.1. From the changelog: "Charts within a subgrid are displaying all records when they should actually display only related records.".
The expected release date is around the middle of December.
I'm looking for some high-level help with determining the best type of Visual Studio 2010 project to use for an Excel custom application.
I will be developing a program that requires the user to enter a dataset in a particular way. Not using a form per se, but rather in columns and the program will need to do some custom validation on the items in order to prep the data. From there, the user will be able to conduct various operations on the data via a custom Ribbon and associated options. The program will also transmit the data via web service.
I've fooled around with the Add-In project and that gives me a lot of what I need but I'm wondering if a Template or Workbook project is better for this in terms of data entry and being able to "guide" the user a little more.
How do you go about choosing between which project type to use? Do all the project types support a custom Ribbon?
Sorry if this is too far off topic. I'm referring to VBA, not Visual Studio, but it might still be relevant.
With an AddIn, compared to a Workbook, you can separate your code from the user's data. So, if the code is complex, and you'll need to update it separately from user's workbooks with data, this is not a bad idea.
With an AddIn, you can add buttons that do things like check to make sure the user data workbook is ok, or process it in someway. However, the AddIn custom buttons will load ever time a user opens any Excel worksheet. This doesn't sound good, but in practice, isn't so bad. You can code your AddIn so it does nothing as long as no one uses a button, so it almost doesn't hurt load times, etc...
A Workbook might be useful if you need to really guide the user - that is, you cannot rely on the user to hit a button to verify something, and instead you need to verify on every change, for example. However, the workbook solution incorporates the user data and your code in the same workbook, so if you need to update the code for existing users' data, that's harder.
I use a combination of AddIn (.xlam) with buttons, and a template (with minimal self-describing data only).
I'm not sure about the template-only option, so won't comment on that.
Does anyone know how to stop Visual Studio from automatically refreshing the Design view everytime I modify the source file associated with a Form?
I'm updating strings on a form that has about a million controls. I'm constantly going back and forth between the design and code for a form. The load time it takes to render the design each time is killing me. I'm not changing anything that would directly affect the design view, so is there a way to stop it updating every time?
No there is not. This is the default behavior and it cannot be changed. The design view when focused will always try to update with the latest version of the source. If it has changed the design view will too. This is necessary to ensure that any changes which occur to the UI reflect changes on the current state of the source code.
My workaround was to edit the code in notepad so I could click around in Design view without refreshes, then pasted the code back into V-Studio