You invested in a Customer Relationship Management (CRM) system and have been diligent in getting the system implemented and adopted across the entire company. However, if your team is not consistently keeping the Lead, Account, Contact, Opportunity and Service Ticket data clean, you are likely missing out on the benefits of having a CRM system to begin with. How?
You are here
The 2017 technology hiring trends are accelerating, creating both opportunities and challenges for organizations searching for tech talent. There are many factors behind the trend. Corporate executives are anticipating deregulation and lower taxes, which is freeing up both operating budgets and capital expenditure budgets. Company information technology budgets across a wide spectrum of industries are supporting higher spending to drive organizational technical excellence forward to support revenue increases.
Candidates and hiring managers alike are on the go today. Neither are always given the luxury of sitting down at a computer to apply for jobs or review resumes. Sometimes, applications must be submitted and viewed from the convenience of a mobile device. In this case, resumes have slightly different rules. The key word is simplicity.
While working in Dynamics CRM, I needed to add several options to a few different optionsets on the Lead entity. Adding the options isn’t difficult, but can be tedious and repetitive, so I didn’t want to do it manually. I decided to leveraged the CRM SDK and used a LINQPad query to populate the optionset as shown in Figure 1.
When building a Web API project, you need to keep in mind how requests to your methods will be made. If requests are made client-side, you'll need to take CORS (Cross-Origin Resource Sharing) security into consideration. This can be done a few ways, which I won't get into for the sake of this post, but you can find more information about CORS here.
Do you have a global software development team? Do tasks get passed daily from work site to work site around the world?
Task handoffs can be tricky when team members are many time zones apart.
You can try using email to communicate work assignments, but emails can be overlooked and emails lack trackability.
You can try a shared spreadsheet of work items, but the spreadsheet can be cumbersome and time-consuming to maintain.
Would you like to use Power BI to build data visualizations around your Visual Studio Team Services user stories, test cases and test results?
Here are the steps to get you there:
1. In the VSTS Work hub, build a query in VSTS to extract user stories and their associated test cases
I have been doing a lot of custom workflow steps lately for MS CRM. I've been using the CRM Developer Extensions which makes it so easy to get started with a plugin or custom workflow. If you add a CRM Workflow Class template, it adds the following lines (I've omitted a few others it adds for clarity):
A handy new feature introduced with C# 7 is Local Functions. As an example, in the LINQ query below, the select method is bit hard to read and can be simplified using a helper function.