Here’s a great article on how to create a report for beginners:
Introduction to create a simple report Thursday, Jun 29 2006
Microsoft CRM and SQL Reporting Services 2:58 pm
Copying Ship To Address to Bill To Address Tuesday, Jun 6 2006
Microsoft CRM 8:50 am
Do you have Billing and Shipping Addresses on any of your forms? Do you have customers that keep asking if there is a way to click a button and copy the address from one to the other if they are the same? Well, here is a sample piece of code I built that will do just that. This assumes that you are making the Billing Address the same as the Shipping Address, but you can modify it to fit any scenario and adjust the fields included as needed.
Thanks to David Pritchett from ePartners to providing me with this code for the blog.
1) Create an attribute (I used a bit –Yes/No). Call it something like “Billing Same As Shipping.”
2) Put this attribute on your form where the addresses are.
3) Add the following code to the OnChange event of this new attribute and enable:
/* Declare your variables to store the data from the Address fields on the form so we can reference them later */
var osaddress1_line1 = document.crmForm.all.address1_line1.DataValue;
var osaddress1_line2 = document.crmForm.all.address1_line2.DataValue;
var osaddress1_line3 = document.crmForm.all.address1_line3.DataValue;
var osaddress1_city = document.crmForm.all.address1_city.DataValue;
var osaddress1_stateorprovince = document.crmForm.all.address1_stateorprovince.DataValue;
var osaddress1_county = document.crmForm.all.address1_county.DataValue;
var osaddress1_postalcode = document.crmForm.all.address1_postalcode.DataValue;
var osaddress1_country = document.crmForm.all.address1_country.DataValue;
var osaddress1_fax = document.crmForm.all.address1_fax.DataValue;
var osaddress1_telephone = document.crmForm.all.address1_telephone1.DataValue;
/* Declare your variable to capture the data from the attribute being changed – Billing Same As Shipping in this case */
var oField = event.srcElement;
/* If the value of the Billing Same As Shipping field you captured is 1 (Yes), then update all of the corresponding Billing Address fields with the data from the Address fields */
if (oField.DataValue == 1)
{
document.crmForm.all.address2_line1.DataValue = osaddress1_line1;
document.crmForm.all.address2_line2.DataValue = osaddress1_line2;
document.crmForm.all.address2_line3.DataValue = osaddress1_line3;
document.crmForm.all.address2_city.DataValue= osaddress1_city;
document.crmForm.all.address2_stateorprovince.DataValue = osaddress1_stateorprovince;
document.crmForm.all.address2_county.DataValue = osaddress1_county;
document.crmForm.all.address2_postalcode.DataValue = osaddress1_postalcode;
document.crmForm.all.address2_country.DataValue = osaddress1_country;
document.crmForm.all.address2_fax.DataValue = osaddress1_fax;
document.crmForm.all.address2_telephone1.DataValue = osaddress1_telephone;
}
There you have it! All of the data from the Shipping Address fields will be copied to the Billing Address fields when you select the “Yes” option on your new attribute.
Enjoy!
Author: Ben Vollmer
Src: http://blogs.msdn.com/MidAtlanticCRM/
Gridview with Object Data Source Friday, May 19 2006
ASP.NET 2.0 7:41 am
How to add a Login, Roles and Profiles system Thursday, May 11 2006
ASP.NET 2.0 9:57 am
Membership/Role Management using Object Data Source Wednesday, May 10 2006
ASP.NET 2.0 7:48 pm
You can find articles and source code here for membership/role management using Object Data Source/ASP.NET 2.0
Deploying Web Application to Tomcat 4.0 Wednesday, May 10 2006
J2EE 7:42 pm
Deploying Web Applications to Tomcat by James Goodwill — James Goodwill takes us through the web application deployment process for the Apache Tomcat Web server.
Accessing the different controls inside a GridView control Wednesday, May 10 2006
ASP.NET 2.0 9:08 am
Are you curious on how to access label, text box or other controls in Gridview? I have found an article showing all the details. If you are too curious, click here
How to remove duplicate rows from a table in SQL Server Wednesday, May 3 2006
Microsoft SQL 4:36 pm
SUMMARY
Microsoft SQL Server tables should never contain duplicate rows, nor non-unique primary keys. For brevity, we will sometimes refer to primary keys as "key" or "PK" in this article, but this will always denote "primary key." Duplicate PKs are a violation of entity integrity, and should be disallowed in a relational system. SQL Server has various mechanisms for enforcing entity integrity, including indexes, UNIQUE constraints, PRIMARY KEY constraints, and triggers.
Despite this, under unusual circumstances duplicate primary keys may occur, and if so they must be eliminated. One way they can occur is if duplicate PKs exist in non-relational data outside SQL Server, and the data is imported while PK uniqueness is not being enforced. Another way they can occur is through a database design error, such as not enforcing entity integrity on each table.
Often duplicate PKs are noticed when you attempt to create a unique index, which will abort if duplicate keys are found. This message is:
Msg 1505, Level 16, State 1 Create unique index aborted on duplicate key.
If you are using SQL Server 2000 or SQL Server 2005, you may receive the following error message:
Msg 1505, Level 16, State 1 CREATE UNIQUE INDEX terminated because a duplicate key was found for object name '%.*ls' and index name '%.*ls'. The duplicate key value is %ls.
This article discusses how to locate and remove duplicate primary keys from a table. However, you should closely examine the process which allowed the duplicates to happen in order to prevent a recurrence.
Displaying Master-Detail Data in ASP.NET 2.0 Wednesday, Apr 12 2006
ASP.NET 2.0 9:18 am
In this tutorial you will learn how to display Master-Detail Data on Separate Pages, create the details page, test the pages and Allow Editing, Deleting, and Inserting Using a DetailsView DataBound control.A variation of the GridView and DetailsView control is the display on separate pages. Each record has an hyperlink which enables them to navigate to a second page where they can view the detail records in a DetailsView control…more>> http://www.exforsys.com/content/view/1657/240/
Creating N-tier Web Application Using Visual Studio 2005 Wednesday, Apr 5 2006
Visual Studio 3:29 pm
I've found a great article to create a web application using Visual Studio 2005.
The author writes, "When .NET Framework was first introduced, it provided excellent features that made the construction of ASP.NET applications a breezy experience. Now the next version of .NET Framework (version 2.0) along with SQL Server 2005 builds on the foundation of the previous versions and introduces some new features that can greatly aid in the design and development of N-Tier ASP.NET 2.0 applications. In this article, I will show you to how to construct an N-Tier ASP.NET 2.0 Web application by leveraging the new features of ASP.NET 2.0 and SQL Server 2005 such as TableAdapter Configuration Wizard, ObjectDataSource Control, App_Code directory to store reusable components, Master Pages, CLR Stored Procedures, and Caching. Along the way, I will also highlight the best practices of using the new ASP.NET features for building N-Tier enterprise class Web applications. From an implementation standpoint, Part-1 of this article will focus on the creation of CLR stored procedures and the data access components in addition to describing the overall architecture of the sample application. Part-2 will focus on the business logic layer object, ASP.NET user interface pages, caching and so on."
Click here to read more about the article
