Thursday, June 25, 2009

Creation of Shortcut to record in Microsoft Dynamics CRM 4.0 in Workflows

There are a lot of such tasks to create shortcut of record which had initialized a workflow execution to be used in email notifications.

Idea of realization of such functionality is not mine. Author of idea - Artem 'Enot' Grunin (Артем Enot Грунин) and I'm very appreciated to him for his bright ideas, help and criticism.

Tuesday, June 23, 2009

Data Audit Manager for Microsoft Dynamics CRM 4,0

I know that there are a lot of similar and free solutions but I decided to have this solution in my exploration portfolio.

There are a lot of codes in the article, so If somebody wants to retrieve code you should leave comment. :)

Monday, June 22, 2009

Personal Default Views Manager for Microsoft Dynamics CRM 4.0

The customer wants to make a personal setting for views according to next scenario.
Default account view is 'Active Accounts' for Tom, and 'My Active Accounts' view is default for Peter.

I've developed a little wizard and I would like to share it.

Tuesday, June 02, 2009

Offtopic.

This is video of Royal Irish Rangers Airsoft Team, Kyyiv, Ukraine. I'm from this team. I hope this video will be interesting for you.

Monday, June 01, 2009

Field Security Level For Microsoft Dynamics CRM 4.0 With Own Hands

Following article describes how to create mechanism which provides/restricts access to see fields of records in edit form/print preview/grids.

Idea:
1. Creation two custom entities - Field Security Level(contains name of entity to restrict access to fields and Business Unit for which restriction will be operate) and Field Security Level Attribute (contains Attribute Name and Bit flag - Access Allowed/Disallowed).
Field Security Level entity is parent to Field Security Level Attribute. Both entities are organization owned.
2. Field Security Level form scripting.
3. Writing a plugin which will create Field Security Level Attributes for just created Field Security Level based on entity name.
4. Writing a base class which will retrieve fields restriction for entity.
5. Writing a plugin which will handle Execute message, retrieve entity name and modify request to prevent appearance of 'forbidden' columns.
6. Writing a plugin which will handle Retrieve message, retrieve entity name and modify request to prevent appearance of 'forbidden' columns.
7. Writing a plugin which will handle RetrieveMultiple message, retrieve entity name and modify request to prevent appearance of 'forbidden' columns.