Currently Merge-CrmDataPackage with pipeline works in a way that all piped packages get appended single AdditionalPackage.
I'd like improve command by allowing piping any number of CrmDataPackage and it will append in an order how items enter within pipeline.
That would allow me having many data projects locally that I want to merge and prepare a .zip for. CRM Packages just flow in and get merged
Get-ChildItem $DataRoot -Recurse -Filter "data.xml" `
| New-CrmDataPackage `
| Merge-CrmDataPackage `
| Export-CrmDataPackage -ZipPath $zipPath
New-CrmDataPackage is also a new command, because I want to get package objects from files within source control and without having to pass a connection to CRM.
Basically I have (or wish to have) a source control structure like this:
Data
entity1
data.xml
data_schema.xml
configentity
data.xml
data_schema.xml
productcatalog_manyentities
data.xml
data_schema.xml
And just pipe up some commands to pack it in a Data.zip for Package Deployer to use.
Currently
Merge-CrmDataPackagewith pipeline works in a way that all piped packages get appended singleAdditionalPackage.I'd like improve command by allowing piping any number of
CrmDataPackageand it will append in an order how items enter within pipeline.That would allow me having many data projects locally that I want to merge and prepare a .zip for. CRM Packages just flow in and get merged
New-CrmDataPackageis also a new command, because I want to get package objects from files within source control and without having to pass a connection to CRM.Basically I have (or wish to have) a source control structure like this:
And just pipe up some commands to pack it in a Data.zip for Package Deployer to use.