D365 V9{Upgrade}: Error while upgrading NuGet package Microsoft.CrmSdk.XrmTooling.CoreAssembly to v9.0.2.5

Recently, while upgrading our D365 instance from V8 to V9, we had some batch jobs for integration which were running on v9.0.2.4 of CRM related NuGet packages. As part of V9 upgrade we need to upgrade those NuGet packages to v9.0.2.5. While upgrading XrmTooling.CoreAssembly to v9.0.2.5, we were getting the below error: "Unable to resolve dependencies. … Continue reading D365 V9{Upgrade}: Error while upgrading NuGet package Microsoft.CrmSdk.XrmTooling.CoreAssembly to v9.0.2.5

Advertisements

Azure: Web Job Deployment Error “The local data store is currently in use by another operation”

Recently, we had written a batch job to connect to D365 and do some operation on a schedule. While deploying the batch job from Visual Studio as a web job we got the below error: "The local data store is currently in use by another operation. Please wait and then try your operation again. If … Continue reading Azure: Web Job Deployment Error “The local data store is currently in use by another operation”

D365: Retrieve, Associate, Disassociate N:N Related Records using C#

In this post, we'll talk about an example where we need to retrieve N:N related records and code snippet for the same. We are using ClickDimensions component in D365 for marketing purpose. We came across a requirement where we were supposed to disassociate the related records(Marketing Lists) from a record(Email Send a ClickDimensions entity) based … Continue reading D365: Retrieve, Associate, Disassociate N:N Related Records using C#

D365 V9{Upgrade}: Client API Change for openEntityForm

Prior to D365 V9, we were using Xrm.Utility.openEntityForm() to open an existing record or to open a create form of an entity providing some additional parameters. However, in D365 V9 as it has been deprecated, we need to use Xrm.Navigation.openForm() to perform the same operation. Here's an example of the change in API along with … Continue reading D365 V9{Upgrade}: Client API Change for openEntityForm

D365 V9{Upgrade}: Client API update for alert and confirm

In D365 V9, as per Microsoft documentation, Xrm.Utility.alertDialog() should be replaced by Xrm.Navigation.openAlertDialog() and Xrm.Utility.confirmDialog() should be replaced by Xrm.Navigation.openConfirmDialog(). Let's take an example of both alert and confirm dialog box and see what exact changes we need to do in JS code apart from the above library change. alert: D365 V8: D365 V9: confirm: D365 V8: D365 V9: … Continue reading D365 V9{Upgrade}: Client API update for alert and confirm

D365 V9{Upgrade}: “v_5 is not a function” error while adding custom filter to lookup

Recently, after upgrading our one of the D365 instance to V9, we came across an issue with custom filtering of lookup. We were using below piece of code snippet to add custom filter: and below is the definition of the addFilterOpp method: fetchQuery = "<filter type='and'>" + "<condition attribute='sab_brandid' operator='eq' value='" + brandId + "' … Continue reading D365 V9{Upgrade}: “v_5 is not a function” error while adding custom filter to lookup

Azure Service Bus Queue Integration with D365 – Part 1

In this series, we'll see how we can integrate Azure Service Bus Queue with D365. This series has been divided into 2 parts: Part 1: How we can create a service bus queue in Azure portal and registration of service endpoint using plugin registration tool Part 2: Do some operation in D365 and the message … Continue reading Azure Service Bus Queue Integration with D365 – Part 1

Power BI: Organisational Content Pack not visible to other users

Recently, we created a content pack in power BI with access to entire Organisation as shown below: After creating it, we used another user to search for this content pack in Power BI and see the result. However, we didn't find any content pack by clicking on Get Data --> My Organisation or Get Data … Continue reading Power BI: Organisational Content Pack not visible to other users

SSIS: The component returned a failure code when the pipeline engine called PrimeOutput()

Recently, while working on SSIS package, we encountered the error after few minutes of execution of package. To get rid of this issue, we implemented one workaround: Go to Data Flow --> Properties Decrease the default buffer size to 1MB i.e. 1048576 Bytes Decrease the default Max Buffer rows to 1000 as shown below: After … Continue reading SSIS: The component returned a failure code when the pipeline engine called PrimeOutput()

SSIS: The column with the sortkeyposition value of 1 is not valid. It should be 0

Recently, while working on one of the existing SSIS package, we found that there were number of sort blocks in SSIS where as it could have been sorted at the source itself and informing the SSIS package that the data is already sorted at the source and can be processed further. Another disadvantage of using … Continue reading SSIS: The column with the sortkeyposition value of 1 is not valid. It should be 0

SSIS: Excel Connection Manager Error “Class not registered”

Recently, we were working on SSIS to get data from AX to the staging tables. As part of the requirement, we were also using Excel Connection Manager to read the data from one of the excel file and load it to a table. After completing the development, we executed the package and it was successfully … Continue reading SSIS: Excel Connection Manager Error “Class not registered”

SSIS: Login failed for user “NT AUTHORITY\ANONYMOUS LOGON”

Recently, we were working on SSIS for ETL(Extract,  Transform and Load) to get the data from AX and push to the staging tables. We were using linked server for AX and we were using Windows Authentication for connecting to it. While running the package from SSDT, it got executed successfully. So, we deployed the packages to … Continue reading SSIS: Login failed for user “NT AUTHORITY\ANONYMOUS LOGON”

SSIS: “The version number in the package is not valid. The version number can’t be greater that current version number”

Recently, while working on SSIS to get data from AX and putting in our staging tables, we faced a weird compatibility issue between SQL Server and SSDT version we were using. We were using database as SQL Server 2012 and SSDT for VS 2013. After completing our development, while executing the package from SSDT, it … Continue reading SSIS: “The version number in the package is not valid. The version number can’t be greater that current version number”