CONTACTOS

“Data is not information, Information is not knowl

Last weekend I found myself staring at a Gmail inbox with about 30 emails in it, and about 20 of those requiring some action.  Right about the same time I noticed the release of a Firefox plugin for applying GTD to Gmail – GTDGmail.  GTDGmail is a greasemonkey-style mashup on GMail that combines some client-side cleverness with GMail’s powerful labeling and filtering mechanisms to deliver a comprehensive GTD inbox system.  It uses what I think is probably a little-known feature in GMail – you can send emails to username+label@gmail.com to have GMail automatically apply a label to an incoming message or to apply special filtering rules to the message.

There has been a ton of chatter lately about using Outlook (especially the beta Outlook 2007) for managing GTD.  I own the Getting Things Done Outlook Add-In, but was eager to abandon it as it added instability to Outlook and I found that the only feature I really used was the “snooze” capability (not a good habit to get into). Melissa Macbeth wrote the article Outlook 2007 and Getting Things Done, Simon Guest expanded on those concepts in his article Implementing Getting Things Done using Outlook 2007, Omar Shahine expanded on those concepts with an improved macro, and finally Scott Hanselman recently published a podcast on A Better Outlook, including GTD add-ons for Outlook.

CardScan for CRM products do not include contact databases of their own.

Search for copies of your page on the Web.

O conhecimento distingue-se da mera informação porque está associado a uma intencionalidade.

O conhecimento não pode ser inserido num computador por meio de uma representação

podemos então olhar o conhecimento como uma atividade intelectual através da qual é feita a apreensão de algo exterior à pessoa.

desenvolvimento social e económico onde a informação, como meio de criação de conhecimento, desempenha um papel fundamental na produção de riqueza e na contribuição para o bem-estar e qualidade de vida dos cidadãos.

todos poderem aceder às Tecnologias de Informação e Comunicação

Com o nascimento de um novo sector, denominado de quaternário, cujo bem mais importante é a informação, assistimos a mudanças profundas na sociedade

// Check
Current User Security Roles and hide tab / field / Button base on
that

Here is some code for Javascript in CRM 4.0 I
am using , it will help you to hide/ disable Tab, Field, Section using
Javascript in CRM 4.0

// pass string of role like Sales Person,/
Administrator and check if that is role exist
function
CheckCurrentRole()
{

//

var userXml =
GetUserRoles();
if(userXml != null)
{
//select the node text
var
allRoles = userXml.selectNodes("//BusinessEntity/q1:name");
if(allRoles !=
null)
{
for(int i = 0; i < text ="="" visibility = "hidden" position =
"absolute" text ="="" lisdocument ="
document.getElementsByTagName('LI');
}
j= j +
1;
}

}
}}}
}

function GetUserRoles(){

// define
XML for retrieve query, for more ask me if you have to buid any query
regarding
var xmlQuery = "" + "" + "

Customize
CRM Data right inside Visual Studio 2005
This article describes
frequently used application code which uses the Microsoft CRM SDK into Visual
Studio.net 2005 code snippets. By creating a library of standard code snippets
which make use of the Microsoft CRM SDK, you can reduce the amount of time
required to develop Microsoft CRM related applications and also reduce the
number of potential bugs introduced into your code!

Use Visual
Studio 2005 to build CRM Callouts!
As many of you know that A callout is
custom code which uses the Microsoft CRM SDK to extend and customize the core
functionality of the Microsoft CRM product. Up until now, callouts had to be
developed using Visual Studio .NET 2003 and not Visual Studio 2005. This article
shows you how to write Microsoft CRM callouts using Visual Studio 2005! This is
great article about writing call outs in VS 2005. But for compiling still
required .Net 1.1.

Occasionally it's a good idea to run sp_updatestats or UPDATE STATISTICS.

Since re-indexing changes the statistics results, I recommend that after
re-indexing, you manually run sp_updatestats or the T-SQL UPDATE STATISTICS
command

<!-- /info -->
It seems regular expressions come up a lot when someone mentions validating email addresses. Curiously, and just as incorrect in my opinion, regex are also mentioned in the same sentence as parsing HTML. Notice the parsing bit, but that's not the topic of this post.

I've presented on the topic of regular expressions a number of times at usergroups and I always put up a slide showing this regex. It's the regex used by the Perl module Mail::RFC822::Address and it's nasty.

My problem with validating email addresses is even though it conforms to the spec does not mean it's an active, valid address and worse may not even belong to the user.

So it seems we'd want to:
1. Catch simple mistakes to make a better user experience.
2. Have a valid email address that can be used.
3. Make sure the email belongs to the user.

So how do we do that?
1. We could use a simple regex that's not too restrictive to make sure it generally looks like an email address (something @ something probably with a .) We could also make the user type their email address twice, verifying it the same way we would make them verify their password. A quick check on equality either means they didn't make a mistake, they consistently make that mistake in which case this hasn't helped us, or they copied and pasted it.

2. We could use a really nasty regex. We could shoot off an external process that tries to verify the email address through the mail server of its domain. We could send some url with a hash and have the user confirm their email. An ongoing part of this solution might also be to cull through bounce mail from the server and invalidate the address.

3. I really don't know how else to do this besides mailing the user something and requiring them to do something based on the contents of the email. This is the option from #2 above with the email containing a url and some hash. Do this every time you get a new email address and you should be fairly confident that you can send email address to the user.

My thought on this whole thing is: Why collect the data if you're not going to use it; and why just guess at it's validity when you could confirm it through user action?

Remarks

Important: You should always consider the form type in your code. In particular, consider how your code will work in the Quick create and Bulk edit forms.

The Quick create form only includes business required or business recommended fields.

If your code references a field that is not on the Quick create form, an error will occur. If your business logic requires certain fields to be present, you should set the Business Recommended constraint so that they will appear in the quick create form.

The Bulk edit form will not include existing data for each record that will be updated. If your business logic depends on specific data for each record to be present in the form, you may want to set specific conditions on which fields you will allow to be updated using the Bulk edit form

Filter data in a CRM lookup field