Qualification Required: BACHELOR OF COMPUTER APPLICATION, BACHELOR OF COMPUTER SCIENCE, BACHELOR OF ENGINEERING
Skills Required: Enterprise Solutions and Frameworks - Microsoft Dynamics CRM
Job Description: "Candidate should be extremely sound in Dynamics CRM entities , workflows , configurations , customization development , integrations development • Sound in core NET technology and SSRS • Proficient on CRM Functional areas in Sales Force Automation , Marketing automation and Service management functionality "
This demo shows the different ways in which managers can gain greater control of their business processes using Microsoft Dynamics CRM 2011.
Dynamics CRM 2011 : Charts and Dashboards
What is difference between early and late binding?
Key difference between early and late binding involves type conversion. Whereas early binding provides compile-time checking of all types so that no implicit casts occur, late binding checks types only when the object is created or an action is performed on the type. The Entity class requires types to be explicitly specified to prevent implicit casts.
Create Record In Dynamics CRM - Late Bound
Following example demonstrates how to create record in dynamics crm using late bound.
Microsoft Dynamics CRM Online - Guided Processes Demo
Microsoft Dynamics CRM Online helps improve team effectiveness with consistent and streamlined processes. Organizations can create customized automated workflows without the need for expensive or complex application development.
Microsoft Dynamics CRM Mobility for Blackberry
Watch this 8 minute demonstration to learn how you could use Microsoft Dynamics CRM, Microsoft Outlook, IE and your mobile device to improve your field sales productivity.
Processes/Workflow Ownership Mystery in Microsoft Dynamics CRM
Under what user’s context does the workflow execute? (If the workflow creates a record, who will be the owner of that new record?)
It depends. Automatically triggered workflows (such as a workflow that triggers on account create) will execute in the context of the owner of the workflow. Therefore, if you have a send email step, the email will be by default sent from the e-mail account of the workflow owner. This is important to consider because the workflow owner might belong to a different business unit and have different privileges than the user who triggered the workflow (e.g. who created the account). Let’s say your workflow creates a task each time an account is created. Depending on the privileges of the user, the task might be in another business unit and not visible to the user, therefore you should consider adding an “assign step” that assigns the new task to the owner of the account. Now, if the workflow is executed on-demand, the workflow will then execute in the context of the user who requests the workflow execution. Because dialogs are always on-demand then they always execute in the context of the user who started the dialog.
Why does the process execute under different users depending on how it was started?
This was a design decision based on security considerations. You don’t want to inadvertently be sending emails and executing actions without knowing it because some other user decided it. Therefore, by having this different behavior we can guarantee that the user under which the workflow executes is always aware that a workflow is performing some actions on his behalf. For the automatic workflow case, the owner of the workflow is also the person who activates it and who selects the trigger mechanism and the workflow steps so it is OK if the workflow executes under that user’s context. For the on-demand case, a user is specifically requesting some actions to be performed on his behalf by a workflow so the user is fully aware of the workflow definition and that it will execute; therefore it is safe to execute the workflow under that user’s context instead of the workflow owner (who might not be aware that a user requests an on-demand execution).
Why can’t I activate/deactivate someone else’s workflow, even if I am the system administrator?
For the same security reason as explained above. You want the workflow owner to explicitly acknowledge that a workflow will be activated and will perform some actions on his behalf. You would not want to allow another user (even the system administrator) to decide that some process should be executed on another user’s behalf. If you want to activate/deactivate someone else’s process you must first assign it to yourself.
If I assign an activated process to another user, why does the user have to re-activate it?
Active processes cannot be modified so the system automatically deactivates them before assigning it to the new user. As per Q3 above, only the new owner will be able to re-activate the process.
I am importing a solution that contains processes and it fails with this error message “The workflow cannot be published or unpublished by someone who is not its owner”. What is wrong?
If your solution contains a process that already exists in the organization and is activated then solution import will attempt to update it. In order to do so, it must first deactivate it. However, if the owner of the activated process is not the same as the user who is importing the solution, then deactivating the process will fail (see Q3). Therefore you have a few options to fix this problem:
Import the solution using the user who owns the activated process. This can be tricky, especially if there are multiple processes owned by different users which need to be updated by the solution import.
Verify which processes are included in the solution, and then find them in the organization, if you can find them and they are not owned by you then you must assign them to yourself. You can reassign them to the original user after you import the solution; however, you will have to ask the process owners to activate it themselves.
• Should be able to create and debug Plugins - Should be able to create and debug Custom Workflow activities
• Should be able to do Ribbon customization - Understanding of Solutions - Understanding of the security in Dynamics CRM
• Should have understanding of using Developer Toolkit for Dynamics CRM
Good to have:
• Strong design and development skills
• Ability to design and develop flows
• Effectively communicates to internal and external stake-holders"
- Basic qualifications
Full Time Graduation
Microsoft Dynamics CRM 2013 for Tablets
CRM Portals By Microsoft Now Released
The Dynamics CRM Online 2016 Spring Wave is shaping up to be a one of the largest updates to CRM with the inclusion of new application extensions, Project Service, Field Service and CRM Portals. Adoxio is particularly thrilled to see the launch of CRM Portals. Having created the Adxstudio portals product before its sale to Microsoft, we at Adoxio are excited to see how the product has evolved since Microsoft took it over.
The Microsoft team, comprised of several former Adxstudio colleagues, has been hard at work integrating the Adxstudio Portals product directly into the CRM Online experience. The new CRM Portal add-ons available in the Spring Wave are specifically tied with this update to CRM Online, and will not be available to the on premise version of CRM until later this fall. CRM on premise customers can continue to use the latest version of Adxstudio Portals compatible with their CRM version until the self-hosted version of CRM Portals is made available.
For installation and management of CRM Portals, the new Portal add-on management has been integrated directly into the CRM Online Administration Center under the new Applications section. The Applications section makes it easy to add CRM Portals to any CRM Online organization through a completely wizard driven process, no downloads or installers required. Through this process you can enable any of the new CRM Portal templates available as part of the Spring Wave, these include: Custom Portal (also called Starter or Basic), Community Portal, Customer Portal, Partner Portal and an all new Employee Self-Service Portal.
CRM Online Administration Center - Applications
CRM Portals available in the Spring Wave is limited to the Software as a Service (SaaS) version of product and as such the deployment of CRM solutions, portal site data and the portal code are all done as part of the application add-on enablement process. This really removes a lot of the previous barriers there was to self-starting your installation and portal deployment, with a couple of clicks now you can get CRM Portals up and running with a ready to use scalable public facing site.
CRM Portals add-ons are priced with a monthly cost of $500 (USD) per portal per month with the Software as a Service offering. Pricing is based on the number of page views on your portal with the base including 1 million page views and additional purchasable with add-ons at $50 for each additional million page views. Through the application add-on management you may enable multiple portals of various templates from within the same CRM organization. Customers that are using CRM on premise or CRM Online looking at purchasing Adxstudio Portals for self-hosting functionality the licensing costs will remain as they are today. To learn more, further enablement details will be available in a future blog post, Enabling CRM Portal Add-Ons in CRM Online 2016 Spring Wave.
There are some important things to note about this release of CRM Portals.
Upgrades from an existing Adxstudio Portals release to CRM Portals v8.1 and running both within the same organization are not currently supported. It is expected that a migration path for existing customers will be available in the fall release of CRM Portals. Until then if you do have an installation of Adxstudio in a CRM Online 2016 Spring Wave organization you can upgrade to the latest version of Adxstudio Portals v7 from the Adxstudio Community site.
With CRM Portals, a portal is limited to one language. To support multiple languages you may enable multiple Portal add-ons in any of the 38 support languages. All CRM languages except right to left languages are supported in the Spring Update, and additional Portal add-on costs are required for each language. Existing versions of Adxstudio Portals continue to support multiple languages within the same portal.
CRM Portals is currently limited to a Software as a Service (SaaS) solution in the Spring Update and hosting of portal code is done using Azure App Services. Configuration of the App Services cannot be directly accessed but will include all the capabilities of Azure with automatic scaling and redundant failover across multiple data center regions. As this is a SaaS solution the portal source code will not be available for modification with Visual Studio which may limit the ability to customize the portal for specific enterprise needs. All customization must be done using the CRM customizer and CRM Portals configuration options like entity forms, entity lists, liquid templating and the many other native functions of CRM Portals.