search

abvogel / Microsoft.Xrm.DevOps.Data

This library provides an easy way to generate filtered data compatible with the Configuration Data Migration Tool. These zip files can be used to push specific records between Dynamics 365 environments using the Dynamics 365 Package Deployer.
MIT License
28 stars 3 forks source link

AppendM2MData Doesn't include the Entity Attributes in the Package #7

Closed dylanhaskins closed 5 years ago

dylanhaskins commented 5 years ago

Love the work you are doing with this :), the current
if (HasManyToManyAttribute(fetchXml)) { this.AppendM2MData(retrieveMultipleResponse.EntityCollection, GetFirstLinkEntityName(fetchXml)); }

results in an export that only includes the primary entity id but none of the other attributes specified in the FetchXML.

abvogel commented 5 years ago

Thanks! I'm super excited about the project and the potential!

Thanks for raising the issue - coincidentally came across the same thing today while testing a delta push of USD changes between environments.

dylanhaskins commented 5 years ago

Likewise, feel free to shout out if you need any testing help, starting to use it for some ALM bits, which is where it shines, as the manual configuration migration step historically was a barrier. Currently this issue is the only one preventing me right now from using it, but almost there 😉

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Andrew notifications@github.com Sent: Tuesday, June 18, 2019 11:17:31 AM To: abvogel/Microsoft.Xrm.DevOps.Data Cc: Dylan Haskins; Author Subject: Re: [abvogel/Microsoft.Xrm.DevOps.Data] AppendM2MData Doesn't include the Entity Attributes in the Package (#7)

Thanks! I'm super excited about the project and the potential!

Thanks for raising the issue - coincidentally came across the same thing today while testing a delta push of USD changes between environments.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/abvogel/Microsoft.Xrm.DevOps.Data/issues/7?email_source=notifications&email_token=ADLFGHCJ2SS7XQ3E7YGXGP3P3ALQXA5CNFSM4HY25RP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4WXAA#issuecomment-502885248, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADLFGHHEMBX73CTCDQ34STLP3ALQXANCNFSM4HY25RPQ.

HIREN-AITC commented 5 years ago

I have a data_schema.xml file from USD installation package. I want to use this file to export USD data to import into other environments through the pipeline. Is there any way I can use my data_schema.xml file to export the data? And yes, I came to this issue because I am also facing the same M2M relationship data inclusion issue.

abvogel commented 5 years ago

Currently the tool is driven from fetches - so that data_schema.xml file could be converted into a series of fetches that represent USD data. I'm going to reference your comment in another issue because being able to drive this from a schema.xml file would be a nice feature to have.

I'll try to add a few unit tests for M2M and get an official release out with support soon.

HIREN-AITC commented 5 years ago

Currently the tool is driven from fetches - so that data_schema.xml file could be converted into a series of fetches that represent USD data. I'm going to reference your comment in another issue because being able to drive this from a schema.xml file would be a nice feature to have.

I'll try to add a few unit tests for M2M and get an official release out with support soon.

Thanks for your prompt response, hope to see the new release soon.

dylanhaskins commented 5 years ago

Hey Andrew,

Any indication of timeline for committing this fix ?

Thanks in advance.

abvogel commented 5 years ago

v1.3.0 includes stub records for related m2m records - reflexive and otherwise.