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..
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..
nameof expression in C#6.0
There are many benefits of using early-binding when coding against CRM. There are times however when you need to fall back to late-binding, for example when you need to query relationships, or when you need to call Retrieve to optimise performance (as this service call allows you to load only selected fields of a record).
Rather than using literal string, you can use the nameof operator in C# 6 to get the attributes and relationship names. This works because the properties of the early-binding classes are generated based on the attributes and relationship names in CRM.
For example, to get the AccountNumber field of an Account record:
And there you have it: late-binding with all the early-binding zen!
We had a requirement to delete few of the components from the solution and we followed the new feature that is now available for this in product, starting from CRM 2016 Update 1.
However, we ran into the following error while trying to apply solution upgrade i.e. Solution with ID does not exist.
First time it worked properly and deleted the components from the TEST environment. Then we removed few more components and tried applying this updated solution again to remove those remaining components from our TEST environment, that is when we got this issue.
The issue happens because of certain orphan records which still exist in the database and references the old deleted solution.
Below is the fix for this issue (i.e. update those records in the database).
http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html
http://code2life.blogspot.in/2016/09/crm-2016-sp1-solution-import-failed.html
However as in our case, as it was online we ended up creating the product support ticket to do the same
Other issues that we faced in CRM 2016 Update 1
Hope it helps..
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
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
Hope it helps..
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.
Hope it helps..
Nishant Rana's Weblog 