1. From the Windows Start menu select Administrative Tools | Computer Management. If this menu item does not exist, you are either not an administrator for the computer or the server is a domain controller and you need to create a domain user instead.
2. From the Computer Management dialog, navigate to System Tools | Local Users and Groups | Users on the left panel; right click on Users and select New user from the popup menu.
3. In the New User dialog, enter prtracker, PR-Tracker and Problem Tracking System for the User name, Full name and Description, respectively.
4. Uncheck box User must change password at next login and then check box Password Never Expires.
5. Click the Create button to create the user and then click Close button.
6. Optional steps follow: double-click the prtracker username on the right panel.
7. From the prtracker Properties dialog, select tab Member Of and click the Add button.
8. From the Select Groups dialog and in the Name box, type Administrators and click the OK button. Also, add prtracker user to be member of DCOM User Group.

Note that optional steps 6, 7 and 8 are only recommended if you plan to use SQL Server as your database provider. Even if you do plan to use SQL Server as the database provider, these steps are optional if you choose to configure the server roles in SQL Server instead.

1. From the Windows Start menu select Administrative Tools | Active Directory Users and Computers. If this menu item does not exist, the server is not a domain controller and you should create a local user instead.
2. From the Active Directory Users and Computers dialog, navigate to Users on the left panel; right click on Users and select New | User from the popup menu.
3. In the New Object – User dialog, enter PR-Tracker and prtracker for the First name and User logon name, respectively.
4. In next dialog check box Password never expires.

Create failed for Login ‘xxx’. (Microsoft.SqlServer.Express.Smo)
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

The MUST_CHANGE option is not supported by this version of Microsoft Windows. (Microsoft SQL Server, Error: 15195)

What i do is uncheck the “Enforce password policy” when create the new user. This way you will not get the error message, but this is not the recommended way for the production Login Name and Password.

Problem solved.

Here is a list of some of the more common date functions:

fn_BeginOfDay
fn_BeginOfHour
fn_BeginOfLastMonth
fn_BeginOfLastSevenDay
fn_BeginOfLastWeek
fn_BeginOfLastXDay
fn_BeginOfLastXHour
fn_BeginOfLastXWeek
fn_BeginOfLastYear
fn_BeginOfMonth
fn_BeginOfNextMonth
fn_BeginOfNextWeek
fn_BeginOfNextYear
fn_BeginOfThisMonth
fn_BeginOfThisWeek
fn_BeginOfThisYear
fn_BeginOfToday
fn_BeginOfTomorrow
fn_BeginOfWeek
fn_BeginOfYear
fn_BeginOfYesterday
fn_EndOfLastMonth
fn_EndOfLastWeek
fn_EndOfLastYear
fn_EndOfNextMonth
fn_EndOfNextSevenDay
fn_EndOfNextWeek
fn_EndOfNextXDay
fn_EndOfNextXHour
fn_EndOfNextXWeek
fn_EndOfNextYear
fn_EndOfThisMonth
fn_EndOfThisWeek
fn_EndOfThisYear
fn_EndOfToday
fn_EndOfTomorrow
fn_EndOfYesterday
fn_FirstDayOfMonth
fn_LastXMonth
fn_LastXYear
fn_LocalTimeToUTC
fn_NextXMonth
fn_NextXYear
fn_NTDayOfWeek

If you would like to see these functions in action, copy the following script into SQL Management Studio and run it ( after connecting to the CRM database ):

select ‘fn_BeginOfDay’ as “Function”, dbo.fn_BeginOfDay(GetDate()) as “Value”
union
select ‘fn_BeginOfHour’, dbo.fn_BeginOfHour(GetDate())
union
select ‘fn_BeginOfLastMonth’, dbo.fn_BeginOfLastMonth(GetDate())
union
select ‘fn_BeginOfLastSevenDay’, dbo.fn_BeginOfLastSevenDay(GetDate())
union
select ‘fn_BeginOfLastWeek’, dbo.fn_BeginOfLastWeek(GetDate())
union
select ‘fn_BeginOfLastXDay’, dbo.fn_BeginOfLastXDay(GetDate(), 1)
union
select ‘fn_BeginOfLastXHour’, dbo.fn_BeginOfLastXHour(GetDate(), 1)
union
select ‘fn_BeginOfLastXWeek’, dbo.fn_BeginOfLastXWeek(GetDate(), 2)
union
select ‘fn_BeginOfLastYear’, dbo.fn_BeginOfLastYear(GetDate())
union
select ‘fn_BeginOfMonth’, dbo.fn_BeginOfMonth(GetDate())
union
select ‘fn_BeginOfNextMonth’, dbo.fn_BeginOfNextMonth(GetDate())
union
select ‘fn_BeginOfNextWeek’, dbo.fn_BeginOfNextWeek(GetDate())
union
select ‘fn_BeginOfNextYear’, dbo.fn_BeginOfNextYear(GetDate())
union
select ‘fn_BeginOfThisMonth’, dbo.fn_BeginOfThisMonth(GetDate())
union
select ‘fn_BeginOfThisWeek’, dbo.fn_BeginOfThisWeek(GetDate())
union
select ‘fn_BeginOfThisYear’, dbo.fn_BeginOfThisYear(GetDate())
union
select ‘fn_BeginOfToday’, dbo.fn_BeginOfToday(GetDate())
union
select ‘fn_BeginOfTomorrow’, dbo.fn_BeginOfTomorrow(GetDate())
union
select ‘fn_BeginOfWeek’, dbo.fn_BeginOfWeek(GetDate())
union
select ‘fn_BeginOfYear’, dbo.fn_BeginOfYear(GetDate())
union
select ‘fn_BeginOfYesterday’, dbo.fn_BeginOfYesterday(GetDate())
union
select ‘fn_EndOfLastMonth’, dbo.fn_EndOfLastMonth(GetDate())
union
select ‘fn_EndOfLastWeek’, dbo.fn_EndOfLastWeek(GetDate())
union
select ‘fn_EndOfLastYear’, dbo.fn_EndOfLastYear(GetDate())
union
select ‘fn_EndOfNextMonth’, dbo.fn_EndOfNextMonth(GetDate())
union
select ‘fn_EndOfNextSevenDay’, dbo.fn_EndOfNextSevenDay(GetDate())
union
select ‘fn_EndOfNextWeek’, dbo.fn_EndOfNextWeek(GetDate())
union
select ‘fn_EndOfNextXDay’, dbo.fn_EndOfNextXDay(GetDate(), 1)
union
select ‘fn_EndOfNextXHour’, dbo.fn_EndOfNextXHour(GetDate(), 1)
union
select ‘fn_EndOfNextXWeek’, dbo.fn_EndOfNextXWeek(GetDate(), 1)
union
select ‘fn_EndOfNextYear’, dbo.fn_EndOfNextYear(GetDate())
union
select ‘fn_EndOfThisMonth’, dbo.fn_EndOfThisMonth(GetDate())
union
select ‘fn_EndOfThisWeek’, dbo.fn_EndOfThisWeek(GetDate())
union
select ‘fn_EndOfThisYear’, dbo.fn_EndOfThisYear(GetDate())
union
select ‘fn_EndOfToday’, dbo.fn_EndOfToday(GetDate())
union
select ‘fn_EndOfTomorrow’, dbo.fn_EndOfTomorrow(GetDate())
union
select ‘fn_EndOfYesterday’, dbo.fn_EndOfYesterday(GetDate())
union
select ‘fn_FirstDayOfMonth’, dbo.fn_FirstDayOfMonth(GetDate(), 10)
union
select ‘fn_LastXMonth’, dbo.fn_LastXMonth(GetDate(), 1)
union
select ‘fn_LastXYear’, dbo.fn_LastXYear(GetDate(), 1)
union
select ‘fn_NextXMonth’, dbo.fn_NextXMonth(GetDate(), 1)
union
select ‘fn_NextXYear’, dbo.fn_NextXYear(GetDate(), 1)

if ( crmForm.all.customerid != null )
{
crmForm.all.customerid .setAttribute(”defaulttype”, “2″);
}

Remember to enable the event and then save and publish the opportunity entity.

Following are codes of basic entities of Microsoft CRM 3 ;

* Account 1
* Contact 2
* Lead 4

Here we go. Add following line in onLoad of opportunity entity form. It will work for atleast the lookup window.
crmForm.all.customerid.setAttribute(”lookuptypes”, “1″);

Lets say you have a DynamicEntity object and you need to clear one of the values in a plugin, for example the parentid of a contact. Normally, to add an attribute to a DynamicEntity you would use the entity.Properties.Add(…) method, but the problem is that CRM only processes values that has a value.

What I tried initially was to remove the value using the entity.Properties.Remove(attributename) method. This did delete the attribute, but on saving the DynamicEntity, it did not save this attribute to the server but instead left it the way it was.

What Patrick suggested was to use the null value coupled with each crm attribute type, example CrmDateTime.Null or CrmNumber.Null. So what I did was to add the null value to the PropertyBag and set the acctual value to null.

entity.Properties.Add(new CrmDateTimeProperty(CrmDateTime.Null));

What is very important here is that each attribute type has it’s own Null value, you cannot interchange CrmDateTime.Null and CrmNumber.Null.

The only exception to this seems to be a string type attribute, you only need to assign the value as an empty string “”. Note that you may also be able to use the String.Empty method, I have not tried this yes but would say that this should also work.

So here is the scenario, you have a picklist (or any other field) and you want to show and hide other fields based on this. Let’s say your picklist field is called “mypicklist” and you have two other fields, one is a text field called “mytextfield” and one is a lookup called “mylookup”. The values in the picklist are “Show Text Field”, with a value of 1 and “Show Lookup Field” with a value of 2. You want to show/hide the fields accordingly.

Firstly you need to write the following code in the mypicklist onChange event:

if (crmForm.all.mypicklist.DataValue == 1) //show text field
{
//hide the lookup
crmForm.all.mylookup.style.display = ‘none’;
crmForm.all.mylookup_c.style.display = ‘none’; //note the _c
crmForm.all.mylookup_d.style.display = ‘none’; //note the _d, only required for lookups

//show the text field
crmForm.all.mytextfield.style.display = ‘inline’;
crmForm.all.mytextfield_c.style.display = ‘inline’; //note the _c
}
else if (crmForm.all.mypicklist.DataValue == 2) //show loookup
{
//hide the lookup
crmForm.all.mylookup.style.display = ‘inline’;
crmForm.all.mylookup_c.style.display = ‘inline’; //note the _c
crmForm.all.mylookup_d.style.display = ‘inline’; //note the _d, only required for lookups

//show the text field
crmForm.all.mytextfield.style.display = ‘none’;
crmForm.all.mytextfield_c.style.display = ‘none’; //note the _c
}
else // hide all
{
//hide the lookup crmForm.all.mylookup.style.display = ‘none’;
crmForm.all.mylookup_c.style.display = ‘none’; //note the _c
crmForm.all.mylookup_d.style.display = ‘none’; //note the _d, only required for lookups

//show the text field
crmForm.all.mytextfield.style.display = ‘none’;
crmForm.all.mytextfield_c.style.display = ‘none’; //note the _c
}

As you can see, each field has two (three for lookups) sections that has to be hidden, the first section is identified by the field schema name and represents the textbox area. The second, represented by the fieldname following by an “_c” represents the label area. Lookups also has an additional area, replresented by the fieldname followed by an “_d” which represents the lookup button. Each of these sections needs to be shown/hidden individually.

The second part is ensuring these are hidden/shown after they are saved, so the exact same code above needs to be placed in the form load event too. It may also make your life easier to create a global function in the onload event and then call this function from both within the onload event and the picklist onchange event. Something like:

ShowHideField = function()
{
//all the above code goes in here
}

// then call the above in both the onload and the relevent onchange event
ShowHideField();

The above goes for most field types and you can also show or hide fields based on whether they contain data or not with the following:

if (crmForm.all.mypicklist.DataValue != null) //show text field
{
…
}

Lets say you have a DynamicEntity object and you need to clear one of the values in a plugin, for example the parentid of a contact. Normally, to add an attribute to a DynamicEntity you would use the entity.Properties.Add(…) method, but the problem is that CRM only processes values that has a value.

What I tried initially was to remove the value using the entity.Properties.Remove(attributename) method. This did delete the attribute, but on saving the DynamicEntity, it did not save this attribute to the server but instead left it the way it was.

What Patrick suggested was to use the null value coupled with each crm attribute type, example CrmDateTime.Null or CrmNumber.Null. So what I did was to add the null value to the PropertyBag and set the acctual value to null.

entity.Properties.Add(new CrmDateTimeProperty(CrmDateTime.Null));

What is very important here is that each attribute type has it’s own Null value, you cannot interchange CrmDateTime.Null and CrmNumber.Null.

The only exception to this seems to be a string type attribute, you only need to assign the value as an empty string “”. Note that you may also be able to use the String.Empty method, I have not tried this yes but would say that this should also work.

 The asp:CustomValidator tag looks like this :

Server Side Validation:

Protected void FunctionToValidateAtServer(object sender, ServerValidateEventArgs e)

{ If (Controls are Valid) e.IsValid = true; else e.IsValid = false; }

Client Side validation:

Function JavaScriptValidationFunction(source, args)

{ If (controls are valid) e.IsValid = true; else args.IsValid = false; }

Till this I used to write the code. But what I used to miss is written below. So never forget to write this code when we write custom validators.

<script type=”text/javascript”>

<!–

  ValidatorHookupControlID(“<%= controlTobeValidated1.ClientID %>”,

     document.all["<%= cutomValidatorToRespond.ClientID %>"]);

  ValidatorHookupControlID(“<%=controlTobeValidated2.ClientID %>”,

     document.all["<%=cutomValidatorToRespond.ClientID %>"]);

     …

//–>

</script>

 <!–
ValidatorHookupControlID(“”,

document.all[""]);

ValidatorHookupControlID(“”,

document.all[""]);

…
// –>This is where the magic happens… This informs the built invalidation subroutines to update validation whenever one of these controls change. You can easily add as many controls as needed to a single validator’s dependencies. The ValidatorHookupControlID function is part of the standard Microsoft validation scripts.

Use of ICallbackEventHandler:

To use ICallbackEventHandler, we will need to inherit it on the page or in a user control. The code will for this will be:

public partial class Default2 : System.Web.UI.Page,System.Web.UI.ICallbackEventHandler

As a result of inheriting from ICallbackEventHandler, we have to implement two functions, namely:

* public void RaiseCallbackEvent(String eventArgument)

* public String GetCallbackResult()

As name of the above two functions indicates, the first function gets called automatically whenever there is a CallbackEvent. After the first function the second function i.e. GetCallbackResult gets called and returns a string to the client

So how to raise a CallbackEvent? For this we will have to use javascript. There will be two javascript functions:

1. A function which will call RaiseCallbackEvent.

2. A function which will handle the response from the server. This function will be called automatically after GetCallbackResult() and the string returned by GetCallbackResult will appear in JavaScript as input to this function.

Implementing ICallbackEventHandler

1. Create an ASPX page as follows
<form id=”form1″ runat=”server”>
<div>
Select The Item and Click the Button
<asp:DropDownList ID=”DropDownList1″ runat=”server”></asp:DropDownList>
<br />
<br />
<button type=”Button” onclick=”CheckForTimeZone()”>Get Timezone</button>
<br />
<table><tr>
<td>GMT Time zone is :</td>
<td><div id=”Results” runat=”server”></div></td>
</tr></table>
<br />
</div>
</form>

In above code “CheckForTimeZone()” in the button tag is a javascript function which we will add later. Also note that the button is a simple HTML control.

2. JavaScript in the Aspx page.

 <script type=”text/ecmascript”>

    function CheckForTimeZone()
{
var lb = document.getElementById(“DropDownList1″);
var selectedItem = lb.options[lb.selectedIndex].text;
CallServer(selectedItem, “”);
}

function ReceiveServerData(retValue)
{ 
document.getElementById(“Results”).innerHTML = retValue;
}

  </script>

In above code CallServer(selectedItem, “”) will be responsible for calling RaiseCallbackEvent on server side. And the ReceiveServerData(retValue) function gets called by GetCallbackResult().

To make above code work the way we want; we will need to add some code to the aspx.cs file.

3. Server-Side C# code (i.e. apsx.cs file)

public partial class Default2 : System.Web.UI.Page,System.Web.UI.ICallbackEventHandler

{

private static Hashtable hashTable;

protected String returnValue;

protected void Page_Load(object sender, EventArgs e)

{

if (!IsPostBack)

{

String cbReference =

Page.ClientScript.GetCallbackEventReference(this, “arg”, “ReceiveServerData”, “context”);

String callbackScript;

callbackScript = “function CallServer(arg, context)” +

“{ ” + cbReference + “;}”;

Page.ClientScript.RegisterClientScriptBlock(this.GetType(),

“CallServer”, callbackScript, true);

hashTable = new Hashtable();

hashTable.Add(“Hawaii”, “GMT -10:00″);

hashTable.Add(“Central America”, “GMT -06:00″);

hashTable.Add(“Greenland”, “GMT -03:00″);

hashTable.Add(“Athens”, “GMT +02:00″);

DropDownList1.DataSource = hashTable;

DropDownList1.DataTextField = “key”; //If you say value Values from HashTable will be added to Drpdownlist

DropDownList1.DataBind();

}

}

In the above code, please note the following:

String cbReference = Page.ClientScript.GetCallbackEventReference(this, “arg”, “ReceiveServerData”, “context”);

If we debug the code “cbReference” it will contain “WebForm_DoCallback(‘__Page’,arg,ReceiveServerData,context,null,false)

”; . Observe that the string, WebForm_DoCallback contains ReceiveServerData, it’s the javascript function we have written in step 2.

String callbackScript;

callbackScript = “function CallServer(arg, context)” + “{ ” + cbReference + “;}”;

Again “callbackScript” will contain some string. Actually it is a JavaScript function which we will register to the client page. Using

Page.ClientScript.RegisterClientScriptBlock(this.GetType(),”CallServer”, callbackScript, true);

This registers our CallServer function on the page. We are essentially passing the selected item of the Dropdown list to the CallServer function if you see the source code of the output page the CallServer function will appear as follows:

This CallServer function is responsible for raising the callbackEvent ( i.e. RaiseCallbackEvent(String eventArgument) ) and the “arg” will be the eventArgument.

4. Finally add RaisecallbackEvent and GetCallbackResult.

Add following code to aspx.cs file

public void RaiseCallbackEvent(String eventArgument)

{

if (hashTable[eventArgument] == null)

{

returnValue = “-1″;

}

else

{

returnValue = hashTable[eventArgument].ToString();

}

}

public String GetCallbackResult()

{

return returnValue;

}

The above code provides the basic plumbing to implement asynchronous callbacks using ICALLBACKEventHandler. In subsequent articles we will extend this to real world applications and develop an AJAX-enabled GridView control.

On page two I have a button using Response.Redirect(“pageone.aspx”) to go
back to page one.

When I view page one, select some information, then go to page two, and then
select the back button (using the response.redirect) none of my selections
remain. If I just use the back button of the web browser everything works
fine.

To get it to work like the back button, Instead of using Response.Redirect
to go back to page one you could execute some client side javascript like
this:
history.go(-1);

So you could have a “Back” anchor tag in your HTML that looks like this:
<a href=’javascript:history.go(-1);’>Back</a>

Here’s more info:
http://www.devguru.com/Technologies/…istory_go.html