You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
janis-veinbergs
added a commit
to janis-veinbergs/Microsoft.Xrm.DevOps.Data
that referenced
this issue
Jan 24, 2024
Sorry for bombarding with PRs - however I got everything working (albeit this PR is just convenience, I first implemented them via PS functions) - the comma/dot separator is critical one, otherwise I just cannot use this module :(
the m2mrelationships bugfix is just inconvenience and this PR is just convenience.
I was always thinking about not breaking someone's commands and I manually tested that they continue working as they should.
Currently
Merge-CrmDataPackage
with pipeline works in a way that all piped packages get appended singleAdditionalPackage
.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
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:
And just pipe up some commands to pack it in a Data.zip for Package Deployer to use.
The text was updated successfully, but these errors were encountered: