crm.atechnisch.nl

A couple of times a month I read the question on a forum how to hide/disable the “Add Existing” button. Unfortunately nobody comes up with a suitable solution.Within my current project someone asked me the same question. My first reaction was that is not possible within the borders of Microsoft support we have committed ourselves to. Some moments later I realized the “Add Existing” button we were talking about was displayed in an iFrame. That is a different story.Based on a previous post, I am able to hide elements in an iFrame and this includes the “Add Existing” button. See picture below (for original form see other post).

The script I added is simple:

//hide the Add Existing button
if (objWindow.document.all._MBtoplocAssocOneToMany4200AccountActivityPointers !=null)
{
objWindow.document.all._MBtoplocAssocOneToMany4200AccountActivityPointers.style.display ='none';
}

 In my previous post you can read how to use it.

I know it does not solve the problem of hiding the “Add Existing” button on the Associated views, but in some cases it can be a way out.

(2 votes, average: 1.00 out of 7)

 Loading ...

I will be attending the Microsoft Worldwide Partner Conference 2008 in Houston Texas USA !!!
It’s my first time attending the conference.

My interest goes out to Microsoft Dynamics CRM and the combination with other Microsoft products. Besides the technical aspects I am very much interested in the Added Value for the Business and the Usability.

If you can reconment a session, an event or want to meet me in person, please let me know. 
Thanks in advance.

(1 votes, average: 1.00 out of 7)

 Loading ...

When it comes to the security roles I like to use roles based on a functionality instead of based on business roles.
In most companies employees with a similar business roles are allowed to do different things in the MS CRM system. Making exceptions is hard when you use role based security roles. Functionality roles on the other hand can be easily combined to create the right level of authorization.
A functionality based role can be, ‘Maintain Accounts’. A user with this role is allowed to read, write, append, append to, share and assign accounts on Business Unit level. Combined with ‘Maintain Contacts’ or ‘Create and Delete Account’, etc, gives a complete set of functionality.
Next to these clear functionality roles a user needs in general a basic role to be able to use the MS CRM basic functionality. For example the ‘Set Regarding’ functionality to link a email to a record in MS CRM.
When designing the basic use role I came across some oddities I couldn’t directly explain. Users with the basic role should be allowed to use the ‘Set Regarding’ functionality, but for some reason I couldn’t get it to work. So I created a new organization with 1 custom entity and puzzled until I found the minimum rights to use the ‘Set Regarding’ functionality.
That’s when I came to the conclusion you must have read rights on Account, Contacts, Leads and Opportunities, to regard an email to a custom entity.
I put the complete set of rights in the pictures below (click the pictures to see an enlargement):

(2 votes, average: 4.50 out of 7)

 Loading ...