Microsoft CRM

Findings on Sdk.Soap.js Action Message and Entity Class Generator

Andre MargonoMicrosoft CRM

Microsoft Dynamics CRM SDK team released the Sdk.Soap.js to write JavaScript code in web resources that can perform actions using theMicrosoft Dynamics CRM 2013 Modern App SOAP endpoint. You can use this library in with web resources.
http://code.msdn.microsoft.com/SdkSoapjs-9b51b99a
The extension of the Sdk.Soap.js is Action Message Generator:
http://code.msdn.microsoft.com/SdkSoapjs-Action-Message-971be943
And Entity Class Generator:
http://code.msdn.microsoft.com/SdkSoapjs-Entity-Class-14ca830f
That really useful in creating early-binding type of development for Dynamics CRM.

I followed through the instruction for the Action Message Generator to connect to Dynamics CRM Online instance. I follow exactly each steps that the instruction described, however I got the following error:

The application terminated with an error.The server could not be contacted.the LDAP server is unavailable.

Initially I was quite confused with the error message, as I did not change any part of the SDK sample code at all. So, I decided to debug the code and I found out that the exception was coming from the lines that were trying to authenticate with the current UserPrincipalName with PrincipalServerDownException. The reason I got the above error is:

  1. My computer is joined to a my company’s domain, and the I’m logged in to the computer as a domain account. However, the DC is unavailable. (I’m off the domain; working on home network)
  2. I’m on the domain. However, I’m in a multiple-domain environment in which the LDAP query service is on an inaccessible domain. (firewall rules on WiFi connection).

 

So, to fix this issue I modified the sample SDK code that apparently utilising the same CrmServiceHelpers class from the Quick Start guide (http://msdn.microsoft.com/en-us/library/hh675400.aspx); from:

// For OnlineFederation environments, initially try to authenticate with the current UserPrincipalName// for single sign-on scenario.else if (config.EndpointType == AuthenticationProviderType.OnlineFederation && config.AuthFailureCount == 0 && !String.IsNullOrWhiteSpace(UserPrincipal.Current.UserPrincipalName)){ config.UserPrincipalName = UserPrincipal.Current.UserPrincipalName; return null;}// Otherwise request username and password.else{ config.UserPrincipalName = String.Empty; if (config.EndpointType == AuthenticationProviderType.LiveId) Console.Write("\n Enter Microsoft account: "); else Console.Write("\n Enter Username: "); userName = Console.ReadLine(); if (string.IsNullOrWhiteSpace(userName)) { return null; }Console.Write(" Enter Password: "); password = ReadPassword();}credentials.UserName.UserName = userName;credentials.UserName.Password = ConvertToUnsecureString(password);break;

To:

// For OnlineFederation environments, initially try to authenticate with the current UserPrincipalName// for single sign-on scenario.else{ var isPrincipalServerDown = false; var currentUserPrincipalName = String.Empty; try { currentUserPrincipalName = UserPrincipal.Current.UserPrincipalName; } catch (PrincipalServerDownException) { isPrincipalServerDown = true; }if (config.EndpointType == AuthenticationProviderType.OnlineFederation && config.AuthFailureCount == 0 && !isPrincipalServerDown && !String.IsNullOrWhiteSpace(currentUserPrincipalName)) { config.UserPrincipalName = currentUserPrincipalName; return null; } // Otherwise request username and password. else { config.UserPrincipalName = String.Empty; if (config.EndpointType == AuthenticationProviderType.LiveId) Console.Write("\n Enter Microsoft account: "); else Console.Write("\n Enter Username: "); userName = Console.ReadLine(); if (string.IsNullOrWhiteSpace(userName)) { return null; }Console.Write(" Enter Password: "); password = ReadPassword(); }}credentials.UserName.UserName = userName;credentials.UserName.Password = ConvertToUnsecureString(password);break;

Now I’m able to generate the Custom Action that generated by the tool:

CRM On-Premise Sandbox Colour Scheme

Andre MargonoMicrosoft CRM

A workmate in crime from Brisbane office, Gerhard Pretorius, recently posted an interesting tricks to change On-Premise Deployment with Sandbox Colour Scheme that currently only available on CRM Online:

To make an On-Premise CRM system display the “Sandbox Theme”, you will need to do some code…

Just a note – this is only available for CRM 2013 RU2 and up. THIS IS AN UNSUPPORTED CUSTOMISATION!

Edit the main.aspx file on the CRM server, this is usually located at C:\Program Files\Microsoft Dynamics CRM\CRMWeb\main.aspx. In the head section of main.aspx, after the title tag add the following tag (replace OrgName with your CRM Organisation name):

<script>

    if (ORG_UNIQUE_NAME == "OrgName") {
        var IS_SANDBOX_ORG = true;
    }

</script>

 

Restart the CRM Server / do an IIS Reset.

Only the sandbox instance will now show the orange “Sandbox Theme”. This is a great way for users to know which system they are in.

Bulk Execute On-Demand Workflow with Kingswaysoft SSIS

Andre MargonoMicrosoft CRM

Recently I read a discussion in a mailing list on how to execute large number of on-demand workflow and out of curiosity, I tried to look for the method that was discussed, which uses Microsoft Dynamics CRM for Outlook as elaborated here:

http://www.powerobjects.com/blog/2013/07/30/run-on-demand-workflow-in-dynamics-crm-250-records/

I tried that method with 7000 records and apparently it took long time for me to finish the operation and makes my Outlook application not usable for long period. So, I think there should be another way to do this, as I was presenting the SSIS toolkit in the last Melbourne CRM UG, I recalled that there’s “Execute Workflow” functionality in Kingswaysoft’s SSIS toolkit.

So out of my experiment, I set up a simple SSIS project to execute On-Demand Workflow on Contact record to give the value on email field:

And create a simple SSIS process as follow:

1. Contact Data Source:

2. Destination To Execute Workflow with Batch Size of 200 (I learned this batch size from SF, where their bulk operation is limited in 200 for performace, unsure about Dynamics CRM)

3. The Result

The whole operation that took hours when using Microsoft Outlook client, now accomplished within 4 minutes and 55 seconds (approximately 5 minutes)! It is accomplished with relatively simple and intuitive process.

Below is the result on contact records:

 

 

 

Dynamics CRM 2013 SP1 – UX Update – Mostly Unnoticed

Andre MargonoCRM 2013, Dynamics CRM 2013, Microsoft CRM, Microsoft Dynamics, New Features, UX,

Dynamics CRM 2013 SP1 comes with lots of new good stuffs, such as the new Service Management, SLA, Timer on Case, Queue Routing, Social Listening and many more. However, for me as CRM user that always use PC and web browser to work with Dynamics CRM, the user experience for PC client quite cumbersome, especially the navigation bar that collapses immediately when my mouse pointer is navigated away from the bar. I love to have responsive mouse pointer and most of the time my mouse pointer goes out the navigation bar and closes the navigation bar, resulting multiple click to main navigation menu.

As my online instance being updated with Spring 14 release, I noticed an improvement in their UX. The navigation bar does not collapse immediately when my mouse pointer goes out of the bar.

This UX definitely gives a massive impact to my productivity. Big thanks to Dynamics CRM product team to listen to the feedback and delivered this feature!

 

Dynamics CRM 2013 SP1 Plugin Registration Tool Revamped!

Andre MargonoDynamics CRM 2013, Microsoft CRM, Microsoft Dynamics, New Features, ,

Today I checked the Dynamics CRM forum to answer some of the questions there. One of the question that I tried to answer was regarding the plugin registration tool. The screen shot that uploaded by the question shows different UI of plugin registration tool that I usually use.

Then I check the latest SDK for Dynamics CRM 2013 SP1 (6.1): http://www.microsoft.com/en-au/download/details.aspx?id=40321. The SDK now provides the new Registration Tool under Tools > Plugin Registration (No longer in the “Bin” folder)

Below is the comparison of the old & new layout of the plugin registration tool:

The new Tool definitely is no longer using Windows Form Application. The new tool has different authentication method than the old tool, where we don’t need to specify the discovery URL (where we usually need to go to Settings > Customization > Developer Resource):

The Online Region Selector now helps us to construct which CRM discovery server to be connected to (where crm5 is my region):

Overall functionality of the tool does not change. There are some details that added to the new Plugin Registration tool

One thing that made me curious is the usage of the “Gear” button (usually it’s setting) that cannot be clicked. Perhaps it’s a bug??

 

 

Data Migration/System Integration using SSIS (Salesforce to Dynamics CRM Example)

Andre MargonoCRM 2013, Dynamics CRM 2013, Microsoft CRM, Microsoft Dynamics, , , , ,

Recently I had a chance to do a couple of data migration & integration projects for Dynamics CRM. On these projects, the ISV product that we chose is Dynamics CRM SSIS Connector by KingswaySoft. I got a great support from my MVP role model, Daniel Cai, during the project.

In this post, I would like to explain some basic setup, features and benefits of using the SSIS connector for Dynamics CRM. SSIS is really useful in system integration and migrating the data from legacy system to a newer one. In my sample scenario I’ll be using Salesforce.com as the data source and Dynamics CRM as target source. (This sample scenario is considering the of the situation of migrating data from Salesforce to Dynamics CRM. So, I hope this post will be beneficial for anyone that migrating data or considering to move from Salesforce to Dynamics CRM).

Note: KingswaySoft provides free SSIS connector to run under BIDS/Visual Studio, therefore it is a great tools for once-off data migration projects. For continuous processes (set the SSIS package schedule for instance), we need to buy the paid license (really reasonable price for this quality of tool + support). For pricing & purchasing info: https://www.kingswaysoft.com/purchase

Part 1: Environment Setup

1 . Visual Studio 2012 with SSDT Installed / BIDS 2008

(Note: Depends on the Production environment; AFAIK, the manifest file generated for deployment will be based on the IDE that generate the SSIS package; e.g. BIDS 2008 is for SQL Server 2008, and SSDT 2012 is for SQL Server 2012)

In this example I’m going to use Visual Studio 2012 with SSDT installed. (Download: http://www.microsoft.com/en-au/download/details.aspx?id=36843)

2. Install SSIS Connector for Dynamics CRM.

Download: http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-crm/download

Dynamics CRM Connector help Manual:

http://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-crm/help-manual

3. Intall SSIS Connector for Salesforce.

Download: https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-salesforce/download

Salesforce Connector help Manual:

https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-salesforce/help-manual

 

The installers from KingswaySoft will then install the License Managers for both products (Dynamics CRM and Salesforce)

Part 2: Getting Started With “CRM” SSIS Project

For this sample, I’m using Salesforce.com developer edition. To get a free developer license: https://developer.salesforce.com/ then click on Sign-Up.

The SSDT installation for Visual Studio 2012 will install Business Intelligence Project Templates in Visual Studio. Therefore, when we create on New Project, the new Business Intelligence Projects will appear on the template list. Select Business Intellience > Integration Services > Integration Services Project:

For a fresh install on BIDS 2008, the Dynamics CRM and Salesforce connector will not appear automatically, to add the Conneciton Manager and the Toolbox components please refer to the help manuals listed above (part 1). Visual Studio 2012 + SSDT installation automatically lists all available pipeline components by scanning the system.

Setup Connection Managers

First of all, we need to create connections to both Salesforce (Source) and Dynamics CRM (Target). By Right-Click the Connection Managers box > New Connection:

Dynamics CRM and Salesforce connection will be listed amongst the connection list:

  • Create Salesforce Connection Manager:

The connection manager will open up the connection window that consist of Username, Password and Security Token to Salesforce org. To test whether connection has been successfully configured, click on “Test Connection” button. Then click OK to create the Salesforce Connection Manager.

Note: Salesforce connection is highly secured and they implemented Security Token for any API connections that came from outside trusted IP ranges. To reset the security token (in case not provided initially):

  • Create Dynamics CRM Connection Manager:

The conncetion manager will open up the connection window that consist of Authentication Type, Discovery Service URL (please note the discovery service only need the first part of the URL. Without the following “XRMServices/2011/Discovery.svc”), Service Endpoint, SDK Client Version, Username, Password and Organisation Name. To test whether connection has been successfully configured, click on “Test Connection” button. Then click OK to create the Dynamics CRM Connection Manager.

Note: (As usual) to get the Dynamics CRM web services URLs, navigate to: Settings > Customizations > Developer Resources

Build SSIS Control Flow & Data Flow

To start building the SSIS package, it starts with the Control Flow and Data Flow. For this example I’ll transfer Lead and Account object from Salesforce to be mapped to Lead and Account Entity in Dynamics CRM. To achieve that: drag 2 Data Flow Task components into the Control Flow and named it with meaningful name, example:

Then drill down to the underlying data flow task by double click the task in Control Flow. Drag Salesforce Source and Dynamics CRM Destination component and link them:

Double Click Salesforce Source to configure the Lead data source. And click on “Columns” to select the required columns as part of the data source. Then click OK:

Double click Dynamics CRM Destination to configure the destination and field mappings from Salesforce:

Note: I created a custom text field with 18 character to store the Salesforce id as reference (FYI: Salesforce ID is generated in either 15 or 18 length format, not GUID).

Do the same with the account and run the project:

Confirm that the data are transferred from Salesforce to Dynamics CRM:

Bonus Part (Part 3): Deployment Preparation and Package Configuration

Configuration

In Visual Studio 2012 + SSDT, we will not find “Package Configuration Wizard” in SSIS when we right click in Control Flow (this is the way to prepare the configurations in BIDS 2008) as the 2012 version introduced the new model for configuration and deployment called the Project deployment model. As part of that change, the old way of doing configuration (environment, xml, parent package, registry and table) is not an option. In the project deployment model, you get parameters and environments. Therefore to create the configuration in the “classic” way, right click on the solution and click on “Convert to Package Deployment Model”:

Now the package configurations option is back:

Since we have converted the deployment mode, the deployment .manifest file can be generated through the solution properties and setting the “Create Deployment Utility” to True:

“

 

And as the project being built; The deployment files are generated:

Microsoft Dynamics CRM Spring 2014 Release Preview Guide

Andre MargonoCRM 2013, Dynamics CRM 2013, Microsoft CRM, Microsoft Dynamics, ,

Following up the excitement of last night presentation about the key new features of Dynamics CRM 2013 in Q2 2014 release in Melbourne Dynamics CRM User Group by Mark Smith (@nzCRMguy). Microsoft also released the release preview guide.

This Q2 2014 release is highlighting lots of really amazing new features:

  • Microsoft Dynamics Marketing – major enhancement for marketing: Drag and drop visual Campaign Designer, Lead lifecycle management, Marketing Personalised Homepage, Scalable Email Marketing, Power BI for Marketing, Improved Sales & Marketing Connector (This Dynamics Marketing enhancement requires an extra Office 365 Procurement).
  • Updates on Sales Automation – Insights (puts real-time company and contact information from 30,000 sources into Microsoft
    Dynamics CRM), CRM Tablet App Enhancements
  • Customer Service – USD (Unified Service Desk – not US Dollar), Enterprise Case Management (SLA & entitlements, dynamic routing, KPI, case merge, parent child case, automated case creation, Define Status Reasons, Social Care, Service Management), CRM Tablet app –  Case Management.
  • Parature – Multi-Channel Care: portal, facebook portal, mobile app, real-time chat, Knowledge Management
  • Social Listening – Listen & Analyze, Monitor & Respond, Social Insights in Microsoft Dynamics CRM
  • Sandbox Environments (2 types of sandboxes are available: Minimal Copy & Full Copy) with the abilities: reset Sandbox to Factory Settings, Sandbox snapshot. On top of the sandbox environment, Admin also has the access to the New CRM Online Admin Center.

Aside from the new front-facing features there are also enhancement on the platform capabilities that enabling organizations to build, test and configure CRM deployments of all sizes.

Tooling:

  • CRM Package Deployment Tool
  • CRM Configuration Migration Tool
  • Updated Plugin Registration Tool
  • Visual Studio Toolkit enhancements
  • More PowerShell Support
  • New Windows Client API ( Microsoft.Xrm.Tooling.xxxx )

Extensibility:

  • OAuth discovery specification to support ISV/office clients
  • GROUP AND/OR for workflows

Scale: Scaling Improvements in Async processing to handle very large workloads.

And again adding more compatible environments:

  • Windows 8.1
  • Internet Explorer 11
  • iOS7 Safari on iPad (web application)
  • iPad Air using Safari (web application)
  • Windows Server 2012 R2 (CRM server)
  • iPad Air using CRM for Tablets

Full details can be found on: http://go.microsoft.com/fwlink/p/?LinkID=395005

Once again, it is definitely an exciting journey for Dynamics CRM, Dynamics CRM is moving really fast and looking forward for the landing of this massive release.

 

 

Dynamics CRM 2013 – New Features Limitations

Andre MargonoBusiness Process, Business Rule, CRM 2013, Dynamics CRM 2013, Microsoft CRM, Microsoft Dynamics, New Features, Workflow

Dynamics CRM 2013 new features: Business Process, Business Rule and Synchronous Workflow are a major leap from CRM 2011. These nifty features added a lot of benefits to the selection customisation tool. For example, by using Business Rule, we could eliminate some javascript form scripting that might require more time to test. And Synchronous Workflow might eliminate plug-in development that sometimes quite tricky to test, especially on Online deployment.

In spite of the benefits that we could utilise from these new features, there are some limitations that we might need to aware of, especially in designing the best solution in terms of maintainability, performance and the time effort that need to be spent.

Business Process
In designing business process there are maximum number of processes, stages, and steps:

  • The maximum number of activated business process flows per entity is 10.
  • The maximum number of stages in each process is 30.
  • The maximum number of steps in each stage is 30.
  • The maximum number of entities that can participate in the process flow is 5.

Synchronous Workflow
With Synchronous Workflow, user could see the results by the time the record is saved (in CRM 2013 form, the changes that made are saved automatically every more or less 30 seconds interval or by clicking the TINY save button at the bottom right of the form), compared to javascript, where user could see the changes straight away.

Planning synchronous workflow might be similar to planning synchronous plugin, try as much as possible eliminate the long-waiting process to be registered as synchronous one for better user experience.

Business Rule
This is one of the killer features of the new Dynamics CRM 2013, but there are some limitations. And for some occasion, it will determine our conclusion whether we should go with javascript/plugin/workflow/business rule.

With current release, as far as my trial-and-error experiment with business process, we could only have one condition and one action. So it is like a single if statement:


If [this condition]
Then do [this action]

Meanwhile, if-else or switch-case scenario is not available

If [condition is A]
Do [action A]
Else if [condition is B]
Do [action B]
Else if [condition C]
Do [action C]
Else
Do [default action]

To achieve this, we need separate business rules and might want to check whether one rule is unique to the other rules, which is quite messy for a solution.

If [condition is A] and [not condition B] and [not condition C]
Do [action A]
And so on…

Business Rules are Entity-Bound
The fields that can be used to build the business rule are only available from the entity that the business rule is attached to. So there are limitations when we need to access fields/condition from related entities (child/parent entity). To achieve this, we should choose either workflow/plugin/javascript path.

So far these are my findings on the limitation of the new features in Dynamics CRM 2013. In future post, I might add any additional limitations Dynamics CRM 2013 or Microsoft might release updates on these limitations to make Dynamics CRM 2013 as the best platform for xRM implementation.

Solution file (.sln) lost CRM Developer Toolkit Instance

Andre MargonoCRM 2011, IT Study, Microsoft CRM, Microsoft Dynamics, Microsoft Dynamics CRM 2011, , , ,

I’ve encountered this issue several times (especially when we are check in to TFS), that the solution file is not merged properly, and for some reason the developer toolkit bind is removed.

 
To fix this, edit .sln file using notepad/any text editor, then add:
 
GlobalSection(CRMSolutionProperties) = preSolution
  SolutionIsBoundToCRM = True
EndGlobalSection​
 
In Global, after:
 
GlobalSection(TeamFoundationVersionControl) = preSolution

 

MS CRM 2011 – Hiding a Group of Ribbon on Specific State

Andre MargonoCRM 2011, Microsoft CRM, Microsoft Dynamics, Microsoft Dynamics CRM 2011, , , ,

Today I come up with another task to only show the button on a group only when the record has already been saved.
After some times reading at the CRM 2011 SDK documentation and some time searching for clue, I found a solution.


The above pictures are the desired result. The button should be shown after the record has been saved.

So the changes to the Ribbon XML can be like this:

<RibbonDiffXml><CustomActions>  <CustomAction Id="Mscrm.ISV.campaignresponse.CustomGroup.MaxSize.CustomAction" Location="Mscrm.Form.campaignresponse.MainTab.Scaling._children" Sequence="150"><CommandUIDefinition>  <MaxSize Id="Mscrm.ISV.campaignresponse.CustomGroup.MaxSize" GroupId="Mscrm.ISV.campaignresponse.CustomGroup.Interaction" Sequence="21" Size="LargeLarge" /></CommandUIDefinition>  </CustomAction>  <CustomAction Id="Mscrm.ISV.campaignresponse.CustomGroup.CustomAction" Location="Mscrm.Form.campaignresponse.MainTab.Groups._children" Sequence="115"><CommandUIDefinition>  <Group Id="Mscrm.ISV.campaignresponse.CustomGroup.Interaction" Command="Mscrm.Enabled" Title="Interaction" Sequence="85" Template="Mscrm.Templates.3.3" ><Controls Id="Mscrm.ISV.campaignresponse.CustomGroup.Controls">  <Button Id="Mscrm.ISV.campaignresponse.Form.Interaction.Button.AddGuest"Command="Mscrm.ISV.campaignresponse.Form.Interaction.Command.AddGuest"ToolTipTitle="Tip"ToolTipDescription="Add Guest"LabelText="Add Guest"Alt="Add Guest"Image16by16="/_imgs/ribbon/AssignRoles_16.png"Image32by32="/_imgs/ribbon/AssignRoles_32.png"TemplateAlias="o1" /></Controls>  </Group></CommandUIDefinition>  </CustomAction></CustomActions><Templates>  <RibbonTemplates Id="Mscrm.Templates"></RibbonTemplates></Templates>  <CommandDefinitions>  <CommandDefinition Id="Mscrm.ISV.campaignresponse.Form.Interaction.Command.AddGuest"><EnableRules></EnableRules><DisplayRules>  <DisplayRule Id="Mscrm.ISV.campaignresponse.CustomGroup.Interaction" /></DisplayRules><Actions>  <Url Address="$webresource:pages/addGuests" PassParams="true"/></Actions>  </CommandDefinition>  </CommandDefinitions><RuleDefinitions>  <TabDisplayRules />  <DisplayRules><DisplayRule Id="Mscrm.ISV.campaignresponse.CustomGroup.Interaction">  <FormStateRule State="Create" InvertResult="true" /> <!-- THIS IS THE TRICK --></DisplayRule>  </DisplayRules>  <EnableRules /></RuleDefinitions><LocLabels /></RibbonDiffXml>

Add Button to Ribbon on MSCRM 2011

Andre MargonoCRM 2011, Microsoft CRM, Microsoft Dynamics, Microsoft Dynamics CRM 2011

Today I got a task to put a button on Ribbon Bar in Microsoft Dynamics CRM 2011.
I’m new to 2011, even I only learned CRM 4 about 5 months ago.

I can’t find good references on the SDK, luckily I found Gareth’s Tucker Blog that discuss into detail how to create a button.

Hopefully it helps us, developers 🙂

CRM 4.0 Deployment Problem – web.config cannot be loaded properly

Andre MargonoMicrosoft CRM, Microsoft Dynamics, , , ,

Today I developed an application to be deployed in ISV. However as per request I couldn’t use the default organization,
so I need to change the url from:
http://(server-name)/ISV/(app-name)
to:
http://(server-name)/(organization-name)/ISV/(app-name)

The problem is my current web.config couldn’t be loaded properly. I got empty configuration even I use existing configuration from other project that use the same CRM.
After a chat with my work mate, he come accoss to Janne Mattila’s blog and I found the solution.

That’s a relief, yet not the end of the problem. I have a project that contains all CRM functions there. The solution above only applicable if I use those functions in one project, unfortunately I use it accross several projects.
So after some time and a chat with my work mate again we come into a solution:

1. I create a function in the config class that I use for the projects

public static void LoadCustomConfigFile()
{
// open the configuration on this specific path
Configuration configuration = WebConfigurationManager.OpenWebConfiguration("/ISV/");

// get all configuration that starts with "Crm" keyword - use "Crm" keyword for Crm related settings
var crmConfigurationKeys = configuration.AppSettings.Settings.AllKeys.Where(k => k.StartsWith("Crm")).ToList();

foreach (var crmKey in crmConfigurationKeys)
{
ConfigurationManager.AppSettings.Set(crmKey, configuration.AppSettings.Settings[crmKey].Value);
}
}

2. On page load event in the ISV application

protected void Page_Load(object sender, EventArgs e)
{
// Load custom config
Config.LoadCustomConfigFile();

// do the rest of page load event
}