Requests to this API should contain at least 100 documents, where each document is not null or empty error while configuring Topic Analysis using Text Analytics in Dynamics 365

Hi,

Recently while trying to configure Topic Analysis in Dynamics 365

https://nishantrana.me/2017/03/24/configure-case-topic-analysis-using-cognitive-services-text-analytics-preview-in-dynamics-365-online/

we got the below error for the failed record.

Error Message:{“code”:”BadRequest”,”message”:”Invalid request”,”innerError”:{“code”:”InvalidRequestContent”,”message”:”Requests to this API should contain at least 100 documents, where each document is not null or empty”,”minimumNumberOfDocuments”:100}}

This was because we had very few case records in our CRM organization < 30. We created few more records to increase the count to be more then 100 and re run the build. This time it got succeeded.

Hope it helps..

Create a simple logic app with Dynamics 365 connector

Let us create a simple logic app that on create of a contact record in CRM creates the same contact in Gmail.

Log in to the azure portal.

https://portal.azure.com/#create/hub

Select New Logic App

Specify Name, Resource Group and Location for the logic app.

Select Blank Logic App

Select “When a record is created” as Trigger.

Sign in to Dynamics 365 Instance.

Select the Organization name and Entity as Contact.

Select Add an action and the New Step

Choose Google Contacts as the Service

Sign in to your Gmail account to be connected

Allow permission to Logic App to access Gmail

Configure Full Name and Primary Email (Dynamic content) as the values for the contact record to be created in Gmail.

Save and Run the app.

Create the new contact record in CRM that triggers the logic app.

On Successful run à

We can see the contact record created in Gmail.

Find all the details here

https://docs.microsoft.com/en-us/azure/connectors/connectors-create-api-crmonline

Hope it helps..

Partner Field Service Portal in Dynamics 365.

Dynamics 365 comes with Partner Field Service portal which helps Partners manage work order, service request, assets, invoices, opportunities etc. from within the portal.

Go to Administrator Center, select Portal and click on Manage.

Select Manage Dynamics 365 Instance

Click on Update Dynamics 365 Instance

Select Partner as Audience and Partner Field Service as the portal to be deployed

Once installed this is how Partner Portal looks like

Below are the different menu options that comes OOB.

Partner Program

Opportunities

Customers

Field Service

Below are the Entity Forms associated to the Partner Portal Web site created in CRM.

Below are the Entity Lists associated to the Partner Portal Web site created in CRM.

Around 121 Entity Permission records are added by the Partner Portal

Web Roles specific to Partner Portal.

Below are some of the permission for the Partner Admin web role.

Once the portal is setup next step would be to Become a Partner. Click on Begin Here.

Update the profile and click on submit.

Within CRM, the admin user needs to run the Approve Partner Application workflow on the corresponding portal contact user record.

After workflow succeeds we can assign appropriate web roles to the portal contact user.

The portal user can create customer contacts record

The portal user can raise Service Requests from within the portal.

Can manage Work Orders.

Can manage Opportunities.

The portal has the Dashboard that shows the details around the opportunity and the cases.

Hope it helps..

Edit Primary Navigation in Portal in Dynamics 365

For updating the Navigation, login to the portal with the user having Administrator web role.

Hover over the Navigation and select Edit

This opens up the dialog box, here we can edit or insert a new navigation link. To add new navigation link click on “+”

We can either specify any existing page within portal or can point to any external URL and can also show up image + text or image only.

This adds the new navigation link

Similarly, we can add new child links or move a link as child link which then appears as drop down. Here we have moved the new Search Home link inside Support by dragging.

The updated navigation looks like below

Hope it helps..

Manage Dynamics 365 Portal Instance

Suppose we have Community Portal configured in our Dynamics 365 Instance.

Now we would like to have Custom Portal instead of Community Portal associated to our instance.

To configure this, we need go to Admin Centre à Select Portal and Click on Manage

Then select Manage Dynamic 365 CRM Instance and then Update Dynamics 365 Instance

From there we can select the Portal Audience and corresponding Portal to be deployed.

This will install the corresponding portal solution to our CRM Instance.

Now our portal URL will show up the Custom Portal instead of Community Portal.

To switch back to community portal, we can select Portal Details and Update Portal Binding to point it to website we want it to bind to.

Suppose we have Employee self-service portal deployed to our instance and we would like to update binding to it.

Below we select Employee self-service as the web site record and click on Update.

Once update is done, opening the Base Portal URL will open up Employee self-service portal instead of Custom Portal now.

Hope it helps..

Site Settings records specific to Registration in Portal (Dynamics 365)

In Portal, we have few Site Setting records that defines the registration behavior.

By default, if user clicks on Sign In page, we see the below options i.e. Sign In, Register and Redeem Invitation as well as Sign in with an external account.

If we want to disable Local Login then we can set the below Authentication/Registration/LocalLoginEnabled value as false.

This hides the Sign in with Local Account option.

For disabling the Registration option we can set the below site setting record as false.

This hides the Registration tabs from the sign in page

Setting both the above site settings as false, presents the user with the only option of using Azure AD for signing in to the portal.

Hope it helps..