Filter Lookups on MSD 365

  • Out of box filter No Code: This just configuration on form.
  • Simple Lookup filter
function AddCustomFilterToLookup(formContext, fieldName, lookuptypes) {

//below fetchxml will be a custom filter to the lookup 
    var fetchxml = "<filter type='and'><condition attribute='ownerid' operator='eq-userid'/></filter>";
    formContext.getControl(fieldName).addCustomFilter(fetchxml, lookuptypes[0]);
}
  • Regarding Object lookup filter

//here fieldName = "regardingobjectid";
//     lookuptypes = ["contact", "account", "soft_cust_EntityName", "incident"];
//     formContext = executionContext.getFormContext(); 
function RegardingObjectFilter(formContext, fieldName, lookuptypes) {
    var control = formContext.getControl(fieldName);
    control.setEntityTypes(lookuptypes);
}

That’s it for now. Thanks!! 🙂

10 Things in Microsoft Flow that isn’t in Azure Logic Apps

Reshared blog, here is the original one.

Sorry about the catchy headline.  I will start by saying I am perfectly ready to see a response post containing 20 things in Azure Logic Apps that we wish are in Microsoft Flow.  The point of this post isn’t about whether one product is better than another product, it is simply to highlight the very-intentional design differences and how as users we have access to both and should make our choice accordingly.

If a comparison must be made, then I think in reality, they are better seen as two siblings – LogicApps is the big sibling with more features, Flow piggybacks LogicApps, but itself has several unique tricks and sometimes, features do move between them.  I love both teams & products.

To best describe Flow to an Azure / Logic Apps person, Flow is Logic Apps + power-user / human workflow-focused workloads, combined with a mobile experience and better in-product integration.  As a result, it caters to a whole different set of scenarios that Logic Apps isn’t focused on.

1. Resource-Owned Flows

Continue reading “10 Things in Microsoft Flow that isn’t in Azure Logic Apps”

Field Service: Demo data import issues

demo data

There are so many questions and problems faced by field service developers while Demo data import for field Service. So thought of let’s make write on common issues for demo data import for field service, which I faced during my demo data import.

You can download demo data from here to import into your field service environment. Microsoft already provided a detailed document on how to import demo data to Field Service. you can find that in downloaded files.  But still, while importing this demo data I faced below issues.. Continue reading “Field Service: Demo data import issues”

Field Service: Sample data installation

field service

While studying Field Service, Field Service installation is not enough,  we need to install sample data or seed data in the environment, so we will get clear idea of how its looks like and we can play with that sample data just like real one.

As well, it can be used for demo purpose.

So here are the steps to install sample data for Field Service… Continue reading “Field Service: Sample data installation”

Schedule anything with Universal Resource Scheduling

This slideshow requires JavaScript.

Schedule anything in Dynamics 365 using Universal Resource Scheduling. You can enable scheduling for any entity including custom entities.

For example, you can enable scheduling for the opportunity form and schedule marketing visits for your opportunities. You can also do this for the case form and schedule time to work on cases.

This is applicable for Sales, Customer Service, Field Service, Project Service Automation Continue reading “Schedule anything with Universal Resource Scheduling”