D365 Unified Interface: Enabling embedded legacy dialogs / Advanced Find

Quite simply put, some of the embedded dialogs like the Advanced Find, Merge Records, Assign window are not by default visible on the Unified ClientnoButtons

Like when you multi-select records, you can’t see the typical Merge, Edit buttons on the ribbon.

Here’s how you enable them

System Settings

In your Web Application’s system settings, you have an option under general where you can enable these buttons in the Unified Interface

systemSettings

Now, you can retain those buttons in the Unified Interface as well

visibleButtons

Have a great time exploring Unified Interface!

Advertisements

Why we see Cross Day in Work Hours on Bookable Resources/User?

Ever wondered what is Cross Day on Work Hours for a Bookable Resources in Dynamics 365 PSA or Field Service? Or even User record for that matter? And why not the actual Work Hours a resource is set to?

You expect to see this –

actualWH

But see this?

crossDay

Reasoning

So, The Bookable Resource’s time zone is GMT

bookableResource

And so is the same time zone of the logged in user i.e. GMT

gmtIsSet

In that case, you’ll see the actual time set for the user i.e. 8am to 5pm.

But, let’s say, you are in a different time zone – Sydney, for example.

sydneyTimeIsSet

And you are viewing Work Hours for a Bookable Resource who was set in some other time zone, their time conversion to your time will result in “crossing the day over” and hence, you see “Cross Day”.

crossDay

Hope this is helpful! 🙂

 

What happens when you force fields on BPF to be required programatically or using Business Rule

I had a requirement where I needed to make certain fields on BPF as required.

So, I tried accessing the control using Xrm.Page.getControl(“header_process_description”) and then getAttribute().setRequiredLevel(“required”) on it would serve my purpose. But actually, not!

To set perspective, the code runs and make the field required too. But there’s a catch!

Required fields on the BPF are supposed to throw an error when you are trying to move to the next stage without filling in the required fields.

But, using the code I’m talking about above (sample shown below), will force you to save the form entirely. Let alone moving the stages further.

jsCode

That when ‘How Did You Hear About Us?’ field has Employee Referral as value, make Purchase Process field required.

empoyeeReferalSet

Field is on the BPF

fieldOnBPF

But prompts me to save the form
promptToSave

 

Workaround

The easiest workaround to this is using the conditional branching of your business process flow –

You can use conditional branching of the BPF itself – You can replicate the same stage twice, one having your required field and other having that same field as optional.

bpfBranching

However, limitations I found with this approach is –

  1. I couldn’t use the same for the first stage of the BPF –
    limitation1
  2. The condition had to be from the previous stage itself
    limitation2

P.S. Business Rules isn’t a solution as well. Also, I tried to inverse the logic by first making the field required in the BPF itself and then trying to make it not required using code. That doesn’t work either.

Hope this gives an idea. Let me know if you have other suggestions! 😊

 

Missing ‘Dynamics 365 App For Outlook’ from Settings in Dynamics 365 v8.2

Hi Folks!

Recently came across a scenario where I was using v8.2 of Dynamics 365 Online and I wasn’t able to find Dynamics 365 App For Outlook in the Settings area.

missingApp.PNG

Fret not! App is enabled for you already if you even an Exchange Online license. But, at times if you don’t see this – just visit this URL as below:

https://[Your_Organization].crm.dynamics.com/tools/appsforcrm/AppForOutlookAdminSettings.aspx

appView

 

 

Hope this quick tip helps!

Quick Tip: Cleaning Queue Items

So are you stuck with email queue that has junk of emails you don’t want? And maybe those emails are important to CRM.

Let’s say you have these emails in your Queue (imagine there are a lot many and removing them seems like a big task)

qItems.PNG

Here’s what to do:

  1. Run a Bulk Delete Job on the following:
    Queue Item entity and the required criteria you want (maybe you want to delete only old Queue Item which you no longer need to convert to other record types)
    bulkDeleteCriteria.PNG
  2. And submit the job.

Now, even if you delete the Queue Items, the Emails will still remain in CRM in Activities records and those are not lost!

Hope this was helpful! 🙂