The company I work for Crimson Ltd have obviously always had a website which no one from the company ever looked at (why would you) but have recently created a company blog as well.
I looked at the CRM part of the company website this week to see what was actually on it – http://www.crimson.co.uk/CRM.aspx, I actually thought this looked quite good, professional, to the point but I wondered when would people look at the site, probably after a introduction had already been done and they were doing some home work on the company.
I have talked about the benefits of blogs before and you can read that here, the power of blogging. I think having a company blog is a good idea, it’s an opportunity for the company (Crimson Ltd) to mention their successes, innovative solutions. It also has the benefit of raising their profile and the opportunity to help the CRM community by blogging the solution to a problem and people finding that solution on the blog.
The other interesting feature of a company blog is it will contain blog posts from a collection of people skilled in different areas. Crimson has a lot of talented people in various areas so they should have a lots of material for the blog, although persuading the people to contribute might be a bit tricky to start with but people will soon get into the flow of things.
A side bonus to the blog is it’s an area to show employees and current customers what services we offer and what we have been doing.
There isn’t much on the blog at the moment but in the future it will be filled with interesting posts and I’m not just talking about my posts either :-).
Click here to look at the blog but I think you might want to check it later when we have put some interesting posts in it.
The other day I was trying to find information on the Subject Tree, you can read the entry – crm 2011 importing and exporting the Subject Tree, I was dicussing the problem with a colleague and he dug out this document about the relationships of the entities in CRM, he said he thought he had this document from before CRM 4.
I found the document on line and it had some useful information with it
Migration Entity Reference
The link talks about migrating entities from different version of CRM, how to map it and how to use the data migration manager.
This part was interesting
To ensure a successful migration, you need to prepare your source data so that it can be mapped to Microsoft Dynamics CRM. For additional reference, the Data Migration Manager Help file describes specific tasks for each type of entity, and each type of attribute. This article provides information to complement the information in Help. At the end of this article is a link to a Microsoft Office Excel spreadsheet that lists the entities and attributes. For each default entity that can have data migrated to it, the following attributes are listed:
- Required. Source files should have one column for each required attribute in the Microsoft Dynamics CRM entity. All records must have data in each of these columns.
- Relationship. If you want to connect one record to a record in another record type, you must have a column in your source file for the data that creates the relationship. If there is no data in a relationship column, the record will not be connected.
- Calculated. Data in calculated attributes is not migrated. Instead, when the data used for the calculation is migrated, Microsoft Dynamics CRM does the calculation and populates the attribute. You should identify any columns in your source data that map to calculated attributes, so that you can select Ignore
Why am I talking about this I hear you ask, well I initially looked at the subject and it’s still the same and it helped me work out what the entity references were (e.g. lookups) and what I needed to call them.
You can download the Entity reference for all the default entities in a nice handy excel document by clicking the link below, it’s displayed in an easy to understand format
Entity reference for default (uncustomized) entities
Click to open the Excel spreadsheet that lists the entities and attributes.