ID3242: The security token could not be authenticated or authorized error in Report Designer (Dynamics 365, CRM 2016 Online)


While working on Report we suddenly started getting the below error

The strange thing was that the other reports that were using the same data source in the same Report Project were working properly.

Find few posts

http://www.dynamicscrmpros.com/solve-error-id3242-security-token-not-authenticated-authorized-connecting-scribe-microsoft-dynamics-crm/

https://social.msdn.microsoft.com/Forums/en-US/ff35a32e-06bc-4c8c-a77f-793fd3cfefb6/id3242-the-security-token-could-not-be-authenticated-or-authorized?forum=crmdevelopment

but none applied here.

Tried creating a new data source, entered credentials repeatedly but nothing worked, eventually restarted the SQL Server Data Tools (IDE) and it fixed the issue.

Hope it helps..

Error while loading code module ‘Microsoft.Crm.Reporting.RdlHelper’. Could not load file or assembly error in report in Dynamics 365


While trying to preview an existing report in SQL Server Data Tools for Visual Studio 2012 got the below error

To fix it,

Go to Report à Report Properties à References Tab and browse to the correct version of the assembly in the BidExtensions folder

Hope it helps..

Fixed – Error installing Report Authoring Extension – “Setup cannot continue because there is a pending restart required. Restart the computer and then try running Setup again” in Dynamics 365


While installing Report Authoring Extension got the above error.

Deleting the following Registry Key fixed the issue

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce.
  • HKEY_CURRENT_USER\Software\Microsoft\Windwos\CurrentVersion\RunOnce


Hope it helps..


Advertisements

Recommended Field showing up as Required Field Issue in Dynamics 365


Hi,

Yesterday while doing the analysis of how the existing solution which uses legacy form rendering works for new form rendering, we found a weird issue.

The field which we were setting as recommended through JavaScript was appearing as required. However, its behavior was like recommended field only i.e. we can save the form without specifying value for it.

In left the fields in legacy form rendering and in right Turbo forms or new form rendering

If we inspect through debugger, it seems like the issue is in the image that is being set

We are still analyzing it.

Hope it helps..

Unsupported filtering of subgrids in Dynamics 365 (CRM 2016)


Hi,

In one of the projects which was recently upgraded to CRM 2016 Online Update 1, legacy form rendering was being used. So, we were analyzing how the new form rendering will affect the existing JavaScript.

One of the unsupported JavaScript that was being used was for sub-grid filtering.

The interesting thing was that it works in CRM 2016 Online Update 1 for legacy form rendering but fails in case of new form rendering (turbo form).

For turbo forms, we get the following objects as null

I couldn’t find any workaround of implementing the same in case of turbo forms. The only possible solution that I could think of is either using Quick View Form with Subgrid control inside it or through a html web resource.

Hope it helps..

Parallel.For vs ExecuteMultiple in Dynamics 365


Hi,

Thought of getting a rough idea on how much performance improvement we can gain if we are using Parallel.For and ExecuteMultiple.

Took a very simple scenario i.e. creating 10000 account records.

Normal For Loop 3242061 milliseconds à 54 minutes à 185 records per minute
Parallel.For 2160337 milliseconds à 36 minutes à 277 records per minute
ExecuteMultiple (single request with batch size of 1000) 494663 milliseconds à 8 minutes à 1250 records per minute

This clearly tells ExecuteMultiple far better.

The sample code that I used for Parallel.For

Hope it helps..

%d bloggers like this: