Greetings Marketing Cloud Experts! You've just updated (or installed) an AMPscript [MCFS] extension for Visual Studio Code. This version brings some really cool new features, that I would like to share with you. Share your ideas using this form, leave your feedback on the Extension Page or add a star on my github repository.
+ === NEW FEATURES ===
+ Extension now works with Corporate Proxies
+ Support for shared Dataextensions (you need to be connected to Ent BU)
- Connect to your MC account
- Find your SQL Query asset in the "SQL Queries" folder and open a "query.sql" file
- Click a "Run SQL Query" button located in the top right corner of the editor (or run a "MCFS: Run SQL Query" command from the Command Pallet)
- Connect to your MC account
- Find your Dataextension asset in the "Dataextensions" folder and open a "rows.csv" file
- Click a "Filter a Dataextension" button located in the top right corner of the editor (or run a "MCFS: Filter a Dataextension" command from the Command Pallet)
- Set the filter and hit enter
- Filter example: OrderID = 'ORD2123F2' AND SubscriberKey = 'ABC'
We have been talking about this behind the scenes already for quite some time but on March 26 the SFMC DevTools were finally open-sourced. It allows you to up-/download all kinds of metadata, run mass-deployments to multiple BUs and on top it can be integrated into your IDE or CI/CD solution. And here comes the best part: We are looking into the possibility of integrating it into this VSCode extension.
With a quick 5 minutes setup you'll be able to edit content blocks, emails, cloudpages, dataextensions and SQL queries without leaving Visual Studio Code. You can now avoid frequent copy-pasting and focus on your work. Have a look a quick demo below. To open Connection Manager:
- Press F1 (or 'CMD+Shift+P' on Mac and 'CTRL+Shift+P' on Windows)
- Start typing 'MCFS'
- Find 'MCFS Connecton Manager' and then press Enter
- You'll find detailed setup instuctions there
As of now, you can only edit existing assets (content blocks, emails, cloudpage and json message). Functionality that is not supported at the moment: create new asset, rename asset, move asset to a different folder, delete asset.
- In your MC accout, create a new installed package and add a 'Server-to-Server' API integration Component
- Add the following permissions:
- CHANNELS: Email (Read and Write)
- CHANNELS: Web (Read, Write, Publish)
- ASSETS: Saved Content (Read and Write)
- AUTOMATION: Automations (Read, Write, Execute)
- DATA: Data Extensions (Read, Write)
- Grant access to all required BUs
- Provide package details in the connection manager below, save it and connect
- You'll find the entire Content Builder library in your File Explorer tab
- To open Connection Manager next time press F1 (or 'CMD+Shift+P' on Mac and 'CTRL+Shift+P' on Windows) and start typing 'MCFS'. Find 'MCFS Connecton Manager' and then hit Enter
Detailed instructions with screenshots are available directly in the Connection Manager. To open Connection Manager press F1 (or 'CMD+Shift+P' on Mac and 'CTRL+Shift+P' on Windows) and start typing 'MCFS'. Find 'MCFS Connecton Manager' and then hit Enter.
- Content Builder assets (Emails, Messages and Content Blocks)
- Landing Pages (created with Content Builder editor)
- Dataextensions (Edit data in dataextensions, apply filters, export to CSV etc.)
- SQL Queries (Edit queries and Run them)
Each asset is presented as a folder that starts with an 'Ω' symbol. You can easily distinguish different asset types based on the colored square that goes after 'Ω':
- 🟥 - blocks
- 🟦 - emails
- 🟨 - templates
- 🟩 - cloudpages
- 🟪 - mobile messages
Each asset folder includes a readonly '__raw.readonly.json' file. This is an API representation of the asset. You can not modify. Instead you can modify all other files available under the asset folder. Each file represents a specific part of the asset. For the template based email you will see for example smth like:
- _htmlcontent.amp - template used to create an email
- _subject.amp - subject line of the email
- _preheader.amp - preheader of the email
- s01.b01.content.amp - content of the first content block (b01) that is located in the first template stack/placeholder (s01)
- s01.b01.super.amp - super content of the block above. Learn more about super content here
- s01.b02.content.amp - content of the second block in the first template stack
- s01.b02.super.amp - super content of the second block in the first template stack
- s02.b01.content.amp - content of the first block in the second template stack
- s02.b01.super.amp - super content of the first block in the second template stack
Now you can mouse hover a function name in your code and a small popup window including documentation on this function will show up. Check a small example below