Microsoft SharePoint Server 2016 Release Candidate (Beta 2) is in the process creating very positive impressions. Interestingly, with the release of Microsoft SharePoint Server 2016 comes a turn in the SharePoint offerings moving forward. SharePoint is clearly at a crossroads. A commitment to choose between On-Premise and Cloud is likely to soon to lean heavily towards SharePoint as a service. These signals are important to consider as your company determines its planning horizon to move important SharePoint-based applications to The Cloud.
You are here
Sometimes, when I’m doing some customizations in Salesforce, I want to see a list of accounts, contacts, leads, etc., but I don’t want to go through the hassle of creating a view. I have to add that it’s not really difficult to create a view, but sometimes you just want to see the data quickly. (There’s also a quick way to get to a form to add a new item as well.) If you want to see or enter the data for a specific record type quickly all you have to do is enter a URL in a specific format:
I recently was looking at some old code that generates SQL statements. Part of this code built a string that rounded a double value to 2 decimal places in SQL - it had been working successfully for many years, but all of a sudden one instance was failing. Here is an example of a successful string:
SELECT ROUND(1.14172780803793, 2) as RoundedNum
While this is an example of a failing string , resulting in the familiar error message "Arithmetic overflow error converting expression to data type numeric.":
I was recently working on a data integration from an external system to Salesforce.com. I was using the force.com developer console to query the number of records by owner and record type for accounts to compare the numbers against the source system.
While it’s always important to keep tabs on what operating system versions are supported for which CRM versions, the recent release of CRM 2016 means that Microsoft has moved on while many organizations may be in the process of evaluating the upgrade before taking the dive. With OS upgrades being pushed out to tablet and phone users on an increasingly regular basis, it has become even more vital to know which updates your users should wait to apply.
While working with ADX Studio, I encountered several situations where I had to provide a lookup that needs to show only related records as selectable options. Fortunately, ADX fully supports the build-in CRM functionality that allows configuring that sort of filtering on the CRM form. After adding a lookup field to a CRM form, we can access the properties of that form field and find the Related Records Filtering.
Recently I was asked to look a Stackoverflow TSQL query that limited the results returned from a joined table to one row. I used the Categories and Products table in the Northwind database (it’s a good simulation of the tables used in the actual query) as a given category can have more than one product and I am returning just the first product record for each category based on the product ID.
MS CRM has a limitation that when you create an email template to use in a workflow, you can only base the template on a predefined list of entities. Adding to that is the frustrating fact that once you choose the source entity you can only add fields from a predefined list of related entities, so accessing fields from a custom entity isn’t possible with out of the box functionality.
I've recently been working with a Kendo Scheduler control. It's a great tool, and fairly simple to customize once you get familiar with it. Something that I found was requested a lot on the Scheduler forums, but not available out-of-box, was to "gray out" or block off time on the scheduler. For example if you only want to your business hours to be available (which may vary day-to-day).
With CRM 2016, came the Web API; a new endpoint allowing the creation, deletion, update and retrieval of CRM data. While Microsoft has stated that the old 2011 endpoint will remain in order to support backwards compatibility, it has been deprecated, and ideally should not be used for new development.