Freigeben über


CRM Gadget - Don't lose time to search CRM data

Hi,

I share you the last version of the ‘CRM search gadget‘. We need beta testers to improve the tool. You can download it here.

This gadget was created to win time of search in CRM(especially during incoming phone calls ). Only one Input to retrieve any entities.

CRM Guide

Because this kind of tool is very useful/interesting for WW CRM Community, we decided (with Remi and Kelvin) to  create a generic solution. So You can use it in your company without coding anything.

You can easily personalize your own parameters in the gadget. If you have to add one entity or attributes to request on CRM.

Technologies Involved: Silverlight 2.0 RTM and CRM 4.0 Web Services.
OS: Vista and Windows Seven
Known issues: Doesn’t work on 64 bits OS
Installation: Double click on MSCRM.gadget file (here).

We’re waiting for feedbacks on design, functionalities and bugs !!!

Should you have any questions, please feel free to add a comment.

See you soon

PAF, Kelvin and Rémi

==============================================

Part 1 - Gadget UI

Step 1 – Enter what you’re looking for

Here, we’re looking for ‘Symtrax’ data in CRM

clip_image001

Step 2 – Result Panel

clip_image002

To copy data in your clip board, just click on labels.

Part 2 – Settings UI

‘CRM’ Tab

Here, you’ll be able to change the CRM target

clip_image004

‘Search’ Tab

Select entities and attributes you want to request.

clip_image005

‘Show’ Tab

Select entities and attributes you want to display in the result panel.

clip_image007

Comments

  • Anonymous
    May 13, 2009
    I tested the gadget and found that it will fail if the display name is different than the unique name. When making the requests to the metadataservice it uses the display name causing the request to fail.

  • Anonymous
    August 03, 2010
    Is there any future release planned support 64 bit OS'? Thx, Eo

  • Anonymous
    February 08, 2012
    Interesting tool. I will test as soon as our organisation will move to Seven (we are still in XP). 64 bits compliance should be considered - I doubt that any new PC will run a 32 bit OS...