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..

How to – Add hyperlink (and button) in Form Notification in Dynamics 365 (CRM 2016 and earlier)


Recently we were working on a requirement wherein we wanted to add a hyperlink to the Notification that we were showing on the form.

For this we can use the following Jscript library

https://notifyjs.codeplex.com/

The JScript code:

Output:

Clicking on Details opens the page specified in the callback function.

The other option is to show hyperlink within a web resource and putting it inside the form.

https://nishantrana.me/2012/02/09/showing-related-entity-information-in-header-as-hyperlink-crm-2011/

Hope it helps..

Advertisements

Inviting existing Contacts to Portal in Dynamics 365


For inviting existing contact records as user of the portal we can follow the below steps.

Open an existing contact record and click on Create Invitation button

This creates the invitation record along with the invitation code.

Select and run the Send Invitation workflow.

The steps for the workflow are as below.

The contact\user receives the link for the confirmation

Clicking on the link opens the portal wherein user\contact can redeem the Invitation Code and Register.

User can set up username and password during registration.

Once registered user can access the portal and update the profile further and can also change the password, email etc.

The Contact record in CRM gets updated accordingly.

Hope it helps..

Setting up Portal Trial in Dynamics 365


Create your dynamics 365 trial as a first step (if not already created)

https://signup.microsoft.com/Signup?OfferId=bd569279-37f5-4f5c-99d0-425873bb9a4b&dl=DYN365_ENTERPRISE_PLAN1&Culture=en-us&Country=us&ali=1

Once trial is set up successfully, open the admin center for Dynamics 365 and select Applications and click on Manage to configure the portal.

Provide details for the portal

Click on Accept

Grant Permission to the Portal

We’d get the below message

After some time

Clicking on here takes us to the manage your solutions page

Once configured we’d see the following area\groups\sub groups added to site map specific to portals

Portal : 

myportal

 

Hope it helps..

“getRequiredLevel is not a function” error while creating a new contact record in Dynamics 365.


We were getting the strange getRequiredLevel is not a function error while creating a new record (in New Form Rendering)

After debugging, we figured out that it was failing for the following field “mapcontrollink”.

We commented out the entire section and imported it back (unsupported). This fixed the issue.

Strangely enough we couldn’t find that field in the Vanilla version, in our case it is the upgraded environment so that could be reason of having that extra field.

Hope it helps..