Open JohnTowgood opened 3 years ago
Hi @JohnTowgood - sounds interesting - is this so that you can easily re-export the data before committing to source control - similar to unpacking the metadata? I think the challenge will be making it easy to create the schema without the configuration migration tool GUI.
Hi @scottdurow, yes it is like unpacking Metadata but in this case unpacking/exporting reference data into source control. I have already built a small command line app to do this and have used it for a year now, so just need to port it to spkl. I had no issues generating the schema and used a configuration file to control attributes and fetchxml to control what data to export. By default all attributes are retrieved then configuration can be added to exclude attributes.
Hi Scott,
I am planning to use spkl as a base to implement data export functionality. It will be a spkl task which will extract data from a Dynamics 365 instance base on some configuration within the spkl.json file. It will create data.xml and data_schema.xml files (Similar to Configuration Migration Tool from Microsoft) and these files can be zipped up to be used by the Package Deployer. What are your thoughts on this?
Regards John