Work Notes

Some useful notes and links here from Steve Mordue , CEO of ForceWorks on Account-Based Marketing, and ways to adapt the native behaviour of Dynamics 365 to support it. Beyond his suggestions I think the following are key in terms of building and information base about your target accounts: acquire as much contextual information about accounts as possible, via both automated and human sources whilst acquiring as much data as possible about individual customer interactions on touchpoints, put significant effort into linking those individuals to an account when customising the touchpoint experiecne for an individual, take into consideration their account context, including other recognised individuals

Background Since upgrade of CRM Online to 8.2, we have noticed some strange issues around workflow triggers that are supposed to be fired by the change of a record status. We have a workflow associated with the Invoice entity that is set to trigger on change of record status: Workflow trigger settings The workflow is responsible for setting up various bits of data when we issue an invoice, then flagging to an external integration that the invoice is ready to send to Finance.

It’s different from Windsor – just working out exactly how

Getting back on the blog wagon

Now playing with Federated Wiki here

Today was rebuilding a solution that had been updated to xunit2, and kept getting random test failures, usually with some kind of conflict with Rhino Mocks. The fix seemed to be to turn off the parallel testing. A little googling turned up this which suggests Rhino Mocks does indeed have a problem in a multi-threaded test environment

Had some issues when adding custom fonts to IdentityServer – which is when I found in the docs that by default it implements Content Security Policy Also found some issues with trying to override the builtin Bootstrap with the CDN version… Found this useful reference on CSP and ASP.net This resource looks useful too – CSP Playground

If you need to use ILMerge, you must use an unencrypted strong name key for your assembly If you change the strong name key for your assembly, CRM thinks it’s a whole new assembly, so it might pay to create new ones explicitly If you are now including the generated CRM early-bound classes through ILMerge instead of as a source include, remember to add [assembly: Microsoft.Xrm.Sdk.Client.ProxyTypesAssemblyAttribute()] to all deployed assemblies

Looking at identity

Contract review and markup with potential new supplier word, sharepoint still good tools for that sort of thing! setting up some sample products in Aha! so far really liking the structure and the UI of the product