Recently we got the below error in one of our SSIS Packages
The packages were working fine in one of the environments and were failing in another.
It was throwing an error in one of the lookup fields that was referring to the alternate key. Here the alternate was defined with 2 fields.
As it turned out in another environment the order of the fields was changed for the alternate key field.
We recreated the alternate key field in the proper order of the attributes to fix this.
Hope it helps..
Recently while working on an integration requirement we had to loop through all the XML Files within a folder and subfolder and create corresponding records inside Dynamics 365 CE.
For this, we used the XML Source component which is part of KingswaySoft’s Productivity Pack https://www.kingswaysoft.com/products/ssis-productivity-pack/help-manual/json-and-xml-processing/xml-source
Below are the steps we need to perform to loop through the files.
Create an SSIS Project and drag the Foreach Loop Container to the control flow.
Here we are using 3 variables, one for the full path to the file, the other for extension and the third one to specify the folder.
Double click and the Foreach Loop Editor, set the enumerator as Foreach File Enumerator and set the Directory and FileSpec property expressions to use the variables that we had defined.
Check the Traverse Subfolder if we want to traverse the subfolders.
Click on Variable Mapping and set the FilePath variable that will be used to iterate through the files in the Folder and Subfolder specified.
To see it in action, we have added a Script Task inside the container.
Here we have set the FilePath variable as the ReadOnlyVariables that we will read within the Script Task code and show it in the Message Box.
Our source code that reads the FilePath and displays it in the Message Box.
Now just execute the package and we will see it looping through all the XML files with the folder specified.
Hope it helps..
Today evening we were the third in the world after London and Heliniski to host our Happy Hour from Singapore and being the first one from Asia!
Let us start with thanking Mark Smith for his new initiative Power Platform Happy Hour!
We did few things same and some newer things. 5 MVPs connected on to this Happy hour, some virtually on Skype for Business!
Myself from Singapore
Not to forget the champs Jeeva and Kasun from Singapore
Nishant from Dubai
Debajit from Bengaluru
Sahan from Australia
Nadeeja from Australia:
Multiple community heads joined:
William from TDG
Simaranjit from Sydney
4 people got goodies which were e-books to my new book. Third one and one of my hardest projects : Mastering Dynamics 365 Customer Engagement which was launched here!
Not to forget the support from Microsoft in the form of Sanjeev!
Some more pictures:
Virtually happy!
Next time Please connect…
View original post 93 more words
Let suppose you’re trying to install a managed solution (such as Project Services Automation, Field Services, Portal, etc.) through Admin Center and you’re facing ‘Solution Installation Failed‘.
Since, Admin Center don’t provide any reason for failure, apart from retry or contact the support which are not very productive.
Go to Dynamics 365 Org – Settings – Customization – Solution History
Open the latest or related solution from ‘Internal Solution History’ view. And, reason for the failure of the solution is available under Exception Message. 🙂
Recently for one of our requirements we had to use the CDS/CRM Connection of KingswaySoft’s SSIS Integration Toolkit for Dynamics 365
Below are the steps to be followed –
Drag the Script Transformation component, specify any input columns and inputs / outputs as required.
In the Connection Managers add the connection to Dynamics 365
Click on Edit Script to open the Visual Studio.
Add references to below 3 assemblies. We need to search for the 2 KingswaySoft assemblies in the machine and then add them.
The sample code –
public override void Input0_ProcessInputRow(Input0Buffer Row)
{
var connMgr = this.Connections.CRMConnectionManager;
var connectionString = (string)connMgr.AcquireConnection(null);
var conn = new CrmConnection(connectionString);
var orgService = (IOrganizationService)conn.GetCrmService();
RetrieveRequest retRequest = new RetrieveRequest();
retRequest.ColumnSet = new ColumnSet();
retRequest.ColumnSet.AddColumn("statuscode");
retRequest.Target = new EntityReference("dxc_contract", "dxc_contractnumberinternal", Row.dxccontractnumberinternal);
var response = (RetrieveResponse)orgService.Execute(retRequest);
if (response.Entity != null)
{
// status is closed
if (((OptionSetValue)response.Entity.Attributes["statuscode"]).Value == 282210002)
{
Row.IsApprovedContract = "N";
}
else
{
Row.IsApprovedContract = "Y";
}
}
}
Get all the details here
Hope it helps..
While trying to register our custom workflow activity from Isolation mode – Sandboxed to None for Dynamics 365 On Premise we got the below error
This was because the user through which we were trying to register the plugin in None Isolation Mode using Plugin Registration Tool was not having Deployment Administrator role.
Adding the user to that Deployment Administrator role through Deployment Manager fixed the issue.
Read more about it
Hope it helps..
Nishant Rana's Weblog 