Showing posts with label crm2013. Show all posts
Showing posts with label crm2013. Show all posts

Wednesday, November 26, 2014

Enable Announcements in CRM 2013 / CRM 2015

By default, announcements are not available for the user in versions > 2011.

In Settings –> Announcements, it is still possible to configure them.

announcements

To show them in the basic navigation, you have to manipulate the SiteMap. I suggest to use XrmToolbox (SiteMap Editor).

toolbox_announcements

You can also add the XML-Code manually.

1 <Group Id="MyWork" ResourceId="Group_MyWork"...>
2 ...
3 <SubArea Entity="businessunitnewsarticle"
4 Id="nav_news" Url="/home/homepage/home_news.aspx"
5 AvailableOffline="false" PassParams="false" />
6 </Group>

Cheers

Monday, February 3, 2014

Sonoma Microsoft CRM Dev Tools

Sonoma offers a new extension for Microsoft Dynamics CRM. It is provided as a Google Chrome-Plugin.

Dynamics CRM DevTools

 CRMDevTools

Functionality

  • Shows Form information (Id, Name, Type Code, Form Type, Is Dirty)
  • Refresh current form
  • Enable/Disable attributes
  • Show hidden attributes
  • Shows User information (Domain Name, User Id, Business Unit Id)
  • Open Advanced Find
  • Search for Attribute, User Id, Privilege Id (and navigate to the record)
  • Set focus to a field
  • Update attributes (testing)
  • Execute Fetch XML Queries

Lets hope there will be a IE-Solution in the future too.

Cheers

Wednesday, October 23, 2013

CRM 2013 – Official Microsoft statement for jQuery usage

In the latest documentation you can find the document

Using jQuery with Microsoft Dynamics CRM 2013.docx

In this, Microsoft describes the prefered usage of jQuery in the Microsoft Dynamics CRM context.

Usage in HTML Webresources

Microsoft: When creating user interfaces with HTML web resources we highly recommend that you also use jQuery. It provides many benefits in creating pages that support multiple browsers that it is practically a necessity.

So this is fine and i think everyone is doing this right now.

Usage in Entity-Forms

Microsoft: However, when creating form scripts we do not recommend that you use jQuery. To enforce business logic in forms we provide objects in the Xrm.Page and Xrm.Utility namespaces that you use to apply your business logic within the form. We do not support referencing or manipulating the DOM (including styles) for our pages in any way. …

Ok, i have done this in the past and i don’t want to miss a lot of the jquery functions (ajax….) in the future too. So to make sure you don’t run into big issues try the following.

  • Avoid “hard” CSS/DOM Manipulation via jQuery

Microsoft: We reserve the right to restructure or rename DOM elements in our pages at any time without notice. If your code has dependencies on any objects defined in the DOM and these objects are reorganized or renamed your code will break.

  • Assuming you are not the only one who is delivering solutions for your customer, use the following construct to create your specific jQuery-Object ($).
   1: my$ = jQuery.noConflict(true);
   2: my$.trim("     some text with space     ");

Cheers

Tuesday, September 17, 2013

CRM 2013 – Create Custom Actions

The new version of Microsoft Dynamics CRM includes a feature called Custom Actions. In this post I want to show the process of creating an Action in the CRM UI and access it over a Console Application.

The Problem to solve:

Create a Custom Action, that creates a task or a phonecall for an existing account record, based on the “Industry” Optionset. It should also be possible to add the description of the task in the Request.

1. Create the Custom Action

In this example we create the action in the CRM UI. It is also possible to create it in Code (only OnPremise).

  • Navigate to Settings –> Processes

processes

  • Click “New” and set “CreateSalesActivities” as Process name
  • Set “Action” as Category
  • Select “New blank process”
  • Set “Account” as Entity
  • Click “OK”

action_screen_basic

  • Add the input parameter for Description

action_screen_input

  • Configure Ruleset

rules_for_action 

action_screen_ruleset_call

Accounting –> Create PhoneCall

action_screen_ruleset_task

Others –> Create Task

  • Save the Custom Action
  • Activate the Custom Action

activate_action 

2. Execute the Custom Action

For executing the Request i have created a Console Application. You can check the sources of my PluginQuickDeploy-Project when you need support creating it.

Executing Accounting-Case:

   1: private static void ExecuteCustomActionAccounting()
   2: {
   3:     IOrganizationService service = GenerateService();
   4:     Entity account = new Entity("account");
   5:     account.Attributes.Add(new KeyValuePair<string, object>("name",
   6:         string.Format("Account generated at {0}", DateTime.Now.ToShortTimeString())));
   7:     account.Attributes.Add(new KeyValuePair<string, object>("industrycode", 
   8:         new OptionSetValue(1)));
   9:     Guid accountId = service.Create(account);
  10:  
  11:     OrganizationRequest req = new OrganizationRequest("new_CreateSalesActivities");
  12:     EntityReference accountReference = new EntityReference("account", accountId);
  13:     req.Parameters.Add(new KeyValuePair<string, object>("Target", accountReference));
  14:     req.Parameters.Add(new KeyValuePair<string, object>("Description", "Text from Request"));
  15:  
  16:     OrganizationResponse resp = service.Execute(req);
  17: }

Executing Default-Case:



   1: private static void ExecuteCustomActionDefault()
   2: {
   3:     IOrganizationService service = GenerateService();
   4:     Entity account = new Entity("account");
   5:     account.Attributes.Add(new KeyValuePair<string, object>("name", 
   6:         string.Format("Account generated at {0}", DateTime.Now.ToShortTimeString())));
   7:     Guid accountId = service.Create(account);
   8:  
   9:     OrganizationRequest req = new OrganizationRequest("new_CreateSalesActivities");
  10:     EntityReference accountReference = new EntityReference("account", accountId);
  11:     req.Parameters.Add(new KeyValuePair<string, object>("Target", accountReference));
  12:     req.Parameters.Add(new KeyValuePair<string, object>("Description", "Text from Request"));
  13:  
  14:     OrganizationResponse resp = service.Execute(req);
  15: }


3. Testing


After execution of the both requests, a phonecall is generated and attached to the first account, a task is generated and attached to the second account. The description is passed by the request.


Created Call:


callCreated Task:


 task



Additional Information - Output Parameters


It is also possible to retrieve information from the custom action. Therefore you have to define Output-Parameters and set them in the rule wizard. In this example the Custom Action returns the Entity Reference of the created task.


return_value


assign_value_step


assign_value_rule


responseThe feature is very interesting and i look forward to use it in one of my next projects (lets hope CRM 2013 will be available and stable soon).


cheers

CRM 2013 – Custom Actions

Custom Actions are a feature shipped with CRM 2013. The easiest way to explain the feature (for developers) is:

You are able to create your own OrganizationRequest”

It is possible to use the CRM UI for creating an “Action” or you can write Code that creates a custom Action.

action_category

Key Points (SDK)

  • Is defined using a Workflow entity record, similar to a real-time workflow.
  • Can be associated with a single entity or be global, meaning not associated with any particular entity.
  • Is executed in the core operation stage 30 of the event execution pipeline.
  • Supports the invocation of plug-ins and real-time workflows registered in the pre-operation and post-operation stages of the event execution pipeline.
  • Can have plug-ins or real-time workflows registered in the pre-operation or post-operation stages while the action status is Draft.
  • Is available through the organization.svc and organization.svc/web endpoints, but not the organizationdata.svc (OData) endpoint.
  • Always runs under the security context of the calling user.
  • Record cannot be deleted while there are plug-in steps and other real-time workflows registered on the action.
  • Can be invoked only by a web service method call, not directly from a workflow. However, the workaround is to write a custom workflow activity that invokes the action and add that to a workflow.
  • Can optionally participate in the current database transaction.
  • Does not support a scope where the execution is restricted to a user, business unit, or organization.
  • Supports input and output parameters.
  • Supports auditing of data changes.
  • Is not supported with offline clients.

This feature will reduce plugin code in the future, because it is possible to encapsulate a sequence of operations in one request.

cheers

Monday, September 16, 2013

CRM 2013 – Business Rules

One of the new pretty interesting Features of Microsoft Dynamics 2013 are Business Rules. The purpose of them is to allow non Developers to customize basic rules like

  • Show and hide fields
  • Set and reset “Business Required” for fields
  • Show Error-Message
  • Set specific Field Value
  • Lock or unlock fields

on specific triggers/conditions. Also Basic-Formulas (+, –, *, /) are possible.

formula

The UI looks nice and clean (a bit like IFTTT).

Example

Set “Approved by Manager” Field as Business Required when Budget Amount of Opportunity is more than 50000,00€.

Before:

business_rule_before

Business Rule:

business_rule

After:

business_rule_after

Hint:

The Value for “Business Required” is not resetting automatically when Budget Amount is decreased to < 50000. An additional rule is required.

less_rule

This feature will reduce the lines of JavaScript code in the future enormously.

cheers

Wednesday, July 31, 2013

CRM 2013 No longer supported stuff

Following stuff is no longer supported in CRM 2013.
  • CRM 4.0 Custom Workflow Tools
  • CRM 4.0 Client Side Scripting
  • CRM 4.0 Plugins
  • 2007 WebService
  • ISV Folder
  • Solution Down Level Tool
Cheers