This tip is from Miquel “Third musketeer” Julien (who runs an excellent http://www.guidemicrosoftdynamics.com/ French Dynamics 365 tipping site).
If your Bing Maps integration is disabled (under Settings > Administration > System Settings > General tab) then any section containing Bing Maps control will be hidden, regardless of any controls it may contain.
1,000 words™
Developers are familiar with the concept of impersonating Dynamics 365 users. It’s easy – all you need to do is to add MSCRMCallerID header to your Web API request, and you’re done (assuming that you have prvActOnBehalfOfAnotherUser privilege).
One of the typical scenarios where you’d want to use the impersonation when you have a web site that connects to your Dynamics 365 instance using either non-interactive user or, better, S2S authentication and then you need to impersonate a currently logged on Azure AD user. The typical flow is: look for a UPN claim, then use that value to find the user in systemuser entity filtered by domainname attribute.
The problem is that UPN claim does not seem to be available when you’re using B2B guest users. In both scenarios a different oid claim is available that returns Azure AD object ID. That value can be used to query systemuser entity using azureactivedirectoryobjectid attribute. Then it’s business as usual, plonk systemuserid value into MSCRMCallerID header and you’re done.
The following approach is undocumented (hopefully not for long!). The usual Tîpp Jäår’s disclaimer applies: not [currently] supported, use at your own risk, contains small children between the flags, not to be consumed with alcohol while driving.
Instead of using Azure AD object ID to lookup the user, pass that id as MSCRMCallerObjectID header.
POST [Organization URI]/api/data/v9.0/accounts HTTP/1.1 MSCRMCallerObjectID: 00000000-0000-0000-000000000002 Accept: application/json Content-Type: application/json; charset=utf-8 OData-MaxVersion: 4.0 OData-Version: 4.0
Saves you the need to lookup systemuser and splitting the logic depending on the user type.
Facebook and twitter cover photo by Greg Ortega on Unsplash.
When Scott “Mr Ribbon Workbench” Durow was delivering his “Typescript or Die” presentation at CRMUG EMEA last month, he stunned the audience by showing his phone right on the screen without any pairing.
He tricked everyone, of course; I don’t believe he even has an iPhone. Turns out, Google Chrome has a not-so-obvious menu when you render things for a predefined form factor.
I was hoping for custom frames for all the devices but seems that this art form is reserved for the fruity family.
What is your first reaction when you receive email like this one
Let’s see. Comes from someone with the name “Workflow”, has attachment and no body text, and refers to financial matters (payment advice/invoice/quote). Delete? Delete!
Out of curiosity I did peek into the email just to see what kind of nasty attachment they sent this time and turns out, it was a legitimate notification from the customer’s accounts payable.
Sending emails is one of the most common uses of the workflow engine in Dynamics 365. But if you are not careful you’ll end up sending something that most likely will end up in a junk, either automatically or as deleted by the recipient.
What can you do?
I’m sure there are other tips to ensure that your email is delivered and read but even following the simple points above will get the job done more often than not.
Back in Tip #736: Add variables to your workflows, George ‘bringing discipline to the rest of us’ Doubinski suggested the excellent Tip of using an Action to simulate a variable in Workflows. I went to use this Tip this week for a lookup and, to my chagrin, found there is an exception to the Tip. Namely, if the output argument is a Lookup (or Option Set), the Action will NOT be available to the Workflow. It simply does not appear in the list. If you have a friendly developer nearby they can create a ‘wrapper’ with a custom Workflow activity but, as my colleague Lachlan ‘Cabin Boy’ Wright pointed out there is a simpler, codeless way. Sometimes the obvious answers come to us through the eyes of the innocent.
While it is possible to define an Input or Output argument as an EntityReference or Entity (think pointer or memory reference if you come from a C background, or GUID vs record, although for the simple purposes of configured Actions I am yet to find a practical difference between the two argument types), this renders the Action useless for the reason mentioned above. The alternative is to use the Workflow’s record, that is, the record the Workflow is running in the context of. So, if you need a lookup ‘variable’, create a lookup in the entity and store the value there. Workflows can be a bit tricky in terms of running their steps in order so be careful but it is a simple workaround to an annoying problem.
I am not even going to pretend that I can match the eloquence level of some Microsoft announcements so I’m going to copy this one verbatim. In short, if you are a Microsoft Partner with expertise in Azure and/or Dynamics 365, and you deal with the government(s), read and take action.
We are excited to announce that our new Azure regions in Canberra are now available. These new regions are designed to serve the needs of Australian and New Zealand Government, critical national infrastructure commercial organisations and their trusted suppliers. We have entered into a strategic partnership with Canberra Data Centres to deliver these new regions, unlocking the potential for digital transformation and innovation.
Additionally, the Australian Signals Directorate has upgraded the certification of 25 Azure and 10 Office 365 services to Protected status, making us the first global cloud provider to achieve this certification level in Australia. Our new regions also offer 100% ANZ supply chain assurance, high availability and disaster resilience, and the specialised connectivity and colocation characteristics necessary to support the mission-critical data requirements of our customers.
We operate a process for whitelisting Azure subscriptions to deploy into the new Australia Central Regions. This is a two-step process to firstly authorise eligible Australian and New Zealand organisations, and secondly to enable these organisations to provide Azure Subscription IDs for whitelisting.
Alongside this and aligned to our launch, we are pleased to announce our Azure Skills Training Program designed to help build the fundamental skills needed to enable cloud adoption. Through July, we will offer a series of highly subsidised, in person and instructor led training courses in all capital cities across Australia.
If you are interested in finding out more, here are some next steps:
Visit Azure.com/Australia to find out more about these new Regions, to check your eligibility, view our launch partners, and learn how to get started.
Dynamics 365 Online is a great platform for extending almost anything including system entities like systemuser. While it’s easy to customize this entity to add some simple additional information about the user, e.g. charge-out rate, induction training completion date, latest lasertag achievement, etc, it may be not a good idea, after all.
The problem is that systemuser entries and, specifically, their status, are controlled outside of Dynamics 365, by Azure Active Directory. During the routine updates it may cause some drama if, for example, a Space Invaders score needs to be corrected for someone who no longer has Dynamics 365 license and is therefore disabled. Data migration between the systems would be even more challenging with the only solution being to temporarily grant licenses, wait a bit for them to take effect, update what’s needed and then remove the licenses. Possible to automate but rather tedious and may require some extra licenses.
Instead, keep additional information about the users in a separate entity with 1:1 relationship to systemuser. Updates to inactive records? Easy done. Migration of the data for 700 disabled users? No problem. And if you ever wanted to keep some of the private information like their hobby or last year bonus, you can apply some Dynamics 365 security juice.
Calling for Dynamics 365 developers around the world but mostly in Europe! CRM Tip of the Day is proud to present an inaugural Business Application Developer Masterclass. Even though the acronym spells “BAD”, it’s going to be good!
Without further ado…
The new, Spring 2018 Dynamics 365 release is here with the new features, new developments, and new challenges. This is your first chance to get your hands on the new technologies and learn the new stuff before anyone else. Hear the news from Microsoft Build 2018 and what does it mean for Business Application Developers.
A rare opportunity to attend personal in-class training by yours truly, George Doubinski, founder of CRM Tip of the Day and CRM.Audio with the guest appearances by Scott Durow, author of Ribbon Workbench and SparkleXrm, and David Yack, Microsoft Regional Director and author of https://xrm.tools.
Who shall attend: For all you experienced Dynamics 365/CRM developers who want to take your skills to the next level.
There is a limited number of seats available so pick your favorite city and register today!
Would you like to convince yourself or your boss? How about 20% discount if you register by the International Labor Day, 1st of May?
Note: Agenda is subject to change
Country fields in D365 are text fields. The reason they are text fields is that that’s how it works in Outlook, and since addresses for contacts in OUtlook synchronize with D365, they are text fields in D365.
Many companies that use CRM have replaced the country and state fields with option sets or lookup fields; however, there are some considerations:
Probably the easiest solution is to add the country option set and have a process update the standard text field with the value selected. This gives you a standard list but ensures that the standard country field is populated so it is populated in the address table as well as the contacts synchronized to Outlook. This doesn’t give a complete answer for contacts tracked from Outlook—the country option set would still be blank for these contacts, but you could create a cleanup batch job that updates these contacts that don’t have a country selected in the country option set.
(The chart fortnight by Ulrik “CRM Chart Guy” Carlsson is over but I’m sure he’ll be back! – t.j.)
Sometimes we need to set the value for a field but only if it does not exist, e.g. user did not bother entering it. Like topic for a lead. I’ve seen the implementations where business asked to make it optional and set default to the lead name.
The first instinct is to do something conditional like:
if lead topic does not have value then update lead with a made up topic
Stacked approach works quite well in this scenario as “if without if”, i.e. update topic to itself otherwise use made up default:
The update is now can be bundled with some other manipulations, saving an extra update call but one thing to be aware of that it is unconditional and will trigger both workflows and plugins if any are registered on update of the field (topic in our sample).
of the