Azure Data Factory - Getting data from D365 partylist attributes

Tim Goodsell (AP) 21 Reputation points
2024-11-12T06:28:56.4066667+00:00

Hi

I have read that the ADF dynamic 365 connectors (when using Copy) cannot extract data from partylist attributes nor can populate them when loading data in D365. If that is the case is there a work around or do i have to revert to using Kingswaysoft

Thanks

Tim

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,646 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Amira Bedhiafi 33,866 Reputation points Volunteer Moderator
    2024-11-12T10:41:07.5533333+00:00

    You're correct that ADF currently has limitations when handling partylist attributes in Dynamics 365. The Dynamics 365 connector in ADF does not support extracting data from partylist attributes during copy operations, nor does it support populating them when loading data into Dynamics 365.

    Workarounds:

    1. Custom Fields in Dynamics 365:
      • Create a custom text field in Dynamics 365 to store the serialized data of the partylist attribute.
      • Use a plugin or workflow within Dynamics 365 to serialize the partylist data into this custom field.
      • ADF can then extract data from this custom field.
      • On the destination side, deserialize the data back into the partylist format as needed.
    2. Alternative Tools:
      • Consider using third-party tools like KingswaySoft's SSIS Integration Toolkit for Microsoft Dynamics 365. This toolkit offers more comprehensive support for Dynamics 365 features, including handling partylist attributes.

    If your integration requirements heavily involve partylist attributes, using specialized tools like KingswaySoft may provide a more efficient and reliable solution.

    Links to help you :

    https://learn.microsoft.com/en-us/answers/questions/32173/azure-data-factory-type-of-column-allparties-is-no

    https://www.kingswaysoft.com/blog/2020/05/12/Manipulate-CRM-ActivityParty-Field-Values

    https://learn.microsoft.com/en-us/azure/data-factory/connector-dynamics-crm-office-365

    https://learn.microsoft.com/en-us/azure/data-factory/connector-dynamics-ax

    https://learn.microsoft.com/en-us/answers/questions/717785/when-the-features-to-support-attributetype-partyli

    0 comments No comments

  2. Smaran Thoomu 24,260 Reputation points Microsoft External Staff Moderator
    2024-11-12T11:12:23.0033333+00:00

    Hi @Tim Goodsell (AP)

    Welcome to Microsoft Q&A platform and thanks for posting your query here.

    You're absolutely right about the current limitations of the Azure Data Factory (ADF) dynamic 365 connectors when dealing with partylist attributes. While they don't directly support the extraction or population of these attributes during Copy activities, there are potential workarounds to consider:

    Custom API Development:
    Pros:

    • Full control over data extraction and insertion processes.
    • Ability to handle complex partylist scenarios.

    Cons:

    • Requires significant development effort and expertise.
    • Increased maintenance overhead.

    Data Integration Tools (Kingswaysoft):

    Pros:

    • Pre-built connectors and transformations for Dynamics 365.
    • Often easier to configure and maintain.

    Cons:

    • Licensing costs may apply.
    • Potential vendor lock-in.

    ADF's Web Activity with Custom API Calls:

    Pros:

    • Leverages ADF for orchestration and scheduling.
    • More flexibility than the standard connector.

    Cons:

    • Requires knowledge of API development and authentication.
    • Increased complexity compared to standard connectors.

    Choosing the Right Approach:

    The best approach depends on several factors:

    • Complexity of the Partylist Scenario: Simple scenarios might be handled with custom API calls, while complex ones may require a more robust solution like Kingswaysoft.
    • Development Resources and Expertise: If your team has the necessary skills, custom API development can be a viable option.
    • Cost Considerations: Licensing costs for tools like Kingswaysoft need to be factored in.
    • Long-Term Maintenance: Consider the ongoing maintenance effort for each approach.

    Similar thread: https://learn.microsoft.com/en-us/answers/questions/32173/azure-data-factory-type-of-column-allparties-is-no

    Reference: https://learn.microsoft.com/en-us/azure/data-factory/connector-dynamics-crm-office-365?tabs=data-factory#data-type-mapping-for-dynamics

    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.