[TASK] Documentation for 5.3

[JoernBerkefeld]

• [FEATURE] retrieve attributeSet and attributeGroup by default to allow checking if shared DataExtensions and data model are in sync  #1090 / PR feature/1090: make attributeGroup and attributeSet be retrieved by default #1091
• [FEATURE] Add support for Data Verfication activity in Automation. #325 / PR Feature/21 + 325 feature add support for verification activity in automation #1083
  https://github.com/Accenture/sfmc-devtools/wiki/05.-Metadata-Type-Support/_edit

MetadataType	CLI argument	Retrieved by Default	retrieve	deploy (create)	deploy (update)	delete	changeKey	buildTemplate	retrieveAsTemplate	Description
Data Designer Attribute Groups	attributeGroup	Yes	Yes	-	-	-	-	-	-	Groupings of Attribute Sets (Data Extensions) in Data Designer.
Data Designer Attribute Sets	attributeSet	Yes	Yes	-	-	-	-	-	-	Data Extensions linked together in Attribute Groups in Data Designer.
Automation: Verification Activity	verification	Yes	Yes	Yes	Yes	Yes	-	Yes	-	Check DataExtension for a row count

• [FEATURE] Fields added to Shared Data Extension are not visible in child Business Unit Data Designer #940 / pr Feature/940 fields added to shared data extension are not visible in child business unit data designer #1074
  https://github.com/Accenture/sfmc-devtools/wiki/06.b-~-Standard-Commands/_edit

deploy

Command: mcdev deploy [business unit] [metadata type] [metadata key] [--fromRetrieve] [--refresh] [--changeKeyValue=yourNewKey] [--changeKeyField=otherFieldInJson] [--execute] [--schedule] [--fixShared]

...

deploy & --fixShared:

If you deploy Shared Data Extensions, mcdev will force you to do that via Parent BU to avoid issues with SFMC APIs. Due to another bug, if one of these shared data extensions is used in an attribute group on a child BU, SFMC fails to update the field information on the attribute group and as a result you cannot select added or renamed fields in places like journey builder.

Example: user will be asked to select which BUs should be checked & potentially fixed

mcdev deploy MyProject/DEV dataExtension --fixShared
mcdev deploy MyProject/DEV dataExtension "key1,key2" --fixShared

Example: user will be asked to select which BUs should be checked & potentially fixed, but the BUs "buName1" and "buName2" are pre-selected

mcdev deploy MyProject/DEV dataExtension "key1" --fixShared="buName1,buName2"

Example: user will be asked to select which BUs should be checked & potentially fixed, but all BUs are pre-selected

mcdev deploy MyProject/DEV dataExtension "key1" --fixShared=*

Example: user will NOT be asked to select BUs; the BUs "buName1" and "buName2" are selected to be checked & potentially fixed

mcdev deploy MyProject/DEV dataExtension "key1,key2" --fixShared="buName1,buName2" --y
mcdev deploy MyProject/DEV dataExtension "key1" --fixShared=* --y

Supported types for deploy & fixShared:

Name	CLI Argument	Effect
DataExtension	dataExtension	Triggers update of relevant attribute groups on selected BUs

• [FEATURE] Add support for Data Verfication activity in Automation. #325 / PR Feature/21 + 325 feature add support for verification activity in automation #1083
  https://github.com/Accenture/sfmc-devtools/wiki/08.-Metadata-specific-settings-%26-options/_edit

Automation

Adding Verification Activities

When Verifications are created, they automatically get a new ID assigned. That same field also acts as key as there is no other field. This comes with the unique challenge of not being able to use the templating system nor pre-defined keys during deployments to ensure the automation can a) work and b) be deployed. To circumvent the issue, make sure to deploy verifications and automations at the same time. That way, the key as seen in the deploy folder is auto-replaced with the newly generated one in all automations that you are trying to deploy.

How does the mapping work?
The system tracks the key in the deploy folder vs the new key on a per-BU basis. That way, the mapping even works in massive multi-BU deployments.

[JoernBerkefeld]

done