Using the Dynamics CRM iOS app is a bit different than the web version. It takes some getting used to, but there are also some features that are not quite what you would expect on mobile, and one of those is wildcard searches (particularly for lookups).
You are here
Now that C# 6.0 has been finalized, it’s time to cover a few of its handier features! One that really stands out is the addition of null-conditional operators. Every developer is painfully aware of how easily an unexpected null can break your code (Tony Hoare even called it his “billion dollar mistake”), so it is necessary to add null checks throughout your code. This new feature allows for some shorthand:
I was recently working on a website that was heavily reliant on AJAX requests. JQuery has a lot of methods to define and process AJAX requests in a convenient fashion, but I noticed that one feature JQuery offers is often overlooked by developers, even though it was added back in version 1.0.
WCF Data Services has been around for some time. It’s the .NET programming framework for building OData services. I’ve used OData a bit with Dynamics CRM in the past, but it wasn’t until recently when I leverage WCF Data Services that I really appreciated its ease of use.
I was helping to prepare a demo for a customer that contained two related entities, but, unfortunately, the customer didn’t give us the foreign key between the two sets of data. Fortunately, we can use Excel to create an artificial relationship for the purpose of a demo.
As an example, assume you have accounts and contacts in your system and each contact should have a foreign key to their parent customer, but in the data you have, that key doesn’t exist. You need to create an artificial relationship for the purposes of a customer demo. It’s easy to do.
Recently, I was working on an application that communicated with an external REST API. When you make a call to a RESTful web service, you can get any number of responses, and I wanted my code to behave differently depending on the response code. Below is some sample code from my PUT request:
var request = WebRequest.Create(_url) as HttpWebRequest;
request.Method = "PUT";
When migrating changes to a new environment, we were receiving an “Invalid XML” error upon import of our solution. Much like what’s detailed in Failed Solution Import in CRM- Invalid XML, the “Technical Details” output on the popup wasn’t immediately helpful. Just like in that article’s example, we also saw the “label attribute is not declared” message.
Informatica – Generating Mapping Configuration Tasks in ICRT
Informatica exposes an endpoint that allows the generation of new mapping configuration tasks. In order to integrate it into an Informatica process, we need to know more about how an action in a service connection needs to be configured in order to communicate with this endpoint.
I’ve been working on integrations between Salesforce and another system. Our standard “pattern” has been to use outbound messages to send a message to our ETL software. It’s been working well – at least until we hit an integration where the performance wasn’t fast enough because it involves a shopping cart operation, often times with someone on the phone waiting for an immediate answer.
One of the new features introduced with SQL 2012 is the Sequence statement and is a welcome addition for auto-number generation. They are similar to the identity property of a column, but handled at the database-level and not bound to a particular table. With earlier versions of SQL Server, you had to settle for an identity property or create your own custom logic to do it.