When it comes to displaying images on your web portal powered by ADX studio, ADX recommends the use of attachment notes as a storage for images. This approach comes with a lot of benefits since it allows the storage of images with various sizes and aspect ratios. The disadvantage of this approach is that it’s rather cumbersome in CRM directly. It provides a rather detached experience when assigning images to entities that in one way or the other will be used as visual assets on the portal.
You are here
When you start development in Salesforce using Apex classes you might struggle at first with building dynamic SOQL queries, specifically when it comes to comparing non-string values - in this example, dates. To start, we have a statement like this which will query active "Resources" objects:
List<Resource__c> resources = Database.query('Select Id, Name FROM Resource__c WHERE Status__c = \'Active\'');
While it is commonly suggested that IExecutionContext.Depth should be used to prevent infinite loops in your plugins, IExecutionContext.SharedVariables can give you finer control over what your plugins are doing, in certain cases. Even better, Shared Variables provide a way to pass values from one plugin to another, as long as they’re in the same sequence of steps for a particular message.
ADX Studio provides a powerful way to display CRM forms and orchestrate multi-step web flows on the web. A web flow step can be configured to display a particular CRM form on the CRM level. Unfortunately, this happens on the CRM level of the ADX portal configuration, which hardcodes a certain form to a step.
AngularJS makes the rendering of an HTML select element quite simple, especially for dynamic options that can be retrieved via a backend service. The directive that AngularJS uses for select elements defined the ng-required attribute that is available for input elements and an ng-options attribute that can be used to generate option elements from arrays and objects, see Listing 1 below.
We recently had a need to be able to retrieve picklist values from the Salesforce case entity for use in another web application that was built using .NET. There are several ways we could have accomplished this. The first would have been to manually add the items to the other application (either hard coded or stored in a database). The problem with that approach is keeping the values in sync becomes troublesome. Do you have someone manually updating items as they change? You could, but what if they forget to update the external application?
After two long months of waiting, the latest CRM 2015 on-premise update has arrived. Originally scheduled to be released in September 2015, this update was delayed without any word on why or when it could be expected. However, on November 5th, Microsoft quietly announced it here: Update 0.2 for Microsoft Dynamics CRM 2015.
Data migration tasks often require us to move records that are dependent on each other or linked with foreign keys. Since those connections are mostly modeled with the primary keys of those entities, we are forced to migrate those records in a particular order. We need to get the IDs of the entities in the new system, first, before we can use those keys to link them with their dependent entities. A common example would be the migration of accounts, including their associated contacts. We first move the accounts over to the new system.
As a technical consultant, you see the various CRM systems up close & personal as well as learn where one system excels relative to the others. In general, one is not necessarily better than other; it often comes down to a customer’s unique set of requirements.