Managing Blogs in Community Portal in Dynamics 365


Let us see the steps that we need to follow to create \ manage blogs.

To create a new Blog, go to CRM – Portals – Blogs

Create a new blog (specify the corresponding existing templates for Home, Page and Archive)

Saving the record, adds the new blog in the Portal.

We can add blog posts to the blog created.

Blog post within Portal: –

For Managing Blog Posts from the Portal, open the blog record in CRM and go to Author Roles

Create a new Web Role and add that role to the Author Roles and assign the same web role to the Contact (Portal User) in CRM.

  • Below is our custom web role

  • Add the role to Author Roles

  • Open the contact record and assign this new web role.

  • Login to the portal and open the test blog. The portal user will have the rights to edit, delete, new etc.

Hope it helps..

Managing Forum in Community Portals in Dynamics 365 (Using Forum Access Permissions) – Part 2


Suppose we have following 3 forums in our Community Portal

  • And we want a particular portal user to have rights to manage a specific forum, say for e.g. test forum in our case.
  • For this let us create a new web role, here we have specified the Community Portal as the WebSite.

  • Navigate to Community – Forum Access Permissions

  • Create a new permission for the Test Forum and assign the newly created Web Role.

    (Specify Forum as Test Forum and Right as Grant Change)

  • Open the contact record (portal user) in CRM and assign the new web role.

  • Login to the community portal.
  • On opening the General Discussion forum, the user doesn’t have any edit rights.

  • On opening the Test Forum, the user has the modify rights

Hope it helps.

Managing Forum in Community Portals in Dynamics 365 – Part 1.


Suppose we have setup portals in Dynamics 365 and have used Community Portal template.

Community portal allows us to create Forums that lets the users discuss various topics.

  • To create a new Forum, log in to CRM, go to Community – Forums.

  • Click on New to create a new Forum.

The important properties here are

  • WebSite – Community Portal. (the web site inside which we want to create the forum)
  • Parent Page – Page where we want the forum to appear. Forums in our case.
  • Partial URL – URL for the page.
  • Forum and Thread Page Template – Specify the existing template for them.
  • Display Order – Defines the order at which it should appear.

Creating the new forum record in published state (Publishing State) adds the Forum to the forum page in the portal.

Forum will have an associated thread (s), which can be created by the Portal user in the portal or can be created by Admin user within CRM.

Test Forum with the associated thread :-

Inside CRM we’d see the thread associated to the forum.

Thread will have associated Post(s) to it. Post are auto created when a thread is created in the portal.

Suppose we are creating a new thread with the below details in our test forum from within the portal.

This will create a post associated to the thread.

In next blog post we’d explore other features of the community portal.

Hope it helps.

Managed solution cannot update reports which are not present in solution package. Report 98b86a45-1dbb-e411-b283-d89d6765a2e4 is not part of current solution.


We got this error while trying to import a managed solution to our TEST. The error was because of one error during import we had removed the parent solution from the solution, but we forgot to remove the child report. So this child report during import was trying to update or lookup for the parent report which caused this error.

Removing the child report from the solution and importing it back fixed the issue for us.

Hope it helps..

Invalid Operation: Trying to update an attribute in Live, which is not allowed while importing solution in Dynamics 365


We got this error recently while trying to import a managed solution. As it turned out the we had few OOB reports in our managed solution that was getting imported to TEST.

Removing those OOB reports from the solution, exporting it and importing it again fixed the issue for us and we were able to import the solution successfully.

Helpful post: http://vjcity.blogspot.in/2016/09/trying-to-update-attribute-in-live.html

Hope it helps..

Few more interesting issues in New Form Rendering in CRM 2016 Update 1


We recently upgraded to CRM 2016 Update 1 and there seems to be noend to the different product issues that we are facing.

The latest ones are missing scroll bar in BPF when a particular stage has large number of fields in it and the other one being “Click to enter” info appearing at wrong place in BPF for fields.

Legacy Form Rendering

The same form in New Form Rendering

Below are the other issues that we have faced in New Form Rendering till now

https://nishantrana.me/2016/12/09/bug-in-new-form-rendering-crm-2016-update-1-add-new-button-not-working-for-opportunity-product-sub-grid-in-opportunity-form/

https://nishantrana.me/2016/11/28/onchange-event-getting-fired-on-setvalue-in-crm-2016-update-1-new-form-rendering/

https://nishantrana.me/2016/11/25/recommended-field-showing-up-as-required-field-issue-in-dynamics-365/

Well it seems like in Dynamics 365 we do not have the issue with scroll bar for new form rendering but the click to enter bug still seems to exist

bug

Hope it helps..