sfmc-devtools
sfmc-devtools copied to clipboard
Accenture
Fast-track your developers and devops engineers by allowing them to programmatically copy-paste / deploy changes and work offline
various types have the option to set up notification emails. we should offer a central md file in the docs folder that lets you check. **relevant types:** - automation -...
during mcdev upgrade we install the latest dependencies  however, if you just pull from the repo, mcdev does not force you run that. instead it only enforces using the...
## hash names _myPrivateField --> #myPrivateField _myPrivateMethod --> #myPrivateMethod **Advantage**: javascript/node enforces its privacy. It simply disallows using that method outside of its scope **Details**: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields ## get and set...
split from PR #749 / issue #139. Adding/removing should be possible though **problem**: couldn't figure out how to retrieve Roles assigned to a user only for a specific BU.
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior  concerning bad BU names in  ### Expected Behavior should...
automatins related to eventDefintions are currently filtered in automation.definition: filter: { description: ['Event Definition Automation'], }, ## fields - el.dataExtensionName - el.sourceApplicationExtensionId - el.publishedInteractionCount ??? - el.automationId - el.arguments.dataExtensionId -...
aside from default tests this needs to also cover `--refresh` which triggers refreshing triggeredSends that use an asset-message which we updated.
This is set to true by default and then enforces that unknown params lead to errors. We should brainstorm about this @DougMidgley ... There are certainly pros and cons here.
current:  better: if credential is wrong, tell the user what is available in config if credential was found but bu was not, advice to run [reloadBUs](https://github.com/Accenture/sfmc-devtools/wiki/06.a-~-Admin-Commands#reloadbus) and alternatively show...
 we currently show this warning but instead we could 1. auto-fix it 2. offer to auto-fix it 3. tell the user how to fix it via mcdev manually