Demo data for Microsoft Dynamics CRM Field Service
Archive for the ‘MS Dynamics CRM’ Category
Demo dataset for Microsoft Dynamics CRM Project Service Automation capabilities
(Free / File / Document / Document Set / List Item / Folder / Wiki Page / Publishing Page / CSV / OleDB / Database / Access / Bulk Import For SharePoint / Office 365 / SharePoint Online / 2010 / 2013 / 2016 / Server / Foundation )
Quickly import large volumes of documents, folders, items into SharePoint document libraries and lists.
For further information, help and assistance please refer to the documentation tab – Documentation
You can also download from and get help using DIFS from the DIFS project on GitHub.
DIFS gives you a simple user interface;
Imports can be configured using XML settings files. When you install the software you will find some examples in the “Examples” subdirectory. You can change these to suit your needs.
Using a folder item destination you may create a folder structure and those folders can be assigned meta data;
Using a document destination you can bulk import documents, setting content type and meta data at the same time;
There are several exciting benefits to CRM Online being part of the Office 365 ecosystem, but one of the biggest is the ability to link your company’s Active Directory system to CRM. This allows you to manage all your users in one place, sign in to CRM Online with your existing credentials (known as single sign-on, or SSO), and even control access to multiple CRM organizations by using Active Directory. In this article, we’ll explain the benefits of setting up Active Directory federation with CRM Online, explain how to setup SSO and Active Directory synchronization, and answer some of the most common related questions.
If you have a large organization that uses Active Directory to manage your users and groups, setting up Active Directory synchronization will allow you to manage all of your CRM Online users in a central location, avoiding the need to manage multiple user accounts and passwords. In the Office 365 portal, each user record automatically includes user details such as phone number, which is populated from the corresponding user entry in Active Directory. After you assign a CRM license to a user in the Office 365 portal, the user (and all associated details) will appear within the CRM application. If the user’s name or other information is updated in Active Directory, any changes will automatically propagate to CRM.
Before setting up Active Directory synchronization, you’ll should check out the Single Sign-On Roadmap and decide if you are interested in setting up SSO. With SSO, users will not need to enter a user name and password to access CRM. Instead, users browsing to the CRM Online website will automatically be authenticated by using their existing Active Directory credentials. If setting up SSO is not feasible in your environment, consider the less complex alternative of using Password Sync, which will seamlessly synchronize your Office 365 account passwords with those in your Active Directory.
After you’ve determined whether or not to use SSO, you’re ready to set up the Active Directory synchronization. To make this process easier, we have provided a tool called DirSync, which empowers you to control and manage user accounts in the traditional way by using Active Directory Users and Computers. Many of the attributes from your local AD Global Address List (GAL) can be synchronized automatically to the cloud.
So, what are the requirements for a DirSync computer? To get started you will need an Office 365 subscription, an Active Directory forest, a directory synchronization computer that meets these prerequisites. For complete details about DirSync prerequisites, installation, and use, see the DirSync Roadmap or follow the “Set up” links that appear on the Office 365 Admin Center.
You can also use the DirSync tool to control multiple CRM organizations by using Active Directory security groups. If your subscription includes multiple CRM instances, the CRM Online Instance Picker also provides the ability to control which users have access to each CRM instance by specifying an Active Directory security group.
For example, if you have a test instance of CRM that your expert customizers use to try out new additions to CRM, you may not want all of your employees with a CRM license to be able to access it. If the customizers are already part of an Active Directory security group, just specify that group as the Instance Security Group, and only the customizers will be able to see the test instance.
Here is an example of setting up an Instance Security Group for a CRM instance:
Step 1: Create the group in Active Directory:
Step 2: After the group is synchronized to Office 365, log in to the Office 365 Admin Center as an administrator and then from the Admin menu, select CRM.
Step 3: Finally, edit the development organization instance in the CRM Online Instance Picker to use your Active Directory security group.
Active Directory Federation Services (ADFS) is used by Microsoft Dynamics CRM for an Internet Facing Deployment (IFD). Relying Parties are used to allow users to be authenticated when trying to access Microsoft Dynamics CRM.
Your session has expired
The default settings require users to re-authenticate every hour if there is no activity. This can quickly become annoying if users have to sign in to CRM several times a day. ADFS gives administrators the ability to increase the timeout and reduce the need for users to repeatedly sign in through out the day.
Update the timeout using Microsoft PowerShell
To change the timeout value, you will need to update the TokenLifetime value. This is achieved using PowerShell. Before you open PowerShell, you will need to find the name of each Relying Party.
Step 1: Find out the name of the relying party
- Open AD FS Management
- Navigate to AD FS > Trust Relationships > Relying Party Trusts
- Make a note of the display name for each relying party
Step 2: Update the TokenLifetime value
- Open Microsoft PowerShell as a user with administrator permissions
- Load the ADFS snapin
- Get the relying party trust settings for each relying party. Use the display name from the previous step.
get-ADFSRelyingPartyTrust -Name “CRM – Local”
- Check the TokenLifetime value. This number represents minutes
- Set the TokenLifetime to the new value (8 hours = 480)
Set-ADFSRelyingPartyTrust -Targetname “CRM – Local” -TokenLifetime 480
- Repeat this step for each relying party
Source: QGate Knowledgebase
Learn how to use the tool with the Integration Tool Tutorial
Download the Integration Tool V1.16 here:
The Integration tool for Dynamics CRM can insert, update & delete records in Dynamics CRM and migrate marketinglists with their members as well. But not only this, you can use it to execute sql-commands against any databases and execute Commandline commands with it as well!
- Make sure .Net 4.5.2 is installed
- If you find any errors, please post them under issues.
- If you require any features, please post them under issues with the type feature.
- If you have problems using the tool, please post under discussion.
Contributors are welcome!
If you’d like to contribute, please contact me and/or create a fork directly on github.
Sourcecode moved to Github: https://github.com/peterwidmer/IntegrationTool
Releases will be published here in future as well!
The tool is made up of modules (red in the graphic below), so that it will be easy to extend it with new functionality.
Currently the tool supports the following types of modules:
Each module is capsuled within an assembly, that implements the complete functionality of a module like the configuration-window and the execution-method. As entrypoint it must provide a class implementing the IModule-interface.
Instead download FetchXML and view it by XML Editor, this solution help you view FetchXML on then fly in Advanced Find window
Some pictures after download and install
View FetchXML button added near the Download FetchXML button
Now create a sample query
View it by XML Editor (Visual Studio Code)
View FetchXML by click on button View FetchXML
Work with Visual Studio, edit and save your file …
one second later, your WebResources in CRM are up-to-date!
There’s no need to update or publish scripts anymore. And if a local file is not in sync with your CRM Organization (TFS and CRM are out of sync!) … ScriptEase will let you know:
With this basic idea, the rest comes for free:
- TFS (Source Control integration)
- Support for XRMPageTemplate, etc.
- Suport for the SDK best practices (script naming conventions)
- Support for multiple developers working on the same CRM Organizatin / Solution
The CRM Job Editor has been made available to help you reschedule jobs that have caused performance issues when executing during the day, it will allow you to edit the scheduling recurrence pattern as well as the next runtime of the jobs without having to make any SQL updates. For questions please post in the discussions or issue tracker area. For other reading about CRM please refer to the blog the team and I post to: http://blogs.msdn.com/b/crminthefield
See the releases page for other CRM editions.
This utility is to be used for editing the CRM maintenance jobs automatically scheduled by the installation of CRM (ie: reindexing job, workflow cleanup, etc).
CRM 2011, 2013, 2015, and 2016 OnPremise and Service Provider Edition – this does not apply to CRM Online. To edit your OrgDBOrgSettings (which apply to OnPrem and Online) visit my other project: https://orgdborgsettings.codeplex.com/
Issue Tracking and Discussions
There is no official support for this utility (through codeplex.com nor via Microsoft); if you have any issues use the issue tracker to log the problem. This utility is not intended to be a ‘community’ developed utility but I encourage the community to discuss and comment on this project. When adding Issues please add as much information (including screenshots) to assist me. If you have comments please feel free to contact me via e-mail through this site; or by posting a comment.
Performance Analyzer for Microsoft Dynamics (DynamicsPerf 2.0) is a toolset developed by Microsoft Premier Field Engineering. This toolset is a set of SQL scripts to collect SQL Server DMV data and Microsoft Dynamics specific product data persisted into a singular database called DynamicsPerf. This allows for quick resolution of performance issues on Microsoft Dynamics products (CRM, AX, GP, NAV, SL)