Introduction This log error will help us to understand and fix an issue as quickly. There are three main phases in an SSIS ETL execution life-cycle to catch errors: When data is being extracted from source systems When data is being transformed When data is loaded to the target systems Customized Error Handling also avoids the failure of Package during Runtime. It allows the package to be executed successfully and the Errors can be checked later from the Customized Error Log Table which you create to know what problem exactly occurred. Our Scenario For demonstration purpose, we will consider a Units Integration Map for Integration of Units from SQL to Dynamics CRM. In this Blog, we will Create a Customized Error Log Table in SQL and Catch the Errors from SQL (Source Block) and Dynamics CRM (Destination block). The Map for Unit Integration is as follows: Customized Error Handling in SSIS Execute the following query and create a customized Error Log Table in SSIS: CREATE TABLE [dbo].[ErrorLog]( [ErrorID][uniqueidentifier] NOT NULL default newid() primary key, [Entity] [varchar](250) NULL, [Record_Id] [int] NULL, [RecordName] [varchar](250) NULL, [ErrorDescription] [varchar](500) NULL, [DateTime] [datetime] NULL ) ON [PRIMARY] The structure of Table is as follows: ErrorID Entity Record_Id Record Name ErrorDescription DateTime Primary Key of Error Log Table. (System Generated) Unit UnitId Unit Name  Error Message  Error Log Date Error Handling at OLEDB Source Block: Step 1: Add a Script Component to catch the Error Description, Error Log Date and Entity. Select Transformation and click on Ok. Step 2: Connect the Error Output (Red Arrow) from OLDEB Source to the Script Component. Select “Redirect row” for all columns in the Error and Truncation Columns to redirect Error Output to Script Component. Step 3: Configure the Script Component as following: In Input Columns section Select Error Code and Error Column. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorDescription Unicode string [DT_WSTR] 500 ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your SQL connection In the Script Section click on Edit Script. After a minute a New Editor Window will Open. Here you have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: try { Row.Entity = “Unit”; Row.ErrorDescription = this.ComponentMetaData.GetErrorDescription(Row.ErrorCode); Row.ErrorLogDate = DateTime.Now; //If an error occurred due to Check Constraint, the ErrorColumn would be 0, and that error affects the entire row. Hence there is no specific column for that error   if (Row.ErrorColumn == 0) { Row.ErrorDescription = “An error that affects the entire row”; }   //If an error occurred due to Data type, then errorcolumn name would be updated.   else { var componentMetaData130 = this.ComponentMetaData as IDTSComponentMetaData130; if (componentMetaData130 != null) { Row.ErrorDescription = componentMetaData130.GetIdentificationStringByID(Row.ErrorColumn).Replace (“Customer Target.Inputs[OLE DB Destination Input].Columns[“, “”).Replace(“]”, “”); } } }   catch (Exception ex) { Row.ErrorDescription = “Unable to get Error Column Name”; } Click on Save and then Close the Window. Step 4: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select ErrorDecription Column and select Data Type as String. Click on OK. Step 5: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Error Handling at Dynamics Destination Block: Step 1: Perform the Steps 1 and 2 as specified above in Error Handling at OLEDB Source Block. Step 2: Configure the Script Component as following: In Input Columns section Select Error Code, Error Column and CrmErrorMessage. In Inputs and Outputs section Add following Columns Column Name Data Type Length ErrorLogDate database timestamp [DT_DBTIMESTAMP] —- Entity string [DT_STR] 50 In the Connection Managers Section add a new connection and select your CRM connection: In the Script Section click on Edit Script. You have to copy and paste the following Script inside the “public override void Input0_ProcessInputRow(Input0Buffer Row)” section. Code Snippet: Row.Entity = “Unit”; Row.ErrorLogDate = DateTime.Now;\ Click on Save and then Close the Window. Step 3: Add a Data Conversion Block to avoid any Truncation Errors because of Data Type Conversion between NVarchar and Varchar Data Types of the Error Description Column. Select CrmErrorMessage Column and select Data Type as String and length as 500 i.e. according to the length of columns SQL. Click on OK. Step 4: Add an OLEDB destination block. Configure your OLEDB Connection Manager and Select the Error Log Table which you had created in SQL Server. In the Mapping section do the following Mappings and click on Ok. Checking the Error Occurred during Integration You can see the Error rows passing through the Error Output and being logged in our Error Log Table. Open the Error Log Table to check the Errors Occurred. Now you can easily identify the errors occurred during Integration process from your Custom Error Log Table and solve them to have successful Integration results.  

In D365 Business Central there is no pre-defined Balance sheet/Income statement, because all these accounting statements can be viewed using Account Schedules. So, in this blog let’s see how we can create new Balance Sheet and how can we check the reports of Balance Sheet. 1.       Search for “Account Schedules” 2. Now, go to Balance sheet line, then select “Process” function and then select “Edit Account Schedule” 3. By selecting “Edit Account Schedule” this will open the following page 4. Now, select “Insert” function and then select the “Insert G/L Accounts”. 5. By selecting “Insert G/L accounts” function the following page will open. 6. Now, right click the three dot options as shown and then select the “select more” option. 7. Now, select all the Assets, Liabilities and Equity accounts to create a new balance sheet. 8. When you click “OK” all the accounts will get added to the accounts schedules as shown below in the picture. 9. Now, use the G/L accounts specified in the account schedules to post transactions. Later, when you want to create a report of the G/L accounts used in the balance sheet we can do so with the following steps. 10. Click on “Report” functions and choose the option to “Print” as shown below. 11. The following page will open, where you have options as follows: a.       Send to b.       Print c.       Preview 12. The report is generated as shown below: 13.  In the reports we can check the transactions with the dimensions assigned to the respective G/L accounts. Once, we choose the option to view the reports, we get options to select the dimensions and view the balance sheet report. In the picture below, we have one dimension as “Trader” and “Dan” is the assigned dimension value. Now, click on preview. 14. Below is the picture with the dimensions as displayed on the 2 G/L accounts. The values on the G/L accounts as seen in the picture are only for the dimension entries. Which means, the transactions with dimensions, are only viewed in the report.

While fetching images using fetch xml there is a possibility that you will not able to get the complete image. You will also notice that this issue generally happens when you are using the multiple internal entities. Description: We were working on a project where we displaying the records notes using the multiple entities, we noticed that it is not showing the complete images, but it is truncated or incomplete. Let’s see the actual query and the output Scenario 1: In the below query we are getting the incomplete images as a base 64 string Result Scenario 2 In the below fetch xml we are getting complete image. If you will closely look into the query distinct parameter for the first was true where as in second case it was false. Conclusion Hope this helps you to retrieve complete image and not the truncated one

Today, I will show you the Environment Setup for PSA to F&O integration with CDS. Step 1: Create the environment Open the link https://admin.powerapps.com and click to create new environment Following pop-up window will appear and enter the details and click on Create Environment, so new environment will gets created   The environment will get created   Step 2: Create the connections To create the connection, open the link https://web.powerapps.com and go to the connection in newly created environment (In this case: DemoEnvironment) In the data section click on connections section and click on the “Create a connection” to create new connection Following screen will be visible, select the “Dynamics 365” connection. When clicked on the Dynamics 365 popup window will appear asking whether to create connection or not. Click on create and enter the credentials     And finally source connection gets created Now create the Destination connection In the connections search for “Dynamics 365 for Fin & Ops”, when clicked it will ask whether to create connection or not click on create and then enter the credentials and finally connection will be created     Once we created the Environment and connections now create Connection sets and create project   Go to https://admin.powerapps.com and open the Data Integration tab.   2. Click on the connection set section and click on the “New Connection Set” following popup window will appear and click on Create   Step3: Once Connection set gets created now let’s create the Project   Go to project section and click new project and following form will be visible and enter the Integration project name and select the ready made template available or create custom integration project. In this case we are selecting ready made template for account and click on next.   Select the connection set from the drop down select the connection set which we have created earlier: DemoConnectionSet and click on next Select organization and click next and finally click on create   So now we have created accounts integration project Hope the above helps!

Introduction: In this blog, I will depict how a checkbox can be inserted in an SSRS report. Pre-Requisites: 1. Microsoft Dynamics 365 Business Central 2. SSRS Reports Steps: 1. Create a placeholder in the Table and insert the character mentioned below. 2. Now select the Font as Wingdings. The following set of symbols can be seen on the Report Layout. 3. When the report is run from the Business Central the checkbox can be seen. Conclusion: Thus, by using the following technique checkboxes can be generated in the SSRS report.

A mobile POS is a smartphone, tablet, or dedicated wireless device that performs the functions of a cash register or electronic point of sale terminal (ePOS). Mobile point-of-sale  technology has moved the point of sale from a brick-and-mortar location to wherever you need to complete a sale. mPOS solutions let you harness the power of a smartphone or tablet to accept payments on the spot. In my work with CloudFronts Technologies, I had a chance to put the process of mobile POS setup  with Dynamics 365 Finance and Operations for Retail to the test, working with House of Sonee Sports, the largest sporting goods retailers in Maldives. CloudFronts consulted and deployed the D365 platform across 15 stores across the Maldives and integrated their ‘BigCommerce platform’ with D365. Apart from this, the project also included migration from their existing AX 2012 R3 platform to D365FO and Retail on the Microsoft cloud for increasing operational efficiency. Sonee Sports wanted to drive the customer journey from online to in-store and hence they sought to leverage D365 for this digital transformation. This is among the first major retailers in Asia to get equipped with integrated mobile POS solutions. It allowed Sonee Sports to drive a 22.5 percent ROI and receive real time data to improve their efficiency. In this article, I’ll explain the process so that you can do it too. Step 1: Create a new Register. Step 2: Set up the following configurations: Hardware profile Visual profile Financial dimensions Screen layout Step 3: Screen layout Create a new screen layout The type for the screen layout will be Modern POS – Compact Width and height should be set as 480×850 pixels Button grids can be set based on requirements   Step 4: Create device Select the application type for the device as Retail Cloud POS Mention the register number Step 5: Configure the hardware station inside the store setup Add a new line for mobile device Select the hardware station type as shared The host name will be the static IP address of the system Step 6: Activation of POS The steps are the same as activating Cloud POS On the register page click on device select. The application type of this device is “Retail Cloud POS.” This means it is CPOS, a browser-based POS. It requires internet connectivity throughout.   Activation status is pending, and validation status is not run. Change the activation status from pending to activated and click on validate devices for activation.     Step 7: Installation of the hardware station Enable IIS on the system. Create an SSL certificate Download the hardware station setup in the system Resolve the prerequisites Select the SSL certificate that you created and test the connection

Transfer order mainly use for Transfer inventory from one location to another location. Below are the steps to create transfer Order In the Search box, enter Transfer Orders, and select the link Click on New button to create new transfer order. Select the Location in Transfer from Code field from where you want to ship the Inventory Select the Location in Transfer to Code field from where you want to receive the Inventory. Direct Transfer: If select yes then the transfer does not use as in-transit location. When you transfer directly, the Qty. to receive field will be locked with the same value as the quantity to ship. Select the Item, quantity on Transfer order lines. If Direct transfer is no then Select the Location in In-Transit Code field which is used for mainly material is shipped from one location but not received in another location. On Action tab, click on post button to ship the Inventory from one location. Select ship in message Box and click on OK. You can check Quantity which are shipped in Quantity Shipped field. Then again click on Post button to receive the inventory in another location. Select Receive in message box and click on OK. You can check transferred shipment in Posted Transfer Shipments. You can check transferred receipts in Posted Transfer Receipts. Conclusion:  Transfer orders involve posting items as shipped from one location and posting them as received at the other location.  

[carousel_slider]