xRM Consultant

Hi,

As much as I like the look and feel of CRM when you are developing a true xRM solution for a client, as we all know, less can be more.

With this in mind, whilst developing a solution for a client recently, I wanted to hide the entire left-hand navigation menu to give my form a simpler feel to it. So when setting it up I used 2 handy little pieces of JavaScript.

The first resized the window, OnLoad, to the size I wanted for my form:

window.resizeTo(700,520);

This gave me the following OnLoad:

As you can see though, most of the screen is taken up with the Left Navigation are, which for this form I didn't need.  So, i hid it using the following code:

document.all.crmNavBar.parentElement.style.display = "none";
document.all.tdAreas.colSpan = 2;

Which game me the following results….

As I said, nice simple JavaScript but I think it makes a huge difference to the appearance of the form and therefore (hopefully) how well the user interacts with it.

Enjoy!

Joel

Hi,

Very pleased to say I have just booked to go to Convergence 2010 Europe.

Got to be honest, never been before but very much looking forward to meeting different people within the Dynamics Community, exchanging ideas etc.

I have been searching for good Dynamics CRM events or even CRM events to keep my knowledge up to date without much joy at the moment. Please feel free to get in touch if you have any recommendations by email (xrmconsultant@gmail.com) or twitter (@xrmconsultant)

Hope to see you there,

Joel

Hi,

Quick but useful piece of JavaScript for you. Put this in the OnLoad event of any CRM form and it will maximise the window to fill your current screen size. Handy eh?!

window.moveTo(0,0);

window.resizeTo(screen.availWidth, screen.availHeight);

Enjoy!

Joel

Howdy,

A customer contacted us today as they were getting a large number of Sync Issues in their outlook Sync Issues folder that relate to CRM. Puzzled and baffled we were…

After a bit of searching we found that this is a known issue that had been fixed as part of recent (10) update roll-ups.

The issue is caused when: (From Microsoft KB Article)

• You share a calendar or a contacts folder in Microsoft Office Outlook with another user.
• You and the user who you shared the calendar or the contact folder with are Microsoft Dynamics CRM 4.0 users.
• Both of you have the CRM Outlook client online or offline.
• The shared calendar or the shared contacts folder contains items that are tracked in Microsoft Dynamics CRM.

In this scenario, the person who is viewing the shared calendar or the shared contacts folder will receive Outlook sync messages in the Sync Issues folder for their mailbox. The sync issue resembles the following:

This item was not completely updated during the last server synchronization. Click here to review other versions.A

Additionally, the items may become untracked if the following conditions are true:

• The person who you shared the calendar or the contacts folder with does not track items in Outlook to Microsoft Dynamics CRM.
• The user has Write privileges to the shared data in Outlook.

CRM obviously struggles to resolved what it is viewing in outlook against the current active user profile within CRM.

Applying the update roll-up resolves this issue and stops your users Sync Issues box filling up. In addition it reduces the considerable performance overhead that this would cause

Hope this helps

Thanks

Joel

Morning,

One thing that always used to wind me right up was the fact that once you hit save to create an entity in MSDYNCRM, you could not change any details about the primary attribute.

 

However, after a bit of searching i found this blog on the Microsoft Dynamics Community site that was very helpful. 

Modifying properties of primary attribute is disabled when you try to do it from “Primary Attribute” tab. However you can change the properties if you opened the attribute from Attributes left navigation instead.

1. Go to Attributes and select “name” i.e. primary attribute of entity. As shown in below screen shot.

2. Open primary attribute i.e. name and change its Requirement Level to “No Constraint” then Save and Close.

3. The changes will also get reflected in Primary Attribute tab. Publish account and test the changes.

Brilliant eh?! Above you have seen how to change the requirement level but this obviously also applies to the display name of the entity. This is particularly handy if you are renaming entities.

Thanks

Joel