Decompose loyalty program setup metadata

[mnunezdm]

Loyalty Program Setup the main configuration metadata type for loyalty does not allow decomposition when retrieving deploying metadata

As it can be tough to manage when the setup gets very complex I think it would be beneficial to allow the decomposing/recomposing of this metadata to maintain legibility and better source control

I have tried doing a simple script to manually decompose/recompose the metadata but this adds complexity to the development and deployment process

[mcarvin8]

@mnunezdm - Depending on Salesforce's response, I imagine they would start with a Beta decomposition service before it making it GA if they proceed with this.

If you want to decompose more immediately and would like to try a 3rd party CLI plugin, you can give my plugin a stab assuming you are using a Salesforce DX Git repo - https://github.com/mcarvin8/sf-decomposer

If you create the JSON file in your repo root for the Hook, it can automatically decompose and recompose when running the retrieve and deploy CLI commands. Thereby, this shouldn't add any complexity to your deployment scripts outside of installing the plugin beforehand and configuring the JSON file for the hook.

The decomposed files will be named with SHA hashes. Based on the Metadata API guide, I could release a minor plugin update to add the unique ID element for LoyaltyProgramProcess[], which looks to be processName.

The meta suffix for this MD would be loyaltyProgramSetup.

[mcarvin8]

If you'd like, you can try sf-decomposer@4.1.8 , which I just released today to add support for the loyalty program setup unique ID element. I created it using the example meta file provided in the metadata api guide for this type.

[mnunezdm]

@mcarvin8 i'll give it a try! just one thing, are you just decomposing into loyalty program process? or you are also decomposing parameters and rules

This is what my "decomposition" looks like

[mcarvin8]

At the moment, my decomposition is just going into the 1st level, which in this case would be into loyalty program process.

I've been thinking about further decomposition and what would be the best way to program that for a more general solution.

My Salesforce decomposer depends on another NodeJS package I developed which is a general XML disassembler. I'll take a look into what updates I would need to do to decompose further past the 1st level and recompose successfully. If you have any suggestions, let me know on the xml-disassembler package.

I'm thinking I'll either need to update the nested element function to continue until there are no nested elements anymore or recursively call my disassembler until no more sub-directories are created. I have a "--postpurge" flag to delete XMLs after decomposing them so I'll have to use that.

[VivekMChawla]

@mnunezdm - I've added this to our New Source Behavior backlog for consideration. W-16511226.

If we proceed, a source decomposition design will first be presented to the community for feedback.

I'll post another message to this discussion if/when that happens.

Thank you!