Microsoft Dexterity does not check in resources "all the way" into source control repository

Just recently, we migrated to Visual Studio Team Services from Visual SourceSafe and Team Foundation Server. Our migration went very smooth, with only a couple issues to report -- you can read more about these in the 2-part series here and here.

During our testing phase, prior to the migration, we ran into an issue where resources were being checked out of the VSTS repository, but did not seem to check back into the repository all the way, requiring the developer to go to Visual Studio Source Control Explorer to complete the check in. We attributed this to a simple environmental issue as the developer also had been having other issues with his machine in general. He had already committed to reformat his machine so no further thought went into this. Also, it is probably a good time to mention that no one else was experiencing this problem so off we went into the sunset.

Fast forward a couple weeks. After completing the migration and back working on our daily development activities, the same developer reported having the same issue once more, this is, he would check out a resource from the repository, make changes to that resource, and check the resource back into the repository. However, the resource would not check all the way in, requiring to complete the check in with Visual Studio.

The next immediate step was to compare the source control settings between a working and the non-working environment. A working environment had the following settings:


Dexterity Source Control Options

Root Directory: C:\Projects\Features\Deadbolt\
Project Name: ABCD

The non-working environment had the following settings:

Dexterity Source Control Options

Root Directory: C:\Projects\Features\
Project Name: Deadbolt\ABCD

In comparing the two, it was obvious the project name in the non-working environment was preceded by the folder on the disk where the project could be located. Dexterity never barked at this during the setup, so our developer assumed it was Ok to leave it as shown above. Since resources were checking out fine and he could work, he never thought much of the setting.

Once his settings were changed to match that of all working environments, things were good again - check-in worked as expected!

In retrospect, the Apply button should validate these settings, so we will attribute this to a bug in Dexterity. Perhaps is non-consequential, but certainly a headache if you are in a pinch.

Until next post!

MG.-
Mariano Gomez, MVP

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more