Skip to main content

Microsoft Dynamics 365 Add/Update Customer Category TO iPaaS

customer category records from MSD365 to iPaaS.com

Updated yesterday

Overview

Customer Category records can be transferred to iPaaS.com through both manual sync and polling. This integration supports syncing of Customer Category data to iPaaS.com using the Microsoft Dynamics 365 Customer Price Group Code for identification.

Before You Begin

Ensure the following prerequisites are in place before configuring this integration.

Microsoft Dynamics 365 Requirements

  • Customer Price Group records must exist with valid Code and Description

  • Web Services must be enabled for Customer Price Groups

iPaaS.com Requirements

  • API credentials with create/update permissions for Customer Category API

  • Customer Pricing Group flag must be supported in iPaaS.com

ID Format

When manually transferring a Microsoft Dynamics 365 Customer Price Group to iPaaS.com, use the Price Group Code as the Customer Category identifier. Enter the correct Customer Price Group Code into the EXTERNAL ID input field on the iPaaS.com manual sync page.

  • Example: Retail

Mapping Collection Status

  • Status: Enabled

  • Trigger Events: Customer Price Group Create, Customer Price Group Update

Supported Child Collections

This integration does not support any child collections.

System Caveats

Microsoft Dynamics 365 Caveats

  • Code as Identifier: The Customer Price Group Code serves as the unique identifier for mapping to iPaaS.com Customer Categories.

iPaaS.com Caveats

  • Customer Pricing Group Flag: Categories synced from Microsoft Dynamics 365 are flagged as Customer Pricing Groups in iPaaS.com.

Authentication and Security

Microsoft Dynamics 365 API credentials are required for accessing the Customer Price Group API. Ensure credentials are stored securely within the iPaaS.com credential manager.

Integration Flow

The integration processes Microsoft Dynamics 365 Customer Price Group records as follows:

  1. Customer Price Group is created or updated in Microsoft Dynamics 365.

  2. Polling or manual sync triggers the transfer.

  3. iPaaS.com authenticates with Microsoft Dynamics 365 API.

  4. Price Group data is mapped to iPaaS.com Customer Category format.

  5. Customer Category record is created or updated in iPaaS.com.

  6. Transfer status and any errors are logged.

Mappings

Parent: Customer Category Add To iPaaS.com

Description

This mapping collection transfers Microsoft Dynamics 365 Customer Price Groups to iPaaS.com Customer Categories with the Customer Pricing Group flag enabled.

Mapping Type

Source (Dynamics 365)

Destination (iPaaS.com)

Description

Static

true

Customer Pricing Group

(Required) Flags the category as a Customer Pricing Group in iPaaS.com.

Field

Code

Name

(Required) Maps the Price Group Code to Category Name.

Field

Description

Description

(Recommended) Maps the Price Group Description.

Error Handling

Duplicate Category Code

Category with this code already exists.

  • Description: A Customer Category with the same Code already exists in iPaaS.com.

  • Resolution: Ensure Category codes are unique or update the existing record instead of creating a new one.

Missing Required Field

Code field is empty.

  • Description: The Code field is required for Customer Category creation.

  • Resolution: Ensure the Customer Price Group has a valid Code in Microsoft Dynamics 365.

Validation and Testing

Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.

Validation Rules

  • Code: Must be present and unique.

  • Description: Should be present for clarity.

Validation Checklist

  1. Customer Price Group Code is present and valid.

  2. Description is present.

  3. No duplicate codes exist in iPaaS.com.

Test Scenarios

Scenario 1: Valid Category Record

Sync a Customer Price Group from Microsoft Dynamics 365. Customer Category should be created in iPaaS.com with Customer Pricing Group flag set to true.

Scenario 2: Update Existing Category

Update a Customer Price Group description in Microsoft Dynamics 365. Changes should be reflected in iPaaS.com.

Scenario 3: Duplicate Code (Failure Case)

Attempt to sync a Customer Price Group with a code that already exists. Appropriate error handling should occur.

Additional Notes

  • Customer Price Groups are mapped to Customer Categories in iPaaS.com.

  • The Customer Pricing Group flag is automatically set to true for all synced categories.

  • Both polling and manual sync are supported for this integration.

  • The Code field serves as the unique identifier for matching records between systems.

Did this answer your question?