Texans are quick to draw, I hear. Today’s tip from Mitch “Texas Baby Oil” Milam just proves that.
The absolute quickest method for adding multiple fields to a form is not dragging and dropping. It is double–clicking. Here’s how it works:
- Select the section within the form where the new fields will be placed.
- Using the Field Explorer, on the right–side of the Form Editor, navigate to the field or fields you wish to add.
- Just double–click on the field name and it will automatically be added to section you selected in step 1.
Once the fields are added to the section, you can use the arrow keys to move the fields around the section, or event between sections.
Thinking about doing an in place upgrade from CRM 2013 to CRM 2015?
If so it isn’t just a matter of running the SetupServer.exe file. That is even assuming that your underlying infrastructure supports CRM 2015.
One notification that you run into immediately is the pre-requisite to uninstall the CRM Connector for SQL Reporting Services. In this case we were updating an all in one server environment in our developer area.
SQL Server Reporting Services Connector Uninstall Warning
Do you need to make changes in the deep reaches of your CRM configuration that aren’t available through the CRM administration panel?
Well there is a solution out there on Codeplex that you can import into your CRM 2011/2013 environment as a managed solution.
This utility allows you to edit your settings without the use of the command line utility in the KB article documenting “OrgDBOrgSettings.” The utility is written using the CRM SDK as a reference and currently all changes and retrieval of settings are done via the CRM’s OData Endpoint. The utility is provided as a managed webresource that can easily be installed and uninstalled from your CRM environment.
The utility is available at: https://orgdborgsettings.codeplex.com/
Here is an example of how to change the export to Excel limit from 10,000 to a higher value (although the top limit is 50,000).
Export to Excel more than 10,000 records
There is no limit to how unusual the discussion topics can get at the Tipping Truckstop.
Blake “Windy City” Scarlavai started this round with this question (but hey, customer is always right, right?):
A client is wondering if it is possible to turn off the Track button in Outlook for emails? Hoping there might be a registry key or something similar that might be able to accomplish this.
Adam “CRMUG Hall of Fame” Vero: Depending on the real business objective, you can force the Track button to behave like “Set Regarding” – this is often what customers seem to be trying to do when they ask this, so they don’t have emails just thrown into the system.
This is an OrgDBOrgSettings one: OverrideTrackInCrmBehaviour set to 1 will do this (0 is normal OOB behaviour). (Tipp Jarr – presumably, one would use the tool rather than poke SQL database directly)
Carsten “Traveling Salesman” Groth: You can even customize ribbon menu and hide the button. (T.J. – endure the pleasure of XML editing or be smart and tap into Scott Durow’s mega-awesome workbench)
Chris “That’s Mr ADFS For You” Cognetta: LOL just don’t install the client. (T.J. – what Chris really meant is that tracking is essential part of the CRM design and it’d be better to educate and encourage your customer to learn, explore and start using CRM Outlook client’s awesome features.)
Dynamic Excel Export is not working?
Remember that you need to have the CRM Outlook Client installed to use the Dynamic PivotTable and Dynamic Worksheet export to Excel workbooks. No Outlook Client or, as it’s known by its full name, Microsoft Dynamics CRM 2015 for Microsoft Office Outlook (that was a mouthful!) – no worky! Don’t know where to find it? It’s right here. If you don’t actually want to use Outlook Client, configure the connection but turn off any syncronization and change user’s email settings in CRM to avoid Outlook.
Thanks to Jim “CRM Baker” Steger for the reminder!
Today’s slice of CRM wisdom is brought to you by Feridun “Best Twitter Handle for CRM MVP” Kadir:
Not all browsers are equal
From time to time something in Microsoft Dynamics CRM stops working that I knew for certain used to work. Of old, my first reaction would be to blame the issue on a CRM bug. But I’m getting wise to the fact that browsers also have bugs feature changes and the problem might not be a CRM issue.
So I have multiple browsers installed on my computers and if something doesn’t work in my usual browser I make sure to test it a different browser before starting a rant in a forum.
Tipp Jarr’s Double Dipp
Nice one, Feridun! We did report on some extra features and inconsistencies between the browsers. Firefox lately has become my defacto developer’s tool but have you ever tried to remove attachment in CRM note? Useless!
So, unless you’re under an evil corporate eye and forced to use IE 6, listen to Feridun and install all three. Feeling adventurous? Throw in Safari, just for fun.
After you CRM 2015 upgrade, the users, teams, and roles should now appear in the Settings area under “Security Management.”
However, what should you do if the new security management section is missing?
Create a solution containing your sitemap and export it out.
Edit the sitemap and add the following subarea to the settings area:
Import the solution back into your CRM environment, and after a refresh, you will now see the Security Management section.
If you upgrade to CRM 2015 and have custom security roles, those roles will not have permission to view the new hierarchy visualization.
To add the permissions to your existing custom roles, use the Role Updater in the XRM Toolbox.
Select the role you wish to update, then click “Next.”
2. Search for “Hierarchy” and give organization read permission for the hierarchy definition and hierarchy rule entities.
Thanks to Scotty “Scott” Sewell for this tip.
Scott “Captain Redlaces” Sewell reminds us to name our relationship display names responsibly. Say you have multiple contact lookups on the account form. If you go with the default naming for the related entity navigation, this will create multiple navigation links with the same name. You might be able to get away with this in browser, but it will be a big problem in the phone or tablet apps. When someone looks at a contact, the related record section of the form will show multiple links with the same name, and users won’t know which to use.
To avoid this, use a custom label for the navigation pane item in the relationship definition. Give the relationships a descriptive name.