Microsoft Common Data Service : CDS


Nice introduction to CDS !

Aishwarya C Ramachandran's avatarUpskill your Tech Skills

Before you go ahead, read this article if you would like the below questions answered: –

  1. What business problem does the CDS solve?
  2. How does the common Data Service(CDS) work?
  3. How can I get access to it?

Business Pain points

CDS brings together all data from different departments/ databases into 1 repository

CDS provides accurate end-to-end views of data from across systems

Today, even mature companies face issues of ‘disconnected data’. HR holds different attributes about the same set of data as Finance does. How would it look if in one place we can find information about an employee from every aspect (HR, Finance, Sales Performance etc.)

Pic1

How does CDS work?

At the core of the common data service is the Common Data Model.

The common data model comes prepopulated with many business entities that are useful across a variety of business and application domains. These entities can be…

View original post 435 more words

The collection of variables locked for read and write access is not available outside of PostExecute error in SSIS


We might get this error while trying to access a ReadWrite variable within Script Component outside Post Execute.

Here we were using it within ProcessInputRow method

As per the official documentation – the reason for this error is because ReadWriteVariables are only available inside PostExecute method for improved performance and minimizing locking.

https://docs.microsoft.com/en-us/sql/integration-services/extending-packages-scripting/data-flow-script-component/using-variables-in-the-script-component?view=sql-server-2017

Updating the code to use PostExecute method fixed the issue for us.

Hope it helps..

How to – Use OverriddenCreatedOn or Record Created On field to update Created On field in Dynamics 365


overriddencreatedon

While working in data migration project, when creating records in the target system, we would want the “created on” field to hold the original value instead of it being set to the actual value when it was created in the target system, which is set by the system or the platform itself.

Suppose we are having the “created on” field in our source SQL Server Table and we are creating the lead records in our target Dynamics 365 organization using KingswaySoft’s CRM Destination Component.

Here we have mapped the CreatedDate of our source table to overrriddecnreatedon field of Lead entity.

On executing the package, back inside Dynamics 365, we can see the following values for Created On and Record Created On (overrriddecnreatedon) field for the lead records.

Record created on will have the time when the record was created in Dynamics 365 and Created On field will have the values that we passed from our source SQL Table.

Get all the details here

https://blogs.msdn.microsoft.com/emeadcrmsupport/2012/08/01/the-truth-about-override-created-on-or-created-by-for-records-during-data-import/

Hope it helps..

Advertisements

Data Flow Transformations in SSIS


SSIS has various data flow transformation components that make it easy to manipulate the source data before it can be sent to the destination for processing.

Below are some of the most frequently used one

  • Data Conversion

For changing the data type of the source column.

Simply select the input column and then specify the data type for it.

For e.g., if our source has one of the date columns as a string, we can apply Data Conversion transformation to convert its data type to Date.

  • Derived Column

Can be used if we want to apply the expression to the source column and create a new column or update the existing column.

For e.g. we are interested in the Year part of the Modified Date column. For this we can use the Year Date/Time function, get the year part and add it as a new column.

  • Percentage Sampling and Row Sampling

To reduce the number of rows in the pipeline.

Percentage Sampling allows us to define the percentage of rows for sampling. It generates two output, one output for the rows that are selected and the other for the unselected.

Similarly, Rows Sampling allows us to specify the number of rows directly instead of a percentage. It also gives the option to select the columns.

  • Multicast

Multicast can be used to pass the same data to multiple destination as shown below.

Sort transformation can be used to specify sorting for the data. In the case of SQL, we can specify sort in the query itself however in case of working with flat files, this function can be handy.

To perform aggregation on the source data we can use Aggregation transformation.

  • Union All

Union All allows us to combine data from multiple sources. Here the column structure should be identical of the sources. The data from the first source is passed to the destination, followed by the data from the second.

We’d covered some of the common transformation components in this post, in the next post we’d try to cover the remaining frequently used transformation.

Hope it helps..

D365 V9{Upgrade}: Client API Change for openWebResource


Ajit Patra's avatarAjit Patra

Prior to D365 V9, we were using Xrm.Utility.openWebResource() to open a web resource in a new window. However, going forward in D365 V9 we need to use Xrm.Navigation.openWebResource() to perform the same operation. Let’s take an example:

D365 V8:

D365 V9:

Hope it helps !!

View original post

How to – Stop SSIS Package Execution in SSISDB


Suppose a package has been running for quite a long time or has been mistakenly run and we would like to stop its execution.

To do so

  • Right Click on SSISDB
  • Select All Execution Reports

  • Filter it to see all the Running packages

  • We can see our all the running packages there.

  • Now to stop any specific package, right click SSISDB and select Active Operations

  • From the Active Operation window, select the running job and click on Stop button to stop its execution.

  • Another option is to use the stored procedure à get the operation id of the running package and execute the stored procedure

Exec catalog.stop_operation  @operation_id = 199915


Hope it helps..