Sunday, April 27, 2014

Google books lets you sample pages from any book

In "shouldn't-this-be-illegal?" news, google books lets you browse some limited number of pages of any book it indexes. That includes many technical books making this quite handy!

Here is one sample book, have fun.

Google lawyers have a FAQ: http://books.google.com/googlebooks/perspectives/facts.html

Fiction: If a book is still under copyright, scanning it without permission is illegal.
Fact: This is probably the most common misconception about Google Books, and about copyright law in general. The "fair use" provisions of U.S. copyright law (USC 17 107) describe the conditions under which someone may copy a work without the copyright holder's permission, like recording a TV show to watch later or quoting from an article in a blog post. Fair use is designed to safeguard copying that doesn't harm people's incentive or ability to produce and sell creative work, including books.
We've carefully designed Google Books to make sure our use of books is fair and fully consistent with the law. Copyright law is aimed at protecting and enhancing the value of creative works in order to encourage more of them–in this case, to ensure that authors write and publishers publish. We believe that by creating new opportunities for readers to find and buy books, we can help authors and publishers sell more of them. You can read more about fair use here.

Given the obvious risk of being able to reconstitute the book samples into the whole the established publishing regime must have disapproved. Google engineers must have seen that coming and had some reasonable arguments to defend the position. To be a fly on the wall there...

TDD is Dead Long Live Testing?

David Heinemeier Hansson has a great article on his blog titled TDD is Dead Long Live Testing. I wrote a similar article here in 2012: To Unit Test or not to Unit Test. TDD is a great programming technique and I cannot agree more with David that when it work, it brings a new confidence to the iterative development practice that is hard to match. But set in its proper context of the software and testing life cycle, TDD is an interesting technique that has costs often exceeding its benefits.

Friday, May 24, 2013

Software Training is All About Timing

The point of this post is simple -- software training cannot be successful until users have the live system in front of them with a goal in mind they want the software to help achieve.

I am not an expert when it comes to the fine details of software training. How best to conduct the sessions and how to present the content are things I respect but have little practical expertise in. I am, however, a witness to a great many people who learn how to use new software systems and I am (painfully) aware of the kinds of problems they have.

I am not naive about the difficulty of setting up the "software in front of your users with goal in mind" scenario but in most software deployments there is one convenient moment that puts your users in a position to succeed -- during parallel testing. A parallel test is no small task but it is the perfect opportunity for this scenario to exist for a wide range of users. Piggy backing on the parallel test for training is superior in efficiency of dollar spent per unit of user skill gained to traditional up-front user training because of the psychological engagement only real use cases can invoke. I strongly recommend parallel testing for any system roll-out for many other good reasons but utilizing the optimal training moment is one of the best side effects.

Psychologically, when users have "skin in the game" they can learn. And to be painfully realistic, very few are capable of learning before that point. We are busy, we have deadlines looming, we simply cannot pay attention to a system training for a system we will not touch for another 2 weeks and we've never seen before!

So I am recommending the abolishment of traditional up-front user training sessions? No. What I am recommending is a shifting of the goal of that up front meeting (and hopefully reducing its duration and expectations).  It can provide enough of a primer that the users think the system will be easy to use. Show high level things it can do. Describe in glorious detail how it will make their life easier. Set up scenarios and make the software sing. Its almost a full sales demo, but with the system's future users instead of its purchasers. Get them excited about it. That first training session is more about "buy-in" and emotional connection to the new reality. Make them want it by selling the system. That is about as good as you can hope for. This is a huge difference from the usual top-down approach that has a tendency to demoralize future users and encourage animosity towards support staff (notice how support teams are seperated from the trainers? Why are these are different teams? Support is very often "just in time" training!) negative feedback that finds its way back to the stakeholders as complaints about the "complexity of the system". That rationally stubborn user behaviour can be curbed by acknowledging the very human need for buy in in a sales-like kick off meeting. Of course there are limits to the success of this initiative and after that buy in meeting there may still be resistors, but at least you've identified them (or perhaps the solution doesnt solve their problems and thats a whole 'nother issue :)).

TL;DR: Up front training is not successful for logical reasons. Use up front sessions to create user buy-in instead of training. Parallel testing is often the ideal time to train users.



Friday, March 8, 2013

Web Deploy v2 and Web Application Packages



WebApplication.deploy.cmd -- when I run this command on my local machine I was getting this message:

To deploy this Web package, Web Deploy (msdeploy.exe) must be installed on the computer that runs the .cmd file. For information about how to install Web Deploy, see the following URL:
http://go.microsoft.com/?linkid=9278654

To install V2 of the MSDEPLOY.exe you MUST FIRST UNINSTALL V1! There is no failure message if you install V2 after V1, it just simply doesnt write the V2 files to the V2 directory if V1 is installed. Odd behaviour, but is what it is.

If this is not your issue, check out VS2010's SP1 fix to the WebApplication.deploy.cmd:
http://stackoverflow.com/questions/6595086/msdeploy-v2-doesnt-work-with-vs2010s-packages



Wednesday, March 6, 2013

CRM 2011 FYI for programmatic solution imports


The ImportSolutionRequest.PublishWorkFlows property also publishes SDKProcessingMessages! It doesnt say this in any documentation, but it does. It is explicit on a solution import through the GUI.

Tuesday, March 5, 2013

Rollup 12 Service Activity bug and Microsoft's Public Apology


Our users found an odd bug on our service activity form (where we have custom javascript to set a lookup field based on some business logic).

The error below started coming up after rollup 12. I explain steps to reproduce in more detail here:
http://stackoverflow.com/questions/14819416/bug-in-crm-service-appointment-forms-javascript-causing-form-save-error/14989557#14989557

We ended up getting an acknowledgement of the bug from Microsoft and they pushed a fix online, but will have to wait for rollup 13 for the fix on-premise. They are damaging their credibility with these bugs and I am not the only one to notice. It even prompted a public apology from Bob Stutz, a Microsoft VP. Apologies can't give me or my customers their time back.

>System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #52178855: System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
>   at System.Guid.GuidResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument, String failureArgumentName, Exception innerException)
>   at System.Guid.TryParseGuidWithNoStyle(String guidString, GuidResult& result)
>   at System.Guid.TryParseGuid(String g, GuidStyles flags, GuidResult& result)
>   at System.Guid..ctor(String g)
>   at Microsoft.Crm.Application.Platform.AttributeCollection.CreateEnityReferenceFromLookupPropertyValue(String name, Object value, IOrganizationContext context)
>   at Microsoft.Crm.Application.Platform.AttributeCollection.SetEntityProperty(Entity entity, String name, String childAttributeName, Object parentProperty, AttributeMetadata attributeMetadata, Object value, IOrganizationContext context)
>   at Microsoft.Crm.Application.Platform.AttributeCollection.Insert(String name, Object value, Boolean throwIfKeyExists)
>   at Microsoft.Crm.Application.Platform.EntityProxy.SetLookupValueData(XmlNode node)
>   at Microsoft.Crm.Application.Platform.EntityProxy.SetData(XmlNode entityElement)
>   at Microsoft.Crm.Application.Platform.ApplicationEntityCollection.Deserialize(String entitiesXml, String entityType, IOrganizationContext context)
>   at Microsoft.Crm.Application.Platform.EntityProxy.SetData(XmlNode entityElement)
>   at Microsoft.Crm.Application.Forms.EndUserForm.RetrieveParametersForEventDefault()
>   at Microsoft.Crm.Application.Forms.EndUserForm.Initialize(Entity entity)
>   at Microsoft.Crm.Application.Forms.CustomizableForm.Execute(Entity entity, FormDescriptor fd)
>   at Microsoft.Crm.Application.Components.PageHandlers.SchedulableActivityBasePageHandler.ConfigureFormHandler()
>   at Microsoft.Crm.Application.Components.PageHandlers.ServiceAppointmentRecordPageHandler.ConfigureFormHandler()
>   at Microsoft.Crm.Application.Components.PageHandlers.RecordPageHandler.ConfigureFormWrapper()
>   at Microsoft.Crm.Application.Components.Utility.GenericEventProcessor.RaiseEvent(String eventName)
>   at Microsoft.Crm.Application.Controls.PageManager.OnPreRender(EventArgs e)
>   at System.Web.UI.Control.PreRenderRecursiveInternal()
>   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
>   at System.Web.UI.Page.HandleError(Exception e)
>   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
>   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
>   at System.Web.UI.Page.ProcessRequest()
>   at System.Web.UI.Page.ProcessRequest(HttpContext context)
>   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
>   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Import CRM 2011 Solution Dependency Error for a Workflow



I have a workflow that creates a Case from an Opportunity. It maps fields like the title and price list and spits out a case, simple and tested in my development org. However, when I exported the unmanaged solution it resides in as managed and import that into a blank org, this error occurred:

The dependent component Attribute (Id=parentaccountid) does not exist.  Failure trying to associate it with Workflow (Id=13e950d4-8e77-e211-b5f0-080027cd26e8) as a dependency. Missing dependency lookup type = AttributeNameLookup.

Despite having the dependency (parentaccountid is a system field on the Opportunity Product entity!) in the target org. So right off the bat I know this is going to be a weird one. How can I not have a stock system field?

My own analysis looking into the XML for the workflow found one node with reference to parentaccountid for preferredserviceid. (perferredserviceid is a system field on the account). However, the workflow did not contain a reference to that preferredserviceid field! How odd. Its like CRM remembered at one point that it did have a reference to it and never removed it. That "memory" caused it to output the field as a dependency in the workflow XML but not in one of the workflow steps itself. How odd.

I attempted deleting the whole workflow and re-add it to see if that node exported in the new workflow and it did not. After deleting and painfully copying each detail from the original workflow into a new one the error was gone. Hope that helps someone else in this situation.